Practice knowledge base
After-Action Review
A short debrief after a project, incident, or iteration helps the team understand what was expected, what actually happened, and what conclusions to reinforce.
Documentation sections
What it is
An After-Action Review is a short meeting held right after a significant event: a release, failure, project, or work iteration. The team compares the plan with the facts, separates good decisions from luck, and records what to change in the process. The practice is useful where learning on the fly is important, rather than waiting for a big retrospective every few months.
When it helps
- The team repeats the same mistakes after projects or incidents.
- After complex work, conclusions stay in verbal discussions and are quickly lost.
- Participants have different understandings of why the result deviated from expectations.
- The manager needs to calmly analyze a failure without looking for someone to blame.
- There are unclear steps in processes that only become apparent after the work is done.
How to start
- 1 Pick a recent event where facts already exist: a project, release, incident, or completed iteration.
- 2 Assign a facilitator who will keep the discussion focused on four questions: what was expected, what happened, why, and what we will change.
- 3 Hold the meeting soon after the event while participants still remember the details.
- 4 Record 1–3 specific process changes, an owner for each change, and where they will be stored.
- 5 Check in the next similar piece of work whether the team and manager applied the recorded conclusions.
Expected effect
The team turns experience into changes to working rules faster: decisions, owners, and lessons are not left in individuals' memory. The manager gets a calm review format where facts are separated from judgments, and the next step is clear.
Common pitfalls
- Turning the review into a blame game: then people hide details, and the team loses facts.
- Holding the meeting too late, when participants have already forgotten key decisions and constraints.
- Recording a long list of conclusions without owners and without checking in the next piece of work.
- Discussing only mistakes and not noticing solutions that are worth repeating.
- Using the practice for every little thing: the team will start to see it as an unnecessary meeting.
Further reading
- Documentation: U.S. Army, After Action Review guidance
- Book: Peter Senge, The Fifth Discipline
- Book: Chris Argyris and Donald Schon, Organizational Learning
FAQ
Who should facilitate such a review?
Usually the meeting is led by the team manager, a project lead, or a neutral facilitator. It is important that the facilitator keeps the conversation on facts, decisions, and next steps, rather than defending their own position.
Can we start without a consultant?
Yes. For the first meeting, four questions, a list of the event's participants, and a place where the team records decisions are enough. Outside help is needed only if there are strong conflicts or if reviews consistently turn into accusations.
How much time should be allocated?
For a small event, a short meeting is usually enough. For a large project or a serious incident, it is better to limit the agenda to key decisions in advance, otherwise the discussion will sprawl and won't yield concrete changes.
How can we tell if the practice is working?
Check whether specific changes in rules, templates, checklists, or responsibilities appear after the review. If conclusions exist only in the minutes but don't affect the next piece of work, the format needs to be simplified.