Practice : After-Action Review
Purpose and Strategic Importance
After-Action Review (AAR) is a structured reflection practice conducted following a significant event — a major delivery, a strategic decision outcome, an incident, or a programme completion — to extract learning and improve future performance. Developed originally by the US Army, it has become a cornerstone of high-performance organisations that treat every significant event as a learning opportunity.
The AAR shifts the question from "who is to blame?" to "what can we learn?" It creates a formal mechanism for leaders to own outcomes — both good and bad — and to extract insight that improves the next decision or delivery. Without it, organisations repeat the same mistakes at scale.
Description of the Practice
- AARs are conducted shortly after a significant event while detail and context are fresh.
- They address four questions: What was intended? What actually happened? Why was there a difference? What will we do differently?
- Blame is explicitly excluded — the focus is systemic learning, not individual judgement.
- Findings are documented and shared, not kept within the immediate team.
- Action items from AARs are tracked to completion, not filed and forgotten.
How to Practise It (Playbook)
1. Getting Started
- Schedule an AAR within one week of a significant event — delay reduces candour and accuracy.
- Use the four questions as a simple agenda: intent, reality, gap, and learning.
- Invite all participants who were involved, regardless of seniority — the frontline perspective is often the most informative.
- The facilitator's role is to draw out honest accounts, not to narrate or judge.
2. Scaling and Maturing
- Build AARs into the cadence following every major delivery milestone, incident, or strategic decision outcome.
- Create a shared learning repository where AAR findings are accessible across teams.
- Track whether action items from past AARs were implemented and whether they had the intended effect.
- Use aggregate AAR findings to identify systemic patterns — the same root causes appearing repeatedly signal a structural problem.
3. Team Behaviours to Encourage
- Participants share honest accounts of what happened, including their own errors and misjudgements.
- Leaders model accountability: naming their own contribution to what did not go as planned.
- Action items are owned by specific individuals and reviewed at subsequent AARs.
- Learning from AARs is shared laterally with other teams who face similar challenges.
4. Watch Out For…
- AARs that become blame sessions despite the framing — the facilitator must actively redirect.
- AARs held too long after the event, where memory has faded and the learning window has closed.
- Action items from AARs that are never implemented, eroding confidence in the practice.
- AARs that only happen after failures — positive events are equally rich in learning.
5. Signals of Success