An After Action Review, or AAR, is a structured conversation used to learn from completed work, an event, a project, or a significant operating experience.
The purpose is not to assign blame.
The purpose is to compare what was expected with what actually happened, understand why, and decide what should be repeated or changed next time.
Start with the expected result
Before discussing what went wrong, clarify the original expectation.
Ask:
- What were we trying to accomplish?
- What did we expect to happen?
- What measures or conditions defined success?
- What assumptions did we make?
This creates a reference point for learning.
Without a clear expectation, the review can become a collection of opinions.
Compare with what actually happened
Describe the actual result using evidence.
Useful inputs may include:
- performance data;
- customer feedback;
- timing;
- defects;
- delays;
- safety events;
- resource use;
- observations from the team.
The goal is to establish the real outcome before explaining it.
Explore the gap
Ask why the expected and actual results differed.
Some differences may be negative.
Others may be positive.
A team may discover that a workaround, decision, or local adaptation worked better than planned.
Root Cause Analysis can support deeper investigation when the review exposes a significant recurring problem.
Capture what should be repeated
Continuous improvement is not only about correcting failure.
Teams should also identify:
- practices that worked;
- decisions that helped;
- communication patterns that were effective;
- controls that prevented problems;
- preparation that saved time.
Those strengths can become part of future standard work.
Convert lessons into action
A lesson is useful only when it changes future behavior.
Actions may include:
- update a checklist;
- change a standard;
- improve training;
- adjust planning assumptions;
- share learning with another team;
- add a new control.
Countermeasure Management helps turn important lessons into owned actions with due dates and effectiveness checks.
Use reflection without blame
People are less likely to share useful information if the review becomes a search for who made the mistake.
Psychological Safety supports open discussion of uncertainty, errors, and unexpected outcomes.
The facilitator should challenge the process and decisions while treating participants respectfully.
Connect to Hansei
Hansei emphasizes reflection on gaps and personal or organizational learning.
An After Action Review provides a practical team format for that reflection.
Share relevant learning
Some lessons have value beyond the original team.
Yokoten can help spread verified learning horizontally to similar processes or locations.
The receiving team should understand the context rather than blindly copy a solution.
Common mistakes
Holding the review too late, focusing only on failures, allowing senior voices to dominate, creating a long lesson list without action, and failing to share learning with other relevant teams are common mistakes.
Practical sequence
- define what was expected.
- describe what actually happened.
- identify meaningful gaps.
- explore why those gaps occurred.
- identify what worked well.
- identify what should change.
- assign important follow-up actions.
- update standards or planning assumptions.
- share transferable learning.
- check whether the lessons were actually used.
The practical lesson
An After Action Review turns experience into organizational learning.
The value is not the conversation itself. The value is what the organization does differently the next time.