The After-Action Review

Experience is the most expensive teacher an organization employs, and most organizations pay the tuition and skip the class. The project ships, the incident ends, the launch lands or doesn’t — and everyone rushes to the next thing, carrying away private lessons that contradict each other and improve nothing shared. The after-action review is the class: a short, structured conversation, held soon after the event, that converts one team’s experience into the whole team’s knowledge. It asks four questions and insists on honest answers. That is the entire technology — and its rarity in civilian work life is one of management’s stranger economies.

Four questions, in order

The sequence is the discipline. What was supposed to happen? — the intention, stated as it was understood at the time, not as it has since been edited by hindsight. What actually happened? — the record, built from facts and artifacts before anyone interprets them. Why the difference? — the analysis, where causes are separated from symptoms and luck, good and bad, is named as luck instead of being promoted to strategy or demoted to excuse. And what will we do differently — sustain what worked, change what didn’t, in decisions specific enough to be checked next time. Skipping order is how reviews fail: teams that jump to lessons are arguing from incompatible versions of what occurred. The first two questions feel slow. They are what make the last two worth anything.

No blame is a method, not a mood

The review’s famous ground rule — no blame — is usually described as kindness. It is actually epistemology. The moment participants expect the review to be a tribunal, they start defending instead of reporting, and the facts — the entire raw material of learning — are the first casualty. Rank gets checked at the door for the same reason: the person closest to the work usually holds the fact that matters most, and they will not offer it into a room where seniority outranks evidence. This does not mean accountability vanishes; it means it lives in its proper place, in follow-up decisions, not in the inquiry itself. Critical thinking, turned on your own operation, is the precise description of the posture: claims tested against the record, alternative explanations entertained, the story we would prefer audited hardest of all.

Short, soon, and written down

The practical fences are unglamorous. Soon — while memory is still evidence rather than narrative; a review six weeks later studies what people now believe happened. Short — the discipline of four questions fits in an hour for most events, and the constraint keeps the review a habit instead of a production. Written — briefly: the intention, the record, the one or two changes adopted, kept where the next team starting similar work will actually find them, because a lesson filed where nobody looks is tuition paid twice. And selective — review the significant and the surprising, successes as well as failures, because an unexamined success teaches a team to repeat its luck as if it were skill. Run this way, the after-action review compounds quietly: each event makes the next one cheaper to run and easier to read. That compounding is the closest thing operations have to wisdom — and it costs an hour.

Choose your first one well: a finished piece of work with real stakes, a mixed result, and a team willing to be honest for an hour. Run the four questions in order, protect the facts from the verdicts, and end with exactly the changes you can name an owner for. A single review run properly makes the case for the habit better than any policy memo — because the team leaves the room knowing something true that it did not know when it entered.

You have already paid for the experience. Hold the review, and collect the education.

← All Insights