Category: Uncategorized

  • Via It’s Not My Emergency: The Chief Blogs

    Here We Go…

    Posted: January 23rd, 2011 | Author: chiefb2 | Filed under: Uncategorized | 3 Comments »

    The term above is something I tend to say to myself when I roll into someone’s bad situation.  I use it here because this is my first foray into the blog world, and may be creating my own bad situation!  Only time will tell.  My intent is to use this forum as a way to share my perspective on various aspects of emergency management and response, with a focus on the rapidly changing world of social media and how it is changing the rules for us emergency manager types.   For the record, I am a emergency response professional with 28 years in the fire service. I’ve been a firefighter, paramedic, fire captain, PIO, chief officer and incident commander for a regional all hazards IMT.  My posts reflect my personal views and not those of my employer (gotta have the disclaimer!).  We’ll see how it goes.

    The blogosphere got a bit richer in the last week or so. Chief Bill Boyd of social media and emergency management fame has started blogging. He’s got more experience in emergency management and public information than I can shake a stick at so I, for one, am looking forward to learning more from him.

  • Via Mitigation Journal: NIMS is dead

    NIMS is dead…you still have to take the classes and jump through the hoops…but the practice is dead. Few if any local governments or response agencies are truly NIMS compliant and the NIMS CAST has become just another checklist – to “say” we’ve done it. In reality our practice of NIMS under the National Response Framework is no better off at improving on-scene coordination and interoperability than twenty years ago.

    Sometimes I worry that I go too much for shock value when I title posts around here. Rick Russotti said the above in a recent editorial. Rick is an emergency responder badass and he says that NIMS is dead, so I figure that so long as I title things a smidge below Rick’s level, I should be okay.

    Beyond that, the full post is an interesting argument about the hoops we all jump through.

  • A Modest Proposal on How to Integrate Social Media Outreach Into Emergency Response

    As part of our ongoing series on the role of public information within the Incident Command Structure, it’s become increasingly apparent that social media is a big driver of the need for change or updating (read: not the only driver, though). To that end, I’d like to address this idea of social media in emergency response.

    First, there are LOTS of amazingly talented and intelligent people out there screaming from the rooftops that social media needs to be included as part of emergency preparedness and response. If you haven’t yet heard one of these folks, there’s a great list of them here. And the astute amongst you will see Craig Fugate, FEMA Administrator, about halfway down that list. If you’re not sure about the need for social media as a component of response, check out these folks Twitter feeds; reach out to them. Passionate doesn’t begin to describe how they feel.

    I start these posts with the mindset that you, the reader, understand the utility of social media during an emergency response, and understand that social media will be a large part of the public’s reaction to the emergency.

    Originally, this post looked at the problems associated with both outgoing social media messages and incoming social media messages, but not having reached resolution after several hundred words has lead me to separate the two. Therefore, today is a post on outgoing, with an upcoming post on incoming.

    If you think of social media as another communication tool, outgoing messages should be controlled by the PIO. Written in the the JIC, approved by the IC and released as the official word of the response. Just like a press release. Well, not really. How many versions does a press release go through? How many versions should a Facebook post go through?

    And this is where it gets tricky. Communications out of the JIC comprise the official voice of the response and anything less than perfect is, frankly, unacceptable. But then you think about the worst case scenario from my last post—twelve hours to get a release approved and, by the time it’s actually released, the information contained within is out of date.

    That’s obviously the worst case scenario, and should never have happened, but think about the timeframe we’re working with. The media can be sated for an hour while you get a release together and approved. Do you think that Joe@Philly, on the internet, can be sated for an hour? Or will he take that hour and post hundreds of inflammatory, incorrect, libelous messages on every social media network that he can register for?

    I’m guessing that probably the latter of the two is more likely.

    So, how should we reconcile the two? Speed versus… Well, accuracy is the wrong term, because quick statements are not necessarily wrong. Speed versus approval. Speed versus coordination.

    When it’s written like that I know where I stand. Our CERC motto is be first, be credible, be right. Nothing in there about proper approvals or coordinated messaging. It’s in the response’s best interest, though, to make sure that your Assistant PIOs aren’t going off half-cocked and releasing unapproved messages. That worry, though, still doesn’t preclude a response from releasing messages quickly, or using social media. If you’ve got someone releasing unapproved messages by phone, by Twitter, by personal contact, you take them off the response; a leak is a leak.

    The problem is that messages take too long to approve. Factual information is collected, vetted, passed to the PIOs, incorporated into messages, the messages are approved and then released. I argue that we should aim to take one of these steps out of the process. I suggest the approval step.

    Whoa, whoa, whoa, what did he say? Yep, I said it. I think that ICs should no longer approve messages before they’re distributed.

    Instead, the IC should approve two other things: the PIO (or spokesperson) and the facts. These are the facts of the situation as we know and can confirm them, and I trust you to craft appropriate messages based upon those facts. Done. At that point, there is no need to have the IC read every little tweet and Facebook post and press release. They can then focus on managing the response (which is what they’re good at and why they’ve been put in charge), instead of micromanaging what the PIO is good at and why she’s been put in charge of public information.

    I agree, it’s a pretty radical idea that diverts strongly from the established practices within ICS, but I think it manages to preserve the overall spirit of the system while allowing public information to flow in a manner appropriate to today’s media environment.