Apply the AAR to successes, not only setbacks
Reviewing what actually caused a win produces replicable insight; reviewing only failures produces only loss-avoidance.
Why it works
Humans are more motivated to analyse failures than successes because negative events are more salient. This systematic bias means the learning database is skewed toward what to avoid rather than what to replicate. An AAR on a successful event asks the same four questions: identifying the specific conditions and decisions that contributed to the outcome produces a template that can be deliberately recreated rather than hoped for.
How to do it
- After any event that went unusually well, run the same four-question format.
- In the gap analysis, the "cause" is what you did that produced more than expected — identify it specifically.
- In the next-time action, specify how to recreate the favourable conditions intentionally.
- Build a "what works" library alongside the "what went wrong" analysis.
Evidence
Positive event review and strength-identification research supports the benefit of systematic analysis of successes; positive psychology interventions that identify and replicate conditions for peak performance show well-being and performance gains. (observational)
Research on "what went well" exercises shows mood benefits; whether systematic success-AARs translate directly to performance replication is less studied than failure-review.
Common mistake
Attributing success to personal qualities ("I’m just good at this") rather than to specific decisions or conditions, which produces no replicable insight.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for After-Action Review: The US Army’s Tool for Continuous Learning
- Run the four-question AAR within 24 hours of any significant event
What was planned? What happened? Why the gap? What next? — answered while memory is fresh.
- Separate judgment from analysis in the debrief
The AAR only produces learning when the analysis phase is free of performance judgments.
- End every AAR with one specific, time-bound next action
An AAR without a concrete next action produces insight without change.
- Build a regular AAR cadence, not just crisis-triggered reviews
Reviews triggered only by problems create a negative-events database; a regular cadence captures ordinary learning that compounds.
- Include a trusted other in high-stakes AARs
Self-conducted AARs have blind spots; a peer or coach who was not inside the event sees the causal story differently.
- Distinguish system causes from individual causes in the analysis
Most failures have system causes and individual causes; fixing only the individual leaves the system to produce the same result again.
Related concepts
- Deliberate Practice, Not Just Practice
Focused, feedback-driven practice at the edge of your ability
- WOOP: Wish, Outcome, Obstacle, Plan
The four steps, the science of mental contrasting, and why fantasy alone fails
- Growth Mindset: The Honest Version
The fixed-vs-growth idea, the real mechanisms, and where the evidence is weak