|
In This Section
|
Web Manager Playbook: Emergency Controls
Author: Kathy McShea
Published: February, 2009
In order to manage crisis communications, Web managers are well advised to set up management controls ahead of time – baking these procedures into your documentation and training positions you to avoid snafus and be prepared for the worst.
These ever-green guidelines that can be adapted to any enterprise organization:
Content Posting in an Emergency
Establish roles and responsibilities for who will be responsible for posting content during emergencies, such as dangerous weather conditions and threat conditions where you may have to work remotely. This may require getting off-duty contact information for approvers in your chain of command if remote email is not accessible such as personal email, phone or cell numbers.
Don't forget to set up remote access to the system for content managers using secure passwords and user IDs for login. That way remote maintenance should be possible from any Internet location.
Alerts in an Emergency
Newsfeeds, also called “really simple syndication” can be used on your news release or announcement page to help employees, the public and the media get real time notice when you update information on these pages. If you don’t have the page coded in XML, use the Delicious hack to create an easy RSS page from regular HTML page or other Web language.
By using a microblogging resource such as Yammer.com you can also setup texting alerts for those sharing a common domain name email address. Determine who in the organization is authorized to send alert notices to employees or the public using this system.
If an urgent notice is necessary, it should be coordinated through the office with primary responsibility for providing operational support for your system during duty hours. At other times it should be routed through your after-hours emergency contact system. If you are large enough to warrant it, a live help desk officer should be available 24-7-365 and have off-duty contact information to be used if necessary for support.
In the Event the Web Site is Offline
In the event that the Web site is offline due to a server malfunction or maintenance issue, make sure outage notification procedures are followed. You should have a temporary outage notification home page available from your server that is automatically posted.
If you have vital applications that are hosted on other servers are available to your users (either third-party or internal), I recommend a Quick Link area be prominently available from the outage notification home page. The links on the Quick Links section should have a review schedule to assure that the URLs are current and working.
Procedures to Collaborate with Content Providers
Typically more than one individual at the organization publishes to the Web. The publishing model could be cenetralized, with a common editorial team getting information from subject matter experts or decentralized with authority pushed to the frontlines.
Whatever the publishing model, in all cases the organization must minimize redundancy and to ensure that information on like topics is consistent and accurate across the organization. To accomplish this, the boss must encourage content providers to collaborate and have systems in place to support this.
The Department of Homeland Security (DHS) adopted a model process during Hurricane Katrina for this, which appear below with slight modifications. Using the language of the Information Superhighway, DHS called the knowledge owners with cross-functional information “Lane Managers” and required everyone to “stay in their lane”.
Business Unit Responsibility: Each business unit remains responsible for providing information that is in their own "lane."
Don't Neglect Community Outreach
Widgets and micro-blogging are great tools from the Web 2.0 space and Webmasters in the know have set up elegant light-weight systems to put them to good use.
A great example of a widget in action is the Federal hurricane response widget page at DHS has content available in “how to get help”, find family and friends, health and safety and donate and volunteer, among other topics. As a widget, the information is catalogued and maintained in real time and when stakeholder groups embed this widget into their sites, they get instant updates from all your experts.
For the inaugural, the DC Government tried to use twitter with a designated hash tag to spread information about the inaugural, and had over 300 followers and nearly 50 posts by the end of the event. But it was not clear that the command centers in the decentralized security team were fully aware of this tool or leveraging it to its fullest.
A selection of tweets from stranded ticket holders from a Huff Post expose the strained. At 10:15AM, for example, Cecilia Hanley tweeted, “DC better get someone with authority over to the purple ticket gate #inaug09” telegraphing an early warning about the security breakdown that left thousands shut out of the event.
Discuss
So what emergency procedures are you using in your organization?
RATE THIS ARTICLE:





