New Media Flak: Megaphone vs. Cocktail Party
TL;DR: A recent back and forth in the opinion pages of GW’s paper of note brought to light an emerging divide in publicists’ approaches to social media.
A recent back and forth in the opinion pages of GW’s paper of note brought to light an emerging divide in publicists’ approaches to social media. One the one hand, GW’s primary Twitter account, GWTweets, casts the University in a stoic, buttoned-up light, with little, if any interactions with members of the rather active online community (For example, mentions, @replies, or ReTweets). GWToday on the other hand, the de facto hub of the campus’s Twitter scene, and arguably a significant presence in higher education’s social media world, has historically taken a more cavalier approach to serving as the University’s digital face. But which approach is “best”?
Technology has the bad habit of upsetting social norms, and as much as we try, there’s nothing we can do to stop it.1 Organizations looking to establish a presence on Twitter cannot afford to treat social media like other media they may have encountered. Social media is not a megaphone for a flaks to broadcast the press releases they would otherwise post elsewhere, but rather a cocktail party that provide organizations with the unique opportunity to loosen their tie, grab a drink, and work the room.
There is a generation of communications directors and public affairs vice presidents out there that see the liberalizing power of social media as a liability, rather than an opportunity. Personal interaction with stakeholders, be they students at a university or just those who enjoy delicious, delicious sandwiches,2 allow organizations to connect with the people most passionate about their brand in a very real way. Just as it is second nature for city dwellers to walk past solicitors handing out pamphlets on the street corner, as the culture surrounding the technology continues to evolve so too will Twitter community begin to ostracize those members who refuse to join the ongoing digital dialog.
Simply put, Twitter is not a dumping ground for pre-vetted paper.3 The occasional typo or personal quip doesn’t hurt a company’s reputation, but rather humanizes it. So long as GWToday (or any corporate handle for that matter) falls short of sharing a picture of what they’re having for lunch, we can only hope that they continue to be the model for establishing an online presence, rather than the exception.
Without too much of a history lesson, see, for example, Abraham Lincoln overseeing the Civil War from the telegraph office ushering in a new era of hands-on presidential leadership; home telephones giving rise to entire industries dedicated to interrupting families’ dinners; Blackberrys changing business email etiquette. ↩
Jimmy John’s often frat-boy-esque vocabulary may push the limits of informal interactions with stakeholders, but none-the-less serves to promote their brand. ↩
Thank the internet gods that TwitterFeed’s RSS to Twitter conversion service didn’t catch on. ↩
If you enjoyed this post, you might also enjoy:
- The difference between 18F and USDS
- Why everything should have a URL
- Five best practices in open source: external engagement
- Why open source
- 19 reasons why technologists don't want to work at your government agency
- Four characteristics of modern collaboration tools
- 15 rules for communicating at GitHub
- The seven things a corporate Chief of Staff does
- 10 lessons learned fostering a community of communities at GitHub
- Leaders show their work
- Twelve tips for growing communities around your open source project
Ben Balter is the Director of Engineering Operations and Culture at GitHub, the world’s largest software development platform. Previously, as Chief of Staff for Security, he managed the office of the Chief Security Officer, improving overall business effectiveness of the Security organization through portfolio management, strategy, planning, culture, and values. As a Staff Technical Program manager for Enterprise and Compliance, Ben managed GitHub’s on-premises and SaaS enterprise offerings, and as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →