Skip to content

After-Action Reviews: Learning From a Crisis Without Blame

How to run an after-action review after a real crisis, using U.S. Army, wildland fire and FEMA practice, and turn lessons into tracked corrective actions.

Leader Chaos · Last reviewed October 23, 2026 · 5 min read

When a crisis ends, most teams are exhausted and want to move on. That is exactly when the most useful learning is available, and exactly when it is most likely to be lost. Within a few weeks, memories blur, people change roles, and the same gaps are waiting for the next emergency.

The after-action review (AAR) is a structured way to capture that learning. It comes from the U.S. Army and is now used well beyond it. The National Wildfire Coordinating Group (NWCG) notes that the AAR "is now used worldwide by military organizations, governments and private industry."

This guide explains how an AAR works, how to run one after a real crisis rather than a training exercise, and how to make sure the lessons actually change something.

What an after-action review is

The Army's Leader's Guide to After-Action Reviews (December 2013) describes an AAR as a professional discussion of a training event that enables participants to discover for themselves what happened and develop a strategy for improving performance. It contrasts this with a critique: a critique gives only one viewpoint, often leaves little room for discussion, and by focusing only on what is wrong it "prevents candid and open discussion" and stifles learning.

The guide describes four parts that apply both in training and in real operations:

  1. Review what was supposed to happen.
  2. Establish what actually happened, gathering as many perspectives as possible.
  3. Determine what was right or wrong with what happened.
  4. Determine how the task should be done differently next time, including who is responsible for making the changes.

It also distinguishes formal AARs, which take planning and preparation, from informal AARs, which can be held on the spot with very little setup.

The four questions, and how to spend your time

The NWCG's leadership toolbox frames the same structure as four questions and suggests how to divide the time:

  • What was planned? Spend about 25 percent of the time on this question and the next one together.
  • What actually happened? Pool multiple perspectives to build a shared picture.
  • Why did it happen? Spend about 25 percent of the time here, and focus on what, not who.
  • What are we going to do next time? Spend about 50 percent of the time here, covering both weaknesses to correct and strengths to sustain.

The time split is a useful discipline. It is easy for a group to spend most of an AAR retelling the story. Reserving half the time for the final question keeps the review pointed at improvement.

Setting the tone

The same toolbox offers practical guidance for facilitators. It recommends holding the AAR as soon after the event as possible with the people involved, making sure everyone participates, and setting clear ground rules: encourage candor and openness, give all participants equal ownership, focus on improving performance, and keep discussions confidential. It suggests opening with words like these: "This is not a critique, not meant to assign blame."

It also says the leader must take part and will occasionally have to accept criticism, because the team will be watching to see whether the process is real. And it offers techniques for common problems, such as asking quiet participants open-ended questions by name, tactfully interrupting someone who dominates, and asking why several times to reach a root cause.

When time is short, the toolbox describes a fast version: go around a circle and ask each person one question, such as what went well, what didn't, or what they would do differently next time.

Adapting an AAR after a real crisis

A training exercise and a real crisis are different. After a real event, people may be grieving, frightened or angry, and some may worry about blame, discipline or legal exposure. A few adjustments help:

  • Separate support from review. Make sure people have had time and resources to cope before asking them to analyze their performance. If the event involved serious injury or loss, see our guide to leading after a workplace tragedy first.
  • Review the system, not the individual. Questions like "What made that decision hard at the time?" draw out more than "Why did you do that?"
  • Clarify confidentiality honestly. If notes may be shared with insurers, regulators or lawyers, say so up front, and consider asking legal counsel how to handle documentation.
  • Hold more than one session if needed. A quick hotwash with the response team while memories are fresh can be followed by a fuller review a week or two later.

For example, imagine a regional credit union that lost power and phones at three branches for most of a day. Its review might find that the plan worked for power but nobody owned customer messaging, that the branch managers' phone tree was out of date, and that a teller's quick decision to post a handwritten sign at the door was one of the most effective actions of the day. All three findings are worth keeping.

From findings to corrective actions

FEMA's Homeland Security Exercise and Evaluation Program (HSEEP), which provides a consistent approach to exercises, shows how to make findings stick. It describes an immediate hotwash after an exercise, followed by an After-Action Report/Improvement Plan (AAR/IP) that documents strengths, areas for improvement and corrective actions. HSEEP also treats after-action reports from real-world incidents as inputs for planning future exercises.

HSEEP recommends that corrective actions be SMART: specific, measurable, achievable, relevant and time-bound. Its after-action meeting is meant to reach consensus on corrective actions, concrete deadlines and an owner for each one. It then calls for tracking corrective actions and reporting on them until they are complete.

That last step is the easiest one to skip. A list of lessons without owners and dates is a memory, not a plan. Put each corrective action in whatever system your team already uses for work, assign a name and a date, and review progress at a regular leadership meeting until every item is closed.

The Army guide's process has the same shape: plan, prepare, conduct and follow up. The follow-up is not optional.

Key takeaways

  • An AAR is a structured discussion of what was planned, what happened, why, and what to do next time.
  • Spend about half the time on the final question, and focus on what went wrong, not who.
  • Set ground rules for candor and confidentiality, and model accepting criticism as the leader.
  • After a real crisis, care for people first and be honest about how notes will be used.
  • Turn findings into SMART corrective actions with owners and deadlines, and track them to completion.

Sources

Spotted something out of date? Let us know.

More in Crisis Leadership