The After Action Review: The Most Underrated Tool in Business

Every major military operation ends with an After Action Review. Every one.

Not a celebration. Not a debrief when things go wrong. Every operation. Win or lose.

The purpose is straightforward: capture what happened, why it happened, and what we're doing differently next time, while the details are still fresh and the team is still together.

Corporate retrospectives exist for the same reason. They're almost universally worse.

Here's why the AAR works, and how to run one that actually changes behavior.

The 4 Questions

A proper AAR answers four questions in order. The sequence matters.

1. What was supposed to happen?
   Establish the baseline. What was the plan? What were the objectives? What metrics defined success?

This step is skipped constantly in corporate retrospectives. Leaders jump straight to "what went wrong" before anyone has aligned on what the goal actually was. That conversation goes nowhere.

2. What actually happened?
   Report the facts. Not interpretations, not feelings, observable events. This is harder than it sounds because people naturally begin attributing causes before they've finished describing effects.

Get the sequence right. Walk through the timeline of what happened from beginning to end before anyone starts explaining why.

3. Why was there a difference?
   Now you analyze. Compare what was supposed to happen with what actually happened and identify the gaps in both directions. Why did some things go better than planned? Why did others go worse?

The most important discipline here is separating execution failures from planning failures. If the plan was wrong, optimizing the execution won't fix it. If the execution was wrong, the plan doesn't need to change. These are different problems with different solutions.

4. What do we do differently next time?
   Concrete, assigned, and time-bound changes. Not "we should communicate better." Specific: "We'll add a 15-minute handoff check to every sprint transition, and Sarah owns it."

If the action items from an AAR don't have an owner and a date, they don't exist.

Why Corporate Retrospectives Fail

Most corporate retrospectives fail at Question 3. They produce accurate descriptions of what happened (Question 2) and generate long lists of action items (Question 4), but skip the causal analysis that makes the action items meaningful.

The result: the same problems recur because the root causes were never identified, just documented.

The second failure mode is psychological safety, or the lack of it. AARs only work in environments where people can say "I made the wrong call" without it becoming ammunition in the next performance review. Leaders who use AAR feedback to assign blame will never get honest AARs. They'll get performances.

How to Run One

Before: Set the frame clearly. "This is a learning event. The goal is to understand what happened and improve. It's not an accountability session." Mean it.

During the AAR:

• Keep it to 60 minutes maximum. Longer and attention drifts.

• The leader speaks last on Questions 1–3. This is critical. If the boss answers first, everyone mirrors the boss's assessment. You want honest data, not social conformity.

• Assign a scribe to document action items in real time. Don't leave with a verbal agreement. Leave with a written document.

• Stick to the sequence. Resist the urge to jump to solutions before you understand the problem.

After: Publish the action items within 24 hours. Assign owners. Follow up in 30 days. The AAR has no value if nothing changes.

When to Run One

After every significant project, initiative, or milestone, not just when things go wrong. Some of the most valuable AARs come from understanding why something went better than expected.

Also run them after near-misses. The events where you almost failed but didn't are the most valuable learning opportunities, because the stakes were real and the lesson is still actionable.

The Insight

The military doesn't run AARs because leaders enjoy self-criticism. They run them because the cost of repeating mistakes in combat is too high.

In business, the cost of repeating mistakes is lower, until it isn't. The organizations that treat every significant event as a learning opportunity compound their institutional knowledge faster than those that only learn when forced to.

The AAR isn't a meeting. It's an investment in the team's future capability.

The Takeaway

Pick one project that ended in the last 60 days, successful or not. Run the four AAR questions with your team. Don't skip Question 1. Don't let anyone jump to Question 4 before you've finished Question 3.

Write down three things you'll do differently on the next project. Assign them.

That's it. That's the tool. The discipline is in the consistency.