Articles

When Collaboration is an Emergency

Tsunami, Earthquake, Hurricane, Flood - everyone’s nightmare disaster can also create the biggest challenges in collaboration and employing information technology. The same Communications of the ACM that had the 7 Habits article had a whole series of articles on Emergency Management Systems.  Surprisingly, the techniques that are required to cope with the flood of information in case of disaster don’t seem all that different from those required by business today. The Indonesian Tsunami and Hurricane Katrina taught the whole planet about the need to invest in preparedness and reaction capabilities regardless of how poor or how rich we are.

One article I found particularly interesting was The Human and Computer as a Team in Emergency Management Information Systems. In fact, nothing in this article seemed to be limited what is required in a disaster, but what is necessary for coping with daily business pressure and information overload. The primary process of coping with a disaster is Build the Picture, Understand the Picture, and Change the Picture in a Goal-Oriented Fashion. Sounds like good business strategy to me.

The article talks about the people who are involved in the command, control, and analysis for emergencies that are built on trust of others who also are working in 14-24 hour shifts knowing that mistakes can cost lives and immediate action is essential. As if describing the persona in a use case, these workers:

  • Feel they are exercising control
  • Have total focus on the problem at hand and ignore all that is not relevant
  • Improvise with unconventional solutions to appraise information and formulate decisions
  • Enjoy the challenge and curiosity of the effort
  • Are highly motivated due to the critical nature of the problem

This sounds like a typical Silicon Valley start-up or anyone else in a highly competitive field where people enjoy what they are doing. The design of the emergency response system then creates challenges that are not a typical of other collaborative systems in a highly reactive environment:

  • Obtain accurate and timely perceptions of reality through communication structures that track and facilitate open exchange of information
  • Enhance focus without interruption and require minimum effort to carry out a task
  • Encourage creativity and improvisation of both the individual and the team

Emergency_system

In disaster management systems under development, the emergency manager has the following tools at hand:

  • Information prioritization - rules to prioritize situational information defined by context
  • Decision support and modeling tools - impact analysis and support for decision execution
  • Representation of a common operating picture - visualization of what is happening and where resources are open to everyone

Wouldn’t it be great to have a system like this in any business? It requires a good understanding though of the participation of the people and computers. What is each good at and what is each bad at? People are good at:

  • Perceiving patterns
  • Improvising flexible procedures
  • Exercising judgment
  • Inductive reasoning
  • Detecting small changes by sight and sound
  • Storing large amounts of information for long periods of time and recalling facts at the right time

Machines are good at:

  • Responding quickly to control signals
  • Applying great force smoothly and precisely (like landing a 747)
  • Repetitive, routine tasks such as monitoring
  • Handling highly complex operations and multi-tasking
  • Deductive reasoning and computation
  • Storing information briefly

In other articles, there were extending these systems to use community participation using open source and mashup to collect information not just from officials but the public at large. Those that were prepared for the Tsunami were often ready because they were alerted by mobile phones. The internet can also play an important role in collecting intelligence. After all, the internet was originally designed to withstand thermo-nuclear war and breakdowns in individual communication links. Here are some examples of mashups for accessing and collecting information:

Emermap1

Emermap2

Automation and collaboration have a role in emergency management. Just as triage methods were invented in time of war and moved on to ordinary civil use, emergency systems can probably help teach us what is important in collaboration and process automation. The primary lesson that the Human and Computer as a Team article conveys is that we ignore the human role at our peril and that the computer supports people and helps build trust between people by increasing trust in the information that they are sharing.

The 7 Habits of Highly Effective Technology Leaders

One of the best values for money I have of any subscription is to the ACM (Association for Computing Machinery). The ACM is the premier organization for computer science and the ACM portal is the best place to go for the state of the art in computing. The Communications of the ACM is the monthly magazine for the latest themes in software and computing. I just got my March copy last week, which is a bit late, but is not unusual for a lot of things coming over to Europe. However, this issue is full of some very interesting articles around the topic of Emergency Response Systems and Time-Critical Information Systems.

Alignment
Some of the business-technology alignments proposed by Stephen Adriole

One article though, is not directly related to the topic, but is well worth reading. Modeled after Steven Covey’s 7 Habits series, the article The 7 Habits of Highly Effective Technology Leaders by Stephen Andriole looks at the habits of successful technology leaders gathered through surveys since 2001. The habits of highly effective business leaders are:

  1. Focus on business models and processes before they focus on technology infrastructure or applications
  2. Track technology that matters by focusing on the distinction between operation and strategic technology and the chasm between technology concepts, prototypes, and bona fide technology clusters
  3. Identify and prioritize business pain - and approaches to pain relief - as they move toward the create of business pleasure
  4. Optimize the value of shared services in centralized and decentralized companies, organize around the distinction between operation and strategic technology, and champion governance above and below the operational and strategic line
  5. Manage computing and communications and infrastructure professionally and const-effectively through negotiated service-level agreements (SLAs) and measurement best practices
  6. Communicate often and predictably, communicate good news and bad news in business terms, and provide transparent insight into technology initiatives through tools like dashboards
  7. Actively market their roles in the company as well as technology’s ongoing contribution to the business through a variety of tools and techniques

Although this list is not quite as deep and profound as Covey’s “Keep the end in mind” and “Sharpen the Saw”, it is an interesting way of looking at the transforming world of technology. I particularly like shifting notion from pain relief, a hang over from the analyst-driven days of ROI, to business pleasure or delight which is espoused in the concepts of Web 2.0.

My Photo

  Subscribe
Add to Google Reader or Homepage
Subscribe in 

Bloglines

Subscribe in NewsGator 

Online
Add to netvibes
Subscribe in FeedLounge

Blog Roll

Powered by TypePad
Member since 02/2005

My Online Status