Social Media Strategery

Image courtesy of O'Reilly Conferences on Flickr

As I’ve said many times before, Government 2.0 isn’t about technology, but what that technology enables. When the TSA rolls out an initiative like the IdeaFactory, developing and implementing the technology is the easy part (disclosure: my company has supported the IdeaFactory project).  When the GSA implements the Better Buy Project, getting UserVoice up and running was probably one of the easiest tasks on the whole project.  No, when a government agency decides to use technology to try to become more transparent, participatory, and/or collaborative, the technology isn’t what’s keeping the project leads up at night.  The hardest part of all of these initiatives is figuring how to change the way the government operates.

Managing change in the government is HARD, much harder than in the private sector. Leadership and, consequently, leadership priorities are constantly changing as administrations change. Because of this, employees suffer from change fatigue (if you don’t like how your department was reorganized, wait a year and it’ll change again), middle managers don’t invest in the change themselves, and leaders all too often push forward with their own agendas and goals, current organizational culture be damned. It’s no wonder we’re still talking about how the best way to create Government 2.0 – we’ve been way too focused on the easy part of this, the technology.

But if changing the government is so difficult, then why have some government leaders succeeded in bringing effective changes while so many others have failed?

To try to answer this question, Booz Allen Hamilton teamed with Harvard University Professor of Public Management, Steven Kelman to identify the common methods—the best “leadership practices”—used by successful government executives to transform their agencies and achieve mission goals. By studying 12 federal cabinet and sub-cabinet level agencies from the administrations of former President Bill Clinton and former President George W. Bush, the study determined which organizational strategies worked best for delivering effective, meaningful change in government—and which did not.  More than 250 interviews were conducted with federal agency leaders and their employees, career executives, congressional staff, unions, media, customers, and interest groups.

So, why are some government leaders able to innovate and reinvent themselves and others stagnate?  At this year’s Gov 2.0 Summit in Washington, DC, some of the findings from this study were discussed at the “Do You Have What It Takes to Change Government?” session. If you’re responsible for a Gov 2.0 initiative, here are some of the key findings that you should keep in mind as you attempt to change government.

• Use a collaborative strategic planning process - This isn’t going to happen via a memo or directive alone.  If you believe that your employees will become more open or collaborative because the boss said so, think again. Involve your employees in the strategic planning process. Sure, it takes a little longer, but you’ll be surprised at what you’ll learn and your employees will have some ownership in the change instead of feeling like they’re being told what to do.
• Develop performance measures – what does success look like?  Can you explain how becoming more open and collaborative will help your agency/team/department/group/division better achieve its mission?  Ten thousand Facebook fans isn’t a goal – your goals should be tied to your organization’s goals and objectives, and your employees should be judged on their ability to achieve those goals.
• Be proactive in building relationships with external groups – Your agency doesn’t exist in a vacuum.  Identify other groups who may be impacted, positively and negatively, and proactively go and meet with them.  Talk with them, listen to them, and involve them wherever and whenever you can.
• Re-organize if you need to – Assess the current organization and determine if you can achieve your goals within the current structure. Are there impenetrable stovepipes? Are there too many layers of middle management? Are there personality conflicts and “turf-guarding?”  Don’t be afraid to shake things up and move people around.
• Focus on 2-3 goals – The majority of successful leaders in the study had 2 or 3 goals that were action-oriented and quantifiable. Unsuccessful leaders typically had jargon-filled, tactical, action-based goals that described the effort, rather than the outcome. Gov 2.0 goals should be focused on an outcome – improving customer satisfaction levels or decreasing FOIA requests by making more data available online, etc.  Unsuccessful leaders typically use goals focused on an action – “implement a new knowledge management system” or “use social media more effectively.”

Here’s the full presentation as it was given at the Summit:

Do the top developers for Google’s Android operating system use Blackberries?  Do the IT guys developing Windows 7 use Macs?  Do the folks at WordPress use Blogger to host their personal blogs?

These are purposely ridiculous questions – wouldn’t the best developers use the actual tools they’re responsible for building?  Wouldn’t they do their job more effectively if they were actually a user of the product they’re developing? Doesn’t the product have more credibility if the people behind it are believers in the product’s features?  Out of everyone, shouldn’t the development team, at least, be the biggest advocates of the very software they’re implementing?  Shouldn’t they be the ones drinking the Kool-Aid?

Unfortunately, IT departments at large companies and government agencies are too often doing the equivalent of developing Android apps at work and using the iPhone at home. Sharepoint developers implement Sharepoint, yet they don’t use it to manage the implementation. The guys installing your organization’s blogging software don’t realize that the “Add a Picture” button doesn’t work because they don’t have blogs.  The team responsible for increasing awareness of your Enterprise 2.0 platform haven’t even created profiles of themselves.

Now, take a look at the official support areas for WordPress, Telligent, MindTouch, Jive or any of the dozens of social software vendor sites.  Notice anything? The developers are often the most active members of their respective communities and they’re using their own software day after day in the course of doing their jobs. If there’s a glitch involved with posting a new comment to a forum, they’re going to be the first ones to see it, diagnose the problem and fix it.

Sadly, I’ve been seeing these situations increase with the emergence of the Enterprise 2.0 and Government 2.0 initiatives. IT departments are increasingly being asked to implement wikis, blogs, social bookmarking, video-sharing, and dozens of other varieties of collaboration software – software they may know how to code, but often have no idea how to actually use.  They’re just told to “give us a wiki” or “develop a blog for me.”  Actually using the blog or wiki isn’t a requirement.  As as I was told by one programmer a year or so ago when I recommended he start a blog to inform the rest of the community about the latest enhancements and maintenance activities,

“Every hour I spend playing around on a blog post is an hour I spend away from coding!”

Well, that was helpful – thanks! Instead of getting frustrated and ending the conversation, I should have instead elaborated on the benefits that a developer enjoys when he becomes a user instead of just a developer.

• Higher quality product – you can identify bugs and feature improvements before they become problems for other users.
• Increased credibility – If, as a user,  I ask how to upload my photo, guess whose response I’m going to be believe – the guy with an empty profile or the guy who’s been active on the community for the last year?
• Increased “forgive-ability” – Look, we know that these sites will go down occasionally, especially when they’re first being developed.  We can deal with that…if we’ve been reading your blog and know that it’s down this Saturday night because you’re installing the new widget we’ve been asking for. If the site goes down and all we get is a 404 error page stating that the site is down for maintenance…again, we’re going to be less than pleased.
• Content Seeding – Clients are always asking,  “how are we going to get people to actually work on this site and add content?”  Well, before you even launch, if your project team (including developers, community managers, comms people, etc.) actually use the site you’re building, you’ll create a solid base of content before you even start to open it up to more people.  Adding to existing content (even if it’s not related) is always easier than creating something new.
• Common Ground – you become a member of the community instead of the guy behind the curtain making changes willy-nilly. You gain trust and respect because they know that you’re dealing with the same issues they are.  You’re struggling to access the site on your phone too.  You’re not getting the alerts you signed up for either.  You’re not able to embed videos correctly.  You go through what they go through.
• Greater ownership in the final product - The community becomes YOUR community, not something you’re just developing for a bunch of “users.”  You become invested in it and want to make it faster, add new features, win awards, etc. because you’re a part of it.

For all you non-developers out there, would you like your IT staff to be more visible?  Would you be interested in learning more about what’s happening under the hood of your Intranet/Enterprise 2.0 platform?  What other benefits do you see to getting them more involved?

For you developers, what’s preventing you from getting this involved in the communities/platforms that you’re responsible for creating?

Download our Gov 2.0 Capabilities Brochure

I’ll be at the Gov 2.0 Expo this week and I’m hoping that I’ll see you either there, or at one of the happy hours/tweet-ups that will surely be occurring.  If you’re the least bit interested in social media or the future of our government, I’d highly encourage you to register and come down for at least a few sessions. There are more than a hundred GREAT sessions taking place, but if you can’t get to all of them, consider participating in one of these ten hidden gems too.

If you are able to make it down to the Convention Center, make sure you stop by the Booz Allen booth on the Expo floor and say hello to me or to one of the many members of our team who will be attending the Expo as well.  Booz Allen is proud to be one of the Platinum Sponsors and I’m one of the members of the Program Committee – needless to say, everyone here at my firm believes very strongly in the principles of Gov 2.0 and has for some time now.  From our work with the Military Health System to U.S. Pacific Command’s All-Partners Access Network (APAN), Booz Allen has long advocated the principles of transparency, participation, and collaboration with all of our clients.

Grant McLaughlin and Walton Smith, two of our Principals, recently gave a short preview of what they will be discussing at the “Innovations in Gov 2.0” session on Wednesday.

Here are some of the projects we’ll be highlighting over the next three days:

Military Health System (MHS)

To strengthen relationships with its nine million beneficiaries and numerous stakeholder communities, the Department of Defense Military Health System (MHS) partnered with Booz Allen Hamilton to leverage social media (MHS Social Media Hub) to help MHS address service members’ healthcare concerns, collaborate with stakeholders, support combat operations, and enhance its capacity to reach and influence diverse audiences.  If you’re interested in learning more about our work with MHS, find Don Jones at the Expo or read more here.

U.S. Pacific Command All-Partners Access Network (APAN)

Booz Allen is working with PACOM to create APAN, a secure platform to foster collaboration and communication between government agencies, international partners, and non-government agencies.  The U.S. Pacifc Command (PACOM) operates in the Pacifc Rim with numerous actors (military, civilian, government, non-government) who must all cooperate in crisis and disaster response situations, joint exercises with foreign militaries and other events where open information flow is essential to success.  APAN has file sharing applications, wikis, blogs and calendaring tools to coordinate schedules. The system also supports mobile applications and integrates public social media sites, such as Twitter and Facebook, as well as sophisticated geospatial systems, such as Open Street, to create detailed maps of damaged areas. The system is designed to handle extremely secure communications, while also interacting with  the general public and disaster relief workers  and organizations. If you’re interested in learning more about APAN, talk to Walton Smith at the Expo or learn more on Bill Ives’ blog here.

U.S. Navy Chief of Information Office (CHINFO)

Booz Allen partnered with the Navy’s Emerging Media Directorate within CHINFO to develop a strategy for providing guidance to all Navy Commands on how to successfully integrate social media into their Public Affairs activities. We worked closely with the Navy Office of the Chief of Information (CHINFO) Emerging Media & Integration Team to develop a plan to:

• Integrate and optimize CHINFO’s use of social media as engagement tactic
• Achieve greater understanding of the use of social media among 300+ Public Affairs Officers
• Foster and align use of social media by commands and commanders (400,000+ Active Duty & Reserve personnel)
• Achieve recognition for the Navy as a military/government leader in social media

To learn more about what the Navy’s doing with social media, check out the Navy’s social media directory and SlideShare account. Or find Commander Scott McIlnay or Tracy Johnson at the Expo.

DHS First Responders Communities of Practice

Booz Allen is working with the DHS Science & Technology Directorate to build and manage the DHS First Responders Community of Practice – a platform that serves the nation’s 2.8 million emergency first responders (e.g., fire, emergency management, law enforcement). Launched in December 2009, the First Responders CoP is designed to decrease duplicate efforts across the various first responder communities and disciplines.  Users can connect with other first responders, create and join communities, create, share and edit documents, blogs, and discussions.  In addition, users can add “expertise tags” which allow them to easily find someone with specific expertise and view and connect to other users with similar expertise.

To learn more, make sure you attend Jose Vazquez’s presentation on Tuesday evening, or find Alexis Fabbri or Walton Smith on the Expo floor.

Meet our People

Stop by booth 309 (I think) to talk with our experts on privacy, cybersecurity, social media, Enterprise 2.0, identity and more.  Make sure that you follow all of our Booz Allen attendees on Twitter too!

Want to Work for Booz Allen?

Make sure you stop by our booth and find Annie Chae (@anniechae), one of our lead recruiters and one of my favorite people.  She’ll be able to answer all your questions about working for us.

Even if you have no interest in the work that we’re doing, make sure check out the full program schedule and try to come by and get to know some of the people who are driving this transformation in the way our government operates.

I’ve been in many meetings with senior executives where the topic has turned to social media, and sooner or later, THE question comes up -

“So, explain to me again why we should be playing around with [insert your social media tool of choice here]?  What’s the ROI of doing this?  I just don’t see how talking about what you ate for dinner on your ‘blog’ is going to help us accomplish the mission.”

Now, at this point, I’m usually fighting an internal battle between jamming a pencil in my eye or resisting the urge to shake the executives and yell, “why don’t you understand the benefits of open collaboration and communication??!!!”

Granted, the discussion doesn’t usually devolve to that level (but imagine how much more fun meetings would be if they did), but I’ve spoken to a number of people in the Gov 2.0 community who have experienced similar frustrations.  While there’s no shortage of resources for how to measure the ROI of social media, but unlike commercial companies, our government doesn’t use social media to make money or to sell products.  One can’t measure the value of using social media in a government agency in sales or revenue.  How do you measure the value of transparency?  How do you measure the value of open collaboration?  And even if you could, how do you make the case that transparency is worth the investment?

As Katie Paine says in Jason Falls’ excellent post on this topic, “Ultimately, the key question to ask when measuring engagement is, ‘Are we getting what we want out of the conversation?’”

So, are government agencies getting what they want out of the conversations?

That’s why Booz Allen Hamilton has teamed up with GovLoop to conduct an investigation into the usage of social media by our government at the federal, state, and local levels. We want to identify and assess the impact that the use of social media has had on efficiency, morale, budgets, outreach, internal communications, leadership effectiveness and other results.

To that end, we are conducting a survey of GovLoop members (survey is only open to members of GovLoop, so if you haven’t joined yet, this is a good reason to do so!) to get their input on what’s worked, what hasn’t, and why. The results of this survey will be published in a report and (hopefully) shared later this month at the Gov 2.0 Expo in Washington, DC.

For each survey respondent, GovLoop will also make a donation to the Social Media Club – Education Connection to further the development of social media education at our country’s colleges and universities.

If you’re a member of GovLoop, please take the survey and help us identify what types of benefits (if any) you and your organization are seeing from social media.