An After-Action Review (AAR) is a structured conversation held after an event, built on four questions: What was supposed to happen? What actually happened? Why was there a difference? What do we change? It is not a post-mortem and it is not a performance review. Run it the same way every time, close it with named owners, and every miss becomes doctrine instead of a repeat.
Where It Came From
The U.S. Army adopted the After-Action Review in the 1970s at the National Training Center, where units fought a dedicated opposing force and usually lost. The losses were the point. After each engagement, an observer walked the unit through what the plan said, what the ground truth was, and where the two parted company. Rank was left at the door. A private who saw the gap was expected to say so, and a commander who caused it was expected to hear it.
The practice spread to every echelon because it worked. It is now the single most transferable discipline the military has produced, and most civilian organizations have never run one properly.
The Four Questions
The AAR is nothing more than four questions asked in order. The order matters, because each one protects the next from drifting into blame or opinion.
- What was supposed to happen? State the plan, the intent, and the standard. If nobody can say what the standard was, you have found the first problem.
- What actually happened? Facts, in sequence, with times. No adjectives yet. This step takes the longest and is the one teams rush.
- Why was there a difference? Now the analysis. Look for causes in the plan, the information, the resources, and the decisions, in that order, before you look at the people.
- What do we change? Two lists: what to sustain and what to improve. Every improvement gets an owner and a date, or it does not go on the list.
Why It Compounds
A single AAR fixes one problem. A monthly AAR changes how the organization thinks. The team starts writing clearer plans because it knows the plan will be read back to it. Reporting improves because question two depends on it. Decisions get documented because question three will ask who made them and on what information.
The compounding is in the standard. Each review produces a small, written change to how the work is done. Over a year that is twelve corrections, each one tested against the next month's reality. Organizations that do not review repeat the same miss with different people, and call it bad luck.
Rules That Keep It Honest
- No rank in the room. The most junior person present can state a fact that contradicts the most senior. If that cannot happen in your organization, fix that before you run an AAR.
- Facts before causes, causes before fixes. Teams want to jump to the fix. Hold the order.
- The leader goes first on what went wrong. A leader who opens by naming their own mistake buys the honesty of everyone else.
- Sustain as well as improve. What worked is written down too, or it is lost the next time the roster changes.
- Same format every time. The value is in the repetition. An AAR that changes shape each month is a meeting, not a discipline.
Where It Fails
Three failure modes account for almost every AAR that stopped being useful.
It becomes a blame session. Question three gets asked about people instead of about the plan and the information they had. The next month, nobody volunteers a fact.
It becomes a ceremony. The review runs, the list is made, nobody owns an item, and the same items appear next month. The cure is question four: no owner, no entry.
It only runs after disasters. A review that only follows failure is a trial. Run it after wins too. A win with an unexamined cause is a loss waiting for different conditions.
How a First Sergeant Runs One
Our Principal closed operations with an AAR for 22 years, across four combat deployments and in readiness, budget, and logistics leadership for more than 3,000 personnel. The method he brings to a client is the one that survived that use: forty-five minutes, a whiteboard, the four questions in order, and two lists on the wall when it ends. Every Mission Success Solutions engagement closes the same way, including the ones that go well.
Run It This Month
Pick one project, launch, or quarter that just ended. Put the people who did the work in a room for forty-five minutes. Ask the four questions in order and write the answers where everyone can see them. Give each improvement an owner and a date. Put the next AAR on the calendar before you leave. Do it four times, then read the first one again and count how many of its items are still open.
Install the Habit
The On-Site Battle Rhythm Audit is one day at your location. We map your cadence of meetings, reports, and decisions, run a live AAR on your last significant project with your team, and leave you a prioritized fix list.
Services are provided on a best-efforts basis.
Want it to stick?
The Overwatch Advisory Retainer puts a monthly AAR on your calendar with us in the room. $3,500 per month.
Related reading
The OODA Loop for Executives: the decision cycle the AAR closes.
Questions
What is an After-Action Review?
A structured review held after a project, event, or operation that compares what was planned with what happened, finds the causes of any difference, and produces a written list of what to sustain and what to change, each change with an owner and a date.
What are the four questions of an After-Action Review?
What was supposed to happen? What actually happened? Why was there a difference? What do we change? They are asked in that order so that facts are established before causes and causes before fixes.
How long should an After-Action Review take?
Forty-five minutes is enough for most projects. Spend the most time on what actually happened, and stop when every improvement has an owner and a date.
How often should a leadership team run an After-Action Review?
After every significant project, and monthly as a standing review of the period. Run it after successes as well as failures, so that wins have known causes.
Who should lead an After-Action Review?
Someone who can hold the order of the questions and keep rank out of the room. The senior leader attends, speaks first about their own mistakes, and does not dominate the discussion.