Tag Archives: Inciweb

Response to Big Windy Complex Fire Demonstrates Public Information Coordination

Post by: Kim Stephens

The recent National Capital Region (NCR) Social Media and Emergency Management Summit brought together Public Information Officers from across the metropolitan Washington DC geographic region.  One of the topics of conversation, and objectives of the event, was to determine how to have an effective/visible joint information system in an area that includes not only many large municipalities, but also many different layers of government, including Federal entities. The NCR summit attendees are part of the regional Emergency Support Function #15, which is designed to “provide accurate, coordinated, timely, and accessible information to affected audiences, including governments, media, the private sector, and the local populace, including children, those with disabilities and others with access and functional needs, and individuals with limited English proficiency.”

fire“Coordinated” is the key word in that definition, but a description of what should happen and what actually occurs are often two vastly different things. There is, however, a great example of what a well-coordinated ESF #15 effort can look like: the external affairs effort around the  “Big Windy Complex” forest fires in Oregon. How are they doing it?

1. Social Presence is not branded with any particular agency.

The external affairs teams providing and updating information about the Big Windy Complex Fire seem to be operating under the mantra “It’s not about us.” Instead of branding information with a particular Incident Management Team, local emergency management or law enforcement agency, or even the Virtual Operations Support Team that’s assisting with this effort, the name of the fire gets top billing. By branding the fire under an event-name versus an organization’s name members of the ESF #15 team can post consistently across the life-span of the fire. The public doesn’t care WHO is posting, they care WHAT is posted.


Branding the event is also huge in terms of how citizens search for content. For those of you in this business it might seem natural to look to the Type I Incident Management Team’s Facebook page–of course–who wouldn’t look there? It might even seem self-evident to look at the Bureau of Land Management’s social site or webpage; but for the general public, they honestly have no idea who these entities are or what they are responsible for. The public might have heard the name of the fire, or they might just know the location–and that’s what is going in the “Google machine.”

2.  Cooperation is visible.

cooperatorsThe Big Windy Complex blog site mimics the Inciweb standard of listing all “cooperators” on the fire response and recovery effort. The cooperators include local and state entities, as well as Federal agencies such as the Bureau of Land Management and the USDA Forest Service. These agencies are hyperlinked along with “Other Useful Links” such as the “Oregon Smoke Information” site. This is a very visible demonstration of cooperation that  implies content endorsement. I think it is key to gaining trust from the public–they might not know anyone who works for the USDA, but they probably know their local Sheriff.

3. Social Is Integrated, Standards are Followed

All of the social sites branded with the Big Windy Complex Fire also illustrate how standard practices are put into place and followed by the entire public information team (no matter which agency or entity is posting).  The standards are visible and can be illustrated by this Facebook entry:

‪#‎BigWindy‬ Complex: 8/17/2013 – Air Quality Summary Report – http://bit.ly/16WHDzI ‪#‎ORFire‬ ^MARH
This information also available on Inciweb:http://inciweb.nwcg.gov/incident/article/3570/20339/

This entry  demonstrates the following conventions:

  • All relevant hashtags are included;
  • Date and times are posted–when appropriate;
  • The person who provided the update is listed (^MARH)–this helps with accountability;
  • Links to official sources-such as Inciweb, are included;
  • The blog site is used as a secondary incident hub (Inciweb is the primary) and is linked to in each social post;
  • Although no questions were posted to this particular entry, it is also apparent from perusing the Facebook page that questions from the public are answered in a timely manner.

Does the Public Respond Favorably?

Although some emergency management work is thankless, social media provides the opportunity for the public to show their gratitude.  It is not uncommon after an event to receive an outpouring of public appreciation, and that is true for the Big Windy Complex event as well. The comment below was posted to the Facebook page and demonstrates that they are clearly reaching the target audience.

I just want to say thank you for this page and all the updates that have been provided. Never once in a million years did I think I would follow Twitter updates and a Facebook page for a wildfire. This is the first first fire my son has ever been on, and although those first several days I was a nervous mom, I can say the updates continually calmed my nerves. The updates are very telling of the management overseeing the fire; the concern for safety, and the desire to communicate to those who are impacted by this fire, whether near or far, directly or indirectly. Thank you, it is very much appreciated.

I agree! Thank you to the folks working on the Big Windy Complex fire for providing such as great case study. Go #VOSTies!

Lessons Learned: Handling an Angry Facebook Comment

Post by: Kim Stephens

Photo by: InernetMonk.com

I recently wrote a post titled “What happens when people make insensitive comments on your Facebook Page?” This post was about an angry/rude/obnoxious (insert descriptor here) person who made some ugly comments on the Barry Point Oregon Fire Facebook page this summer. The page, as well as other social media sites including a blog, a Twitter account, and a Google+ profile, was set up by the National Incident Management Organization (NIMO) with the aid of a Volunteer Operations Support Team (VOST) after the NIMO team assumed command of the  fire on August 13, 2012.

The objective of using social networking was to provide information to local residents on numerous platforms and to foster engagement. Although the Incident Information System website called Inciweb was in place with up-to-date content, Inciweb does not have a mechanism  to receive feedback from the community. Furthermore, the site is a little “crashy” as the warning implies: “Due to high demand this Web site may become unresponsive.”

Within 3 days of putting up the Facebook page, they got a little more engagement than they bargained for. So much so, in fact, that it led to not only my blog post about the incendiary comments, but a “lessons learned” report. You can download that paper written by Kris Eriksen, lead PIO, here: Barry Point SM Lessons learned.

The Story

What happened, in sum, was one woman decided to use the Facebook page to rant against the Forest Service  by posting the comment below. This comment was her idea of inserting a caption to a picture of the Incident Commander addressing people with the aid of a  megaphone at a shift change.

Hi Hater

Hi Hater (Photo credit: Wikipedia)

I can hear it now….. “THIS IS BIG DOLLARS MEN AND WOMEN” Your paychecks depend on this fire burning up as much as possible. The longer we can Let’er burn the bigger ALL of our pockets get! So be careful out there, eat a good lunch, be sure you all take your government mandated breaks… Every 15mins whether you need it or not! Ooh and don’t forget hacky sac play offs are tonite following directly after dinner, so be sure to practice on that while your standing around watching the fire today!

The reaction from the public was swift and in full support of the Forest Service and the firefighters. Other community members essentially ended up “shouting down” the woman and all of her subsequent comments: the quote above was just her first foray. As one of the PIOs is quoted as saying: “I don’t think we have to do anything. These people are totally trashing her!”

Keeping it Cool

What is interesting to me, however, is not what was happening on the page, but what was happening behind the scenes. By reading through the stream of comments it seems as if the PIOs were playing it completely cool–fully aware that the community would find her comments repulsive, or at least ill-informed, and come to their defense. But what the lessons-learned document, as well as my converstations with Ms. Eriksen, demonstrates is that a much more complicated story was unfolding, one full of hand-wringing.

Ms. Eriksen reflects:

It’s funny, but in the heat of the moment it didn’t seem as simple as it does looking back!!  I remember when the first comment appeared from Theresa and Brie Magee, another PIO, read it to me.  We all sort of said “Wow, that was nasty.” and we talked about answering, but didn’t. Many more comments came.”

In a situation such as this, the nature reaction is to defend yourself–“Hey-that’s not true!” As Ms Eriksen states:

“You want to respond.  You worry about where it will go and what damage letting it go might do.  Then there is the damage from stamping it out.  So you try to juggle it, knowing that the decision will have a long-term effect and is important, and realizing you only have one shot to get it right.”

But on a public page, administrators should understand that by arguing with someone they can diminish their own stature and add legitimacy to the person commenting. Kris says in the report

 “After one, I don’t remember which one, but it was factually wrong about how we fight fire, so I thought it was an opportunity to at least answer and say something, so I drafted a sort of generic answer about how we manage large fires and worked in a few things that referred to her earlier comments but didn’t address her directly, but still, we didn’t send it. We were still thinking about it. Some of the PIO’s were getting a bit worried about where this would go, were unhappy that it was happening and thought we should respond.” 

Mr. Eriksen writes that they didn’t have to talk about how they fought fires because citizens posted correct information. She also states that they determined that the woman shouldn’t be blocked  or her comments deleted because she never  violated the policy. But what they did want to do was let everyone visiting the page know they were watching what was happening and that they would draw act if things got out of hand (e.g. threatening comments were posted). This is why they decided to prominently re-post the comment policy. They also knew that these comments weren’t the first thing people saw when they visited the page–on Facebook,  comments are not featured prominently.

3 Great Lessons from a Public Relations Professional

Upon review of this case, a public relations expert sent Ms. Eriksen 3 reasons why ignoring the comments and leaving them on the page was the right thing to do:

“If you were to have deleted the post, you would have inflamed the situation by:

  1. Enforcing what negative poster said in her initial post and reiterated in several subsequent posts — that the system was at fault as was less than responsive;
  2. Encouraging her to keep posting thereby putting you in a situation of worrying more about her posts and whether to delete them again and again versus worrying about the things on which you should be focused;
  3. Deterring your defenders from posting all of that great information about the tasks and issues at hand.”

One thing the public relations expert didn’t relay is that deleting comments on a page representing a public agency–especially if they are just critical of the organization versus racist or threatening, could be considered a violation of the person’s first amendment rights and they might sue you…great.

A Happy Ending

I love Ms. Ericksen’s summation:

“In the end, I think the whole exchange was actually beneficial. I think the community came together over her comments and once the positive thank you’s started flowing, it’s was all really good stuff.  I think we reached a tipping point – on the page at least, where it became positive for us and the firefighter, despite the continued growth of the fire. We learned a lot about what could happen and I got my belief reaffirmed that the community would balance things out.  I think it will be a very powerful tool for agency leaders and others who hesitate because they worry about exchanges like this.

…There is additional pressure from knowing this will affect the future relationship between the agency you’ve been hired to work for and their community;  compounded by the fact that they didn’t ask for the social media to be done –  we just did it.  And they would likely (if it went badly) blame it on SM and our team, potentially harming every team’s ability to ever engage with social media again, anywhere.  The repercussions were enormous.  That load felt a bit heavy.”