Key Decision Log

Once again the Wildfire community is leading the way in developing tools that are leading the emergency response and emergency management community in developing tools needed in all the communities. The Key Decision Log designed to be used periodically during a response to review decisions made during the incident is a key action in developing situational awareness and a common operating picture. This allows commanders and their team to review and to analyze their decision in almost real time. It can be used at shift change briefs and during the planning period for the next Incident Action Plan. It is a simple yet powerful concept of analyzing why a decision was made and making sure that the whole team understands the reasoning behind the decision. It also records the affects of that decision on the incident. This type of document should adopted in every EOC in the country as a response tool for any type of incident.

Large Fire Management Wildland Fire Lessons Learned Center

Key Decision Log  

The Key Decision Log (KDL) is one of a suite of evolving tools that make up the WFDS System. It allows Agency Administrators, Fire Management Officers, incident management organizations and other fire leaders to accurately record, in near-real time, implementation decisions that directly and indirectly affect the management of a wildland fire.

Identifying best practices and promoting organizational learning is the cornerstone of a High Reliability Organization (HRO). By understanding how and why decision makers select a specific course of action, the complexity of an incident can be better understood and transparently communicated through agency channels. It can also be used as a real-time reference to past decisions that promotes consistency during team transitions and key decision points along the life of an incident. The KDL facilitates high reliability and continual improvement by allowing practitioners and researchers to recreate the sequence of events that occur over the life of an incident. These patterns can then be used to develop Lessons Learned that embrace the fundamental concept of Doctrine by sustaining best practices and identifying and eliminating unwanted decision traps.

Moving forward from a "Lessons Learned" framework - mindset

Lessons Learned are not learned unless actions are taken to correct the problems identified. Also lessons learned does not necessarily mean what was done wrong. That is another misnomer of the phrase. I have seen organizations and people afraid of lessons learned in AAR's because they point out where they made mistakes. It can be a reinforcement for some actions and a source of information for the correction of others. 

It has been my experience that there are plenty of lessons learned produced but the attitude in the industry is not one of learning from them. I hate to keep harping on the military use of lessons learned but there is a correlation between the military profession and our own. I'll always remember when General Schwarzkopf giving a briefing after the first Gulf War about the overall tactics of the war. He mentioned a Civil War battle that he had studied at West Point as the basis for his determining the tactics he would use. That is the example of how lessons learned should be used in our profession. I'll never forget one official after Katrina stating that one of the most difficult and unexpected problem after the storm was the total destruction of so much of the communication infrastructure. That lesson was learned after Hugo and Andrew close to twenty years previous. Until we as a profession begin study disasters and the various problems they produce to create our plans we will continue to repeat our mistakes.

What are the ABC's for emergency management?

Like the ABC's used in EMS for every patient; airway, breathing and circulation. What are the first three most important things an emergency manager must know to begin their response to any disaster? Are there three over arching pieces of information that should guide emergency managers in the initial hours or days of a response.

In my book using the Observe Orient Decide Act (OODA Loop) as my guide I came up with What do you have? What do you need to do? What do you need to do it? Repeat. Repeating the Three Questions would keep everyone in a constant state of evaluation until a clear picture has been established. My objective was try to find out how to begin. What do you do every time no matter how big or small the incident (a tornado or tsunami or earthquake) in the first minutes, hours or days to be able to properly size up and respond to an event. But I still feel as if there is a better more complete set of questions or basic principals out there. 

Part of the answer has to be the ICS/EOC interface. The people with their feet on the ground are your only assets in the beginning. One of the answers it would seem to me is: what assets are still capable of responding and what are they doing. This would include fire, law enforcement, public works, hospitals etc. What is their condition and have the been impacted by the incident and have they begun operations. This would be reported by the IC or if the incident was large enough multiple IC's. It goes back to the old question we used in the field when we walked up on an incident. What you got?

Mobile device use in recovery and early response

Mobile IT is at the center of emergency management of the future. I saw a video tape (that is how long ago it was) about an earthquake in California close to fifteen years ago. It was showing what the future held for the use of technology in a disaster. First it showed an earthquake warning system altering civilians and giving them a few seconds warning, enough to take cover. Japan has this system in place today and was used during the Mega Quake. It gave as much as thirty seconds warning depending on how far you were away from the epicenter. There is a wave that an earthquake produces that travels faster than the physical movement and can be recorded. Tens of thousands of residents received a warning on their cell phones. It was used even to trip some factories to shut off prior to the physical effects were felt.

Next it showed CERT team members using what is now an IPad to report damage and injuries to the EOC. It showed the same type of technology being used by the first responders to report progress or report damage. In Haiti they used a program to map the local of incoming calls of damage and injuries using cell phone location. These maps were used by the Marine Corp and Coast Guard to decide on the best use of their resources. So it is already beginning to happen.

I think the use of drones with live feeds to the EOC to receive an early damage assessment are the next big thing. Think if they could have been launched immediately after the tornado in Joplin.

I am not even touching on the power of social media to warn as well as collection information from the public.

So IT and mobile devices are at the center of emergency management. The biggest question is how to integrate it with current operations.