ControlStandard.Tools Get a free report

Glossary

After-Action Review (AAR)

An after-action review is a short, structured debrief that asks four questions: what was supposed to happen, what actually happened, why was there a difference, and what will we change? Originally a US Army practice, it turns experience into improvement — and works best when it's blameless but accountable.

An after-action review (AAR) is a structured way to learn from something that just happened — a project, a launch, an incident — so the lessons actually change what you do next. The format was formalised by the US Army in its doctrine A Leader's Guide to After-Action Reviews (TC 25-20, 1993), and has since spread across business, healthcare and software.

A good AAR answers 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?

Blameless, but accountable

The most common way an AAR fails is by turning into a hunt for who to blame. People stop telling the truth, and the review learns nothing. The fix is to keep it blameless but accountable: separate the question of what in the system let this happen from any question of individual fault, and end with a concrete change that has an owner and a date — otherwise the review is just a conversation.

Turning patterns into improvement

A single AAR fixes one event. The bigger prize is spotting when the same problem keeps recurring — that's a signal the system, not the people, needs changing. Reducing those recurring costs is exactly the drift tax problem, and deciding whether a repeated pain is worth systemising is what the "Should you automate this?" diagnostic helps you judge.

Frequently asked

Is an after-action review the same as a retrospective?
They overlap but aren't identical. A retrospective is the agile ritual a team runs at the end of each sprint to improve how it works together. An after-action review is the broader US Army format applied to any event — a launch, an incident, a project phase — and structures the conversation around four set questions.
Who should run an after-action review?
Ideally someone close enough to understand what happened but neutral enough to keep it blameless. A facilitator who didn't own the outcome can ask the hard questions without the conversation becoming defensive, which is why many teams rotate the role or use a manager from an adjacent team.
When should you hold an after-action review?
Soon enough that memories are fresh, but after the immediate pressure has eased. For a project, run one at the end of each major phase rather than waiting for the finish, so the lessons can change the next phase instead of only the next project.

Related

Term

Pre-Mortem

A pre-mortem is a planning exercise where, before work begins, the team imagines it has already failed and works backwards to explain why. By making it safe to voice doubts up front, it surfaces risks that optimism would otherwise hide — the opposite of a post-mortem held after the damage is done.

 Term

Root Cause Analysis (RCA)

Root cause analysis (RCA) is a structured way to find the underlying cause of a problem — not just its symptoms — so a fix stops it coming back. It uses tools like the 5 Whys, fishbone diagrams and Pareto analysis to move from "what happened" to "why", and ends in a change with a named owner and a date.

 Term

Definition of Done

A definition of done is an agreed, shared checklist of the criteria a piece of work must meet before it counts as finished — not just "code written" but tested, reviewed, documented and shippable. It removes the ambiguity that lets half-finished work get called "done".

 Guide

What Is the Drift Tax? The Hidden Cost of Work That Drifts

The drift tax is the invisible, compounding cost of work that slides sideways while everyone stays busy: rework, chasing, last-minute rescues, missed windows, eroded trust and personal stress. It rarely appears as a line on the P&L, which is exactly why it goes unmanaged — and why it quietly grows.

 Term

Lessons Learned

Lessons learned are the documented insights a team captures during or after a project — what worked, what didn't, and what should change — so the next piece of work benefits from the last. A core project-management practice, recognised by PMI and PRINCE2, it only pays back when a lesson becomes an actual change.

 Term

Just Culture

A just culture is an organisational approach to error that holds people accountable for reckless choices while treating honest mistakes as a signal to fix the system, not the person. Popularised by Sidney Dekker and David Marx, it replaces "who messed up?" with "what let this happen?" — so people report problems instead of hiding them.

← Back to the glossary