Bright+3

The Web 2.0 Pivot

Indian Gulch Fire (City of Golden photo).
During the Indian Gulch Fire near my community of Golden, Colorado several weeks ago (where I serve as the mayor), one of my City Council colleagues and I found ourselves focused primarily on gathering information about what was happening, sharing the information in a bunch of different ways (including Facebook and Twitter), and listening closely out on the ground and via social media to what our community members were asking and what they were concerned about (so that we could respond to all of that). (I posted more about the specifics of the lessons learned during the Indian Gulch fire on my mayor’s blog.

We weren’t officially representing the city while we were doing this, but by virtue of our roles in the community we had credibility and a lot of folks relied partly on our communication to stay on top of the fire and the evacuation situation. We were both (naturally) very plugged in to what was happening, and we used discretion when we weren’t certain of the facts or where sensitive information was in play, but it was entirely outside the formal command structure and communications system, and it created some consternation within that system that the mayor and a city councilor were engaged in so much independent communication.

This probably sounds like a familiar story. In fact, any organization that is struggling with the pivot to a Web 2.0 world will find itself grappling with these very same types of challenges: how do you maintain the accuracy of information when the flow is dispersed, how do you control the message when everyone has the means to alter it or even challenge it, how do you deploy your communication resources when the information flow far exceeds any capacity you will ever have to manage it, and how do you manage independent communication by people who are part of your own team?

In the case of an emergency response system, unlike most nonprofit environments, there is still a need for an unchallenged command-and-control decision process. Incident commanders need to make big picture decisions that they know will be implemented down through the vertical hierarchy, just as folks down that command chain have to know that their decisions will be implemented as well.

But the part of all this that involves communication and information flow lives outside of this command-and-control chain regardless of how hard the incident commanders work to contain it, and that’s why this is such a familiar-sounding story. (The Emergency Management blog has an interesting post about these challenges from the perspective of the emergency responders.)

The answer doesn’t reduce to adding your social networks to your press release distribution list (although that may be better than nothing). As Beth Kanter and Allison Fine argue in The Networked Nonprofit, you can’t simply layer a social media strategy on top of an organization whose modus operandi is largely defined by deep organizational hierarchies and one-way communication between the organization and its members. Your organization needs to be willing to adopt a “social culture” emphasizing two way communication and conversation with people inside and outside the organization, an openness to trying and learning from new approaches, and staff autonomy and agility.

In fact, some of the most important lessons we drew from our experience during the fire in Golden are the same sorts of lessons that nonprofit folks are drawing all the time now as they grapple with social networking:

For the most nimble and cutting-edge social sector organizations, this is easy. In fact, they are already fully inhabiting a Web 2.0 world, using social networking tools to engage, empower, and collaborate with their supporters. For everyone else, change is hard (as Dan Health likes to say).

Exit mobile version