After-Action Review
A structured debriefing process to analyze what happened, why it happened, and how to improve, originally developed by the U.S. Army.
Also known as: AAR, Post-mortem, Retrospective, Debrief
Category: Methods
Tags: learning, reflection, organizational-behavior, continuous-improvement, teams
Explanation
An After-Action Review (AAR) is a structured review process for analyzing what happened, why it happened, and how it can be done better. Developed by the U.S. Army in the 1970s, the AAR has become one of the most widely adopted organizational learning practices, used in military, business, healthcare, emergency response, and many other contexts.
**The AAR structure**:
The traditional AAR format centers on four key questions:
1. **What was supposed to happen?** (Planned)
- What were our objectives?
- What was the plan?
- What outcomes did we expect?
2. **What actually happened?** (Reality)
- What occurred?
- What were the actual outcomes?
- What's the factual timeline of events?
3. **Why did it happen?** (Analysis)
- What caused the gap between planned and actual?
- What worked well and why?
- What didn't work and why?
- What external factors influenced results?
4. **What can we do better next time?** (Learning)
- What should we sustain (keep doing)?
- What should we improve (do differently)?
- What should we start or stop doing?
- What specific actions will we take?
**Principles for effective AARs**:
- **No blame**: Focus on learning, not assigning fault. Psychological safety is essential.
- **Participant-driven**: Those who did the work should do the analysis
- **Facts first**: Establish what actually happened before analyzing why
- **Everyone contributes**: All perspectives are valuable; rank is left at the door
- **Candor**: Honest assessment requires safe environment for truth-telling
- **Focus on improvement**: The purpose is future performance, not historical judgment
- **Timely**: Conduct soon after events while memory is fresh
- **Action-oriented**: End with specific, assignable improvement actions
**Types of AARs**:
- **Formal AARs**: Scheduled, comprehensive reviews after significant events or projects
- **Informal AARs**: Quick discussions immediately after smaller activities
- **Personal AARs**: Individual reflection using the same framework
**Conducting an AAR**:
1. **Preparation**: Gather relevant data, timeline, and metrics
2. **Introduction**: Set tone (learning, not blame), review ground rules
3. **Review objectives**: What were we trying to achieve?
4. **Summary of events**: Build shared understanding of what happened
5. **Analysis**: Discuss gaps between intended and actual results
6. **Lessons and recommendations**: Identify insights and improvement actions
7. **Documentation**: Record key findings for organizational memory
8. **Follow-up**: Ensure lessons are implemented and shared
**Common pitfalls**:
- Turning into blame sessions rather than learning opportunities
- Focusing only on what went wrong, ignoring successes
- Vague lessons that don't translate to specific actions
- Not documenting or sharing findings
- Failing to implement identified improvements
- Conducting too long after events when memory has faded
**Personal AARs**:
Individuals can apply AAR principles to their own work:
- After completing a project or task, ask the four questions
- Keep a learning journal to capture insights
- Review regularly to identify patterns across experiences
- Connect insights to specific behavior changes
The AAR is a practical implementation of reflective practice that transforms experience into learning through structured dialogue and action planning.
Related Concepts
← Back to all concepts