After Action Review

A structured debrief methodology developed by the U.S. Army, built around four questions: (1) What was supposed to happen? (2) What actually happened? (3) Why was there a difference? (4) What will we do differently next time? The power is in the structure: by separating intention from reality, then diagnosing the gap before jumping to solutions, the AAR prevents both blame and premature fixing. It works because it makes learning systematic rather than accidental.

When to use it

After any significant project, milestone, or event—successes AND failures; after decisions with unexpected outcomes; at regular intervals during long-running projects; whenever a team keeps making similar mistakes.

How it can help

The simplest and most effective learning ritual a team can adopt. Run a 30-minute AAR after every significant project, launch, meeting, or decision. The key discipline is asking 'what actually happened' before 'why'—most teams skip straight to blame or solutions. Write down the lessons and make them accessible. Teams that do AARs consistently learn 3-5x faster than teams that don't, because they convert experience into transferable knowledge.