How does "Separate judgment from analysis in the debrief" work?

Evaluative language ("that was a failure," "I did badly") activates defensive processing, which narrows the causal search to self-protective explanations rather than accurate ones. The Army’s format is explicitly non-judgmental: the question is "what caused the gap," not "who was at fault." The separation allows causal accuracy, which is the precondition for actionable improvement.

How does "Apply the AAR to successes, not only setbacks" work?

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 does "End every AAR with one specific, time-bound next action" work?

Implementation intentions — if-then plans specifying when and where a new behaviour will be performed — dramatically increase follow-through on intentions. An AAR insight that is not converted into an implementation intention exists as an aspiration in working memory, where it decays. A specific "next time X happens, I will do Y" converts the learning into a cued response that fires automatically.

How does "Build a regular AAR cadence, not just crisis-triggered reviews" work?

Deliberate practice theory holds that improvement is driven by systematic, feedback-rich engagement with performance — not by accumulated time. A regular review cadence provides the feedback loop that makes experience into expertise; absence of regular feedback means experience simply accumulates without converting to skill. Crisis-only reviews bias the learning database toward what went badly, missing the positive feedback that builds confidence and reinforces effective practices.

How does "Include a trusted other in high-stakes AARs" work?

Self-serving attribution bias and narrative smoothing are well-documented in memory and attribution research: people unconsciously revise their account of events to protect self-esteem and preserve a coherent narrative. A facilitating partner who was not inside the event can ask questions that surface inconsistencies in the causal account that the reviewer, within their own narrative, cannot access.

How does "Distinguish system causes from individual causes in the analysis" work?

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.

US Army — After Action Review

How do you conduct an after-action review and why does it improve performance?

A four-question debrief that turns experience into usable learning

Short answer

An after-action review (AAR) is a structured debriefing developed by the US Army that asks four questions after any event: What was supposed to happen? What actually happened? What caused the difference? What do we do differently next time? Applied consistently, AARs build a culture of learning from experience rather than simply moving on. The evidence base is primarily observational and practice-based; experimental studies are limited but supportive.

The after-action review was developed by the US Army in the 1970s as a way to extract learning from training exercises before lessons were forgotten. The format is deliberately simple: four questions applied within hours or days of any significant event. Its power is not in the format but in the discipline — most individuals and teams move from event to event without closing the loop. The practices below apply the AAR framework to personal and professional contexts, with honest notes on what is established versus inferred.

The practices (7)

Why it works

Memory for specific situational details degrades rapidly after events; encoding fades within hours while emotional impressions persist longer. Running an AAR within 24 hours captures specific facts — decisions, sequences, environmental conditions — that will not be available at a weekly review. The structured format redirects attention from blame to causation, which is what produces actionable learning rather than morale damage.

How to do it

1Immediately after a significant event (a presentation, a difficult conversation, a project phase), write answers to the four questions: intended outcome, actual outcome, cause of the gap, and one specific next-time adjustment.
2Keep the format short — 10–15 minutes maximum.
3Write in specifics: "I skipped the agenda because I felt rushed" rather than "communication was poor."
4End with a single, concrete, testable action: something to do differently in the next comparable situation.

Evidence

Observational

The AAR was developed through field application in the US Army and has been adopted widely in military, healthcare, and sports contexts. Research on structured debriefing in medical simulation and team settings shows consistent performance improvement over no-debrief conditions.

Honest caveat: Most rigorous debrief research is in team contexts; individual AAR practice extrapolates from this, as solo application has less direct study.

— Tannenbaum & Cerasoli (2013), meta-analysis of debriefing effectiveness, Human Factors

Common mistake: Waiting more than 48 hours to run the AAR, at which point specific situational memories have been replaced by narratives and the causal analysis becomes retrospective rationalisation.

Go deeper on this practice →

Practice this with IX Coach

Reading about a practice changes nothing on its own. IX Coach turns these into a guided, adaptive routine — discerning where you are in real time and walking the practice with you, session after session.

Start with IX Coach →