After Action Review¶

Strategy · All strategies
Evidence · 1 claim (1 for) · 3 studies (2 causal, 1 quant-synthesis), q3–q4 · 1 of 3 report an effect size

Description¶

An After Action Review (AAR) is a structured reflection conducted immediately after a task, simulation, or performance episode. Learners answer four canonical questions — what was supposed to happen, what actually happened, why the differences occurred, and what will be done differently next time — converting experience into explicit, transferable lessons. The format originated in the U.S. Army and has been adapted widely in medical simulation, aviation, and project-based education.

Design Implications¶

AARs work because they force comparison between expected and observed outcomes, which surfaces faulty mental models that unstructured experience leaves implicit Comparing and contrasting cases improves learning. [+M]. The review must be blame-free and learner-led; when facilitators dominate or attribute error to individuals, psychological safety collapses and participants stop surfacing genuine causes. Timing matters: conducting the AAR while memory of the event is fresh preserves diagnostic detail.

Context¶

Requirements¶

• A concrete, recently completed performance event with observable outcomes
• A facilitator (or trained peer) who enforces the four-question structure and a no-blame norm
• Time to articulate causes and commit to specific changes (Articulation)
• A record of lessons learned that feeds into the next attempt or Practice cycle

Constraints¶

• In low-trust or hierarchically charged environments, learners underreport errors and the review produces sanitized lessons
• Reviews of rare or ambiguous events can entrench wrong causal explanations when groups settle on a plausible-but-incorrect "why" without evidence
• AARs conducted long after the event lose accuracy as memory reconstructs; immediate or same-day review is substantially more diagnostic
• Overuse on routine tasks breeds ritual compliance — the format adds value only when outcomes were uncertain or performance fell short

Implementation Variability¶

• Facilitator-led (medical simulation debriefs): an instructor probes causal reasoning with advocacy-inquiry questioning
• Peer-led team AAR (project-based learning): students rotate the facilitator role to build evaluative capability
• Micro-AAR: a two-minute self-questioning routine after individual problem sets or writing drafts
• Written AAR logs: asynchronous versions in online courses, ideally paired with instructor Feedback on the causal analysis itself

Target Learners¶

• Learners in simulation, clinical, or performance-based settings where errors carry diagnostic information
• Intermediate learners who have enough experience to generate causal hypotheses; pure novices often lack the knowledge to explain why outcomes diverged and need expert modeling of the causal analysis
• Teams, where shared review builds a common model of what "good" looks like

Target Learning Goals¶

• Transfer: extracting generalizable principles from specific episodes
• Self-regulation: building the habit of monitoring and adjusting one's own performance
• Diagnostic reasoning: linking outcomes to underlying causes rather than surface features

Instructions¶

1. Complete the task, simulation, or performance episode and capture observable outcomes.
2. Ask: What was supposed to happen? — restate the intent and success criteria.
3. Ask: What actually happened? — establish facts before interpretations.
4. Ask: Why was there a difference? — probe causal explanations, using Articulation to make reasoning explicit; the facilitator models expert causal analysis for novices.
5. Ask: What will we do differently? — commit to specific, testable adjustments for the next cycle.
6. Record lessons and revisit them at the start of the next attempt, closing the loop with Practice.

Related Strategies¶

• Structured debriefing in simulation-based education — the clinical adaptation of the same four-question protocol
• Error analysis — AAR is the team-level, event-driven form of the same diagnostic move
• Use premortem analysis before implementing a reform to surface success factors and roadblocks

Examples¶

• U.S. Army training doctrine — the original AAR format, run at soldier, team, and unit levels after every training exercise, with lessons rolled into the next iteration (Army field guidance).
• Medical simulation debriefing — programs such as those following the Center for Medical Simulation debriefing model use advocacy-inquiry versions of the AAR after mannequin-based scenarios.
• Agile retrospectives — software teams run sprint retrospectives that adapt the AAR's intent/actual/cause/change structure to development work.

Key Sources¶

• Morrison, J. E., & Meliza, L. L. (1999). Foundations of the after action review process (IDA Document D-2331). Institute for Defense Analyses.
• Ellis, S., & Davidi, I. (2005). After-event reviews: Drawing lessons from successful and failed experience. Journal of Applied Psychology, 90(5), 857–871. doi:10.1037/0021-9010.90.5.857
• Rudolph, J. W., Raemer, D. B., & Simon, R. (2014). Establishing a safe container for learning in simulation: The role of the presimulation briefing. Simulation in Healthcare, 9(6), 339–349. doi:10.1097/SIH.0000000000000047
• Tannenbaum, S. I., & Cerasoli, C. P. (2013). Do team and individual debriefs enhance performance? A meta-analysis. Human Factors, 55(1), 231–245. doi:10.1177/0018720812448394