Notification and communication in Washington Technology

September 5, 2007

It’s always great when you get interviewed for an article and the quotes they use are the ones you want and sound reasonably like what you remember saying. David Essex writing in the current issue of Washington Technology (a government technology publication) did just that. Another of the spate of articles about emergency notification following Virginia Tech, this article included the important point that most notifications, while critical, simply start the process of communication by creating a huge demand for additional information. Those who are able to follow up the initial siren with a constant stream of information updates distributed in multiple modes and formats and are also able to manage the incoming rush of questions and comments are the ones who are truly able to communicate. For more on this topic I encourage you to read the White Paper “Why Notification is Not Communciation.” Yes, I and my associate Marc Mullen wrote it.


2 Responses to “Notification and communication in Washington Technology”

  1. Mike Says:


    The white paper looks interesting, and I think I’m going to use it as a source for an end-of-class essay I’m writing on planned change communication versus unplanned change communication.


  2. Mike Says:

    Thanks for the great article. I work for an emergency notification company and we strongly suggest sending out multiple alerts throughout the course of a critical event in order to keep people updated about an ongoing situation. A good alert service also allows for 2-way communication, so that people who are outside can respond to an initial alert and provide additional information to administrators.

Comments are closed.

%d bloggers like this: