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.
Why it works
Attribution research shows humans default to personal attribution ("I made a mistake") over situational attribution ("the system made this mistake easy to make"), especially in self-analysis. System causes — ambiguous processes, missing information, misaligned incentives — tend to recur until addressed structurally. Individual-level fixes on system problems produce temporary improvement followed by relapse.
How to do it
- In the causal analysis, ask both: "What did I do that contributed?" and "What about the situation or system made this outcome more likely?"
- For recurring gap patterns across multiple AARs, specifically look for the system cause rather than applying the individual fix again.
- Implement system changes (checklists, process modifications, environment redesigns) when a pattern repeats more than twice.
Evidence
Human factors and safety research consistently finds that system-level contributing factors are underweighted in post-event analyses, and that individual-blame responses leave error-producing systems intact. (clinical)
Safety engineering research focuses on high-consequence domains; the system-vs-individual attribution principle generalises to personal productivity and performance, but the stakes and stakes-structure differ.
Sources
- Reason (2000), "Human error: models and management", British Medical Journal
Common mistake
Resolving the same gap with the same individual-level fix repeatedly without asking whether the system is reliably producing the gap despite individual effort.
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.
- Apply the AAR to successes, not only setbacks
Reviewing what actually caused a win produces replicable insight; reviewing only failures produces only loss-avoidance.
- 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.
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