Tim Schneider Manager, Web Services Creative Services, External Relations University of Alberta Crisis Communications on the Web
What could possibly go wrong?
fire terrorist tornado active shooter systems failure blizzard bomb threat riot pandemic computer compromise road closures expolosion scandal bad news good news media attention You never know
Building your plan you can’t plan for everything starting point control what you know checklist
What we’ll cover
What we won’t cover
At the U of A
Keep the lines open
Go deep
PANDEMIC ~40%
How deep: technology?
February 5, 2008 Union University, Jackson, Tennessee
uuemergency.blogspot.c om
Remote access
What we plan for
Level 1
Browser
Level 2
Browser
Level 3
Traffic spike This is all that matters Ongoing event Level 3
April 16, 2007 Virgina Tech 9 minutes 49 people shot 32 dead
April 16, 2007 Virgina Tech Normal day: ~15GB April 16: 432GB
April 16, 2007 Virgina Tech Normal day: 193,258 Page Views April 16: 2,294,687 Page Views
What to plan for Speed Download Time to publish You could be anywhere Keep it simple Mobile devices
Refer everyone to website
Be very clear
Timestamp
What to do
Old vs. New information
Level 3 page Minimize external calls (.js,.css) Remove Google Analytics? Shutdown all other services on the server Provide mobile css ~20Kb
Browser
Procedural Identify source that will provide the web updates One person should always remain connected
Other communication tools Twitter
Other communication tools Twitter Google Earth
Other communication tools Twitter Google Earth Facebook Blogger Other municipality sites
During the crisis Use your peers Screen shots Gather feedback New ideas
During the crisis Continuous updating Monitor services Log
During the crisis Monitor social media Twitter Youtube Flickr Digg Delicious Technorati
Monitoring Social Media search.twitter.com Tweetdeck? RSS Yahoo Pipes Google Alerts Google Reader
Worst case scenario
Preview Slideshow
After the Crisis
Tell your story
Test & Review
Questions
More