Jonas Landgren’s blog takes a sharp look at the much-bandied notion of a Common Operational Picture:
The common operating picture is not in the map, but in the interactions where some form of common understanding is interpreted and negotiated.
It happened that I was back in D.C. last week, where I spent some time chatting with a GIS-oriented colleague about this very question. It’s closely related to another buzz-term we toss around with more vigor than rigor: “situational awareness.”
In both cases I’m afraid what used to be technical terms have been absorbed into marketing- and proposal-speak and have lost much of their actual meaning. (For folks interested in understanding what’s actually known about situational awareness… what it comprises, how it’s achieved and what it’s good for… I’ll recommend the writings of Dr. Mica Endsley, especially her book “Designing for Situational Awareness.” Turns out there’s a lot more to it than just projecting maps on a large screen.)
Underlying these particular bits of jargon is an error that’s bedeviled emergency management for many years, even before the current post-9/11 American militarismo: A tendency to confuse our tactics with our goals, our means with our ends.
Both “situational awareness” (SA) and “common operational picture” (COP) have become objects of this ends/means inversion. Neither SA nor a COP is an end in itself. What we’re really hoping to achieve is better decisions. The implicit assumption in much of the current homeland-security / emergency-management literature is that map-based COPs are the key to making improved decisions. But as Jonas’ article reminds us, that’s only an assumption.
The problem with the map-centered approach is that a lot of interesting parameters of use in the detection and management of emergencies aren’t geographic in dimensions. Many of them are much more appropriately charted against time, or proportionally, or against demographic or economic parameters, and so on.
For example, one of the most useful displays I saw on the giant video screens of Florida’s state EOC last year was a very simple line graph showing the volume of auto traffic crossing a single freeway sensor loop. It showed vividly the onset, peak and diminishment of evacuation traffic. In a glance it showed that, at the point I saw it, the majority of folks who were going to move had already done so. It would also have been useful to see that particular sensing location plotted on a map, but even without any geospatial information at all, it was highly meaningful in a way that a map depiction of current traffic at a particular point wouldn’t be.
My narrow point isn’t that maps are bad, but only that they aren’t the answer to every question. My broader point is that we need to resist the temptation to let particular solutions become ends in themselves and lose focus on our actual goals.
(And for folks interested in the wide range of ways visual presentations can support decisionmaking… including but going far beyond just maps… I’ll recommend the books of Edward Tufte, especially “The Visual Display of Quantative Information.” For a quick read-in on how life-safety critical this stuff can be, take a look at Tufte’s analysis of how a poorly-crafted PowerPoint presentation obscured critical information that might have prevented the Challenger space shuttle disaster.)
Comments