After-Action Review Protocol (AAR)

A structured team learning protocol developed by the U.S. Army and adapted for business contexts, conducted immediately after any significant event, project, or milestone. The protocol follows four questions in strict order: (1) What did we intend to happen? — Establish the original plan, objectives, and expected outcomes. This must be stated FIRST, before outcomes are discussed, to prevent hindsight bias from rewriting intentions. (2) What actually happened? — Document the actual outcomes factually. What went right? What went wrong? What was unexpected? (3) Why was there a difference? — Analyze root causes of the gap between intention and reality. Distinguish between factors within the team's control and external factors. (4) What will we do differently next time? — Generate specific, actionable changes. Assign owners and timelines. The AAR should be conducted within 24-48 hours of the event, involve all key participants, be blame-free, and be documented. Critical rule: AARs are learning exercises, not performance evaluations.

When to use it

After any significant event: project completions, product launches, incidents, crises, organizational changes, failed initiatives, and notable successes. After negotiations, presentations, or sales pitches. Weekly during long-running projects. The lower the threshold for triggering an AAR, the faster the team learns.

How it can help

The most proven organizational learning protocol in existence, battle-tested across military and business contexts for decades. The strict separation of 'intended vs actual' prevents the revisionist history that plagues most post-project reviews ('We never expected it to go perfectly'). The 24-48 hour window captures lessons while memory is accurate. Organizations that conduct AARs consistently report significantly fewer repeated mistakes and faster adaptation to changing conditions.