After-Action Reviews: Turn Experience Into Better Performance
After-action reviews give teams a structured way to extract clear lessons from completed work, so the same mistakes stop compounding across projects and futu…
Topic: Operations & Continuous Improvement
Why It Matters
Teams will often finish a project, hand over the deliverable, and move straight to the next one. The knowledge gained in that process (what worked, what did not, and why) evaporates within days.
The next time a similar challenge appears, the team starts from scratch: making the same misjudgements, running into the same friction points, and relearning lessons that were already earned the hard way.
An after-action review creates a structured pause at the end of a piece of work to extract those lessons while they are still fresh. It is a short, facilitated conversation built around four straightforward questions: what did we plan to do, what actually happened, why was there a difference, and what should we do differently next time. The result is not a report that sits in a shared drive. It is a direct input to how the team works going forward.
After-action reviews are used across teams at every scale, from a small project group debriefing a client pitch to a cross-functional leadership team reviewing a product launch. The format is consistent, but the value compounds over time. Teams that use them regularly develop a shared language for improvement and a culture where honest reflection is expected rather than avoided.
Ask yourself the following questions. If any of them apply, an after-action review may be worth running.
Have you just completed a project where the outcome was not quite what you expected, either better or worse?
Does your team tend to repeat similar problems across different projects?
Are you about to start a new initiative that closely resembles something you have done before?
Origin and Underlying Logic
The after-action review was developed by the United States Army in the 1970s as a tool for debriefing military exercises. The intent was straightforward: create a repeatable mechanism for extracting learning from experience, regardless of whether the outcome was a success or a failure.
It has since been adopted widely in corporate environments, healthcare, emergency services, and consulting, where the same need exists. Work generates knowledge, but that knowledge is lost without a structured way to capture it.
The underlying logic is simple. Performance improves when feedback loops are short and specific. An after-action review shortens the loop between completing a task and understanding it clearly. It also makes feedback collective rather than individual, which shifts improvement from a personal habit to a team norm.
The approach sits within the broader tradition of experiential learning, associated with thinkers such as David Kolb, who argued that experience alone does not produce learning. Reflection on experience does. The after-action review operationalises that principle in a format that works inside a busy organisation.
Related frameworks include the retrospective (common in agile software development), lessons-learned reviews (used in formal project management), and the plan-do-check-act cycle used in quality management.
Structure and Application
The after-action review is built around four questions, asked in sequence. Understanding why each question exists helps a facilitator draw out genuinely useful answers rather than surface-level responses.
Question 1 asks what the team planned to do. This sets a clear baseline and removes ambiguity about what success was supposed to look like. Without it, the debrief risks sliding into vague impressions rather than a comparison against intent.
Question 2 asks what actually happened. This is a factual account, not an evaluation. The facilitator's role here is to keep the discussion grounded in observable events rather than interpretations.
Question 3 asks why there was a gap between plan and outcome. This is where most of the analytical value sits. A good after-action review does not stop at "the timeline slipped." It asks why the timeline slipped, and then why that cause occurred, moving toward a root explanation rather than a symptom.
Question 4 asks what the team would do differently next time. This is the output: a short, specific list of changes to process, approach, or preparation that the team commits to carrying forward.
The format is typically a facilitated discussion lasting 45 to 90 minutes, depending on the complexity of the work being reviewed. It works best with a neutral or semi-neutral facilitator, a clearly defined scope (one project or one phase, not a sweeping review of everything), and a commitment from participants to be specific rather than diplomatic.
An after-action review can be run at multiple levels: individual (after a presentation or negotiation), team (after a project or sprint), or organisational (after a major programme or change initiative). The questions remain the same; the depth of analysis scales with the stakes.
Quick-start: Before your next team meeting, identify one recent piece of work that produced an unexpected result and block 60 minutes with the people who were closest to it. Bring the original plan or brief as your baseline. Running just the first two questions (what we planned, and what happened) will surface gaps that the deep dive below shows you how to turn into lasting improvement.
FAQ
The following questions address what managers most commonly ask when they first encounter this format.
Q: What is an after-action review?
A: An after-action review is a structured debrief used by teams to examine what happened during a piece of work, why it happened, and what to change next time. It follows four core questions in sequence, moving from what was planned through to specific improvement commitments. The format originated in the US Army and has been widely adapted for business teams across sectors.
Q: How is an after-action review different from a retrospective?
A: The two formats share the same intent (learning from experience) but differ in context and structure. Retrospectives are most commonly used in agile software development and follow a fixed cadence, typically at the end of a sprint. After-action reviews are used more broadly, can be triggered by any completed piece of work, and are more explicitly tied to a plan-versus-outcome comparison. In practice, many teams use the terms interchangeably.
Q: How long does an after-action review take?
A: Most after-action reviews run between 45 and 90 minutes. Shorter sessions work for smaller, more contained pieces of work; more complex projects may need longer. The key constraint is focus: reviews that try to cover too much ground in a single session lose specificity and produce generic conclusions.
Q: How do I know if an after-action review is right for my team?
A: The format is most useful when your team has just completed a discrete piece of work with a defined goal, when there was a meaningful gap between what was expected and what happened, or when you are about to repeat a similar type of work and want to carry forward what you learned. It is less useful as a general team health check or for reviewing work that is still in progress.
Q: Do after-action reviews only work when something goes wrong?
A: No, and this is one of the most common misconceptions. Some of the most valuable after-action reviews follow successful outcomes, because they identify what specifically drove the success (rather than attributing it to general team effort) and make it repeatable. Reviewing what went well is as important as reviewing what did not.