Operations Operating practice

After-Action Review

An After-Action Review compares the expected and actual course of work and derives concrete learning and improvement actions.

An After-Action Review reconstructs a completed activity against its goal, plan, and actual course. The group examines differences, helpful conditions, and opportunities to improve. Discussion focuses on the work and its conditions, not personal blame. The outcome is a set of actions to check in a comparable future situation.

Core question

What was meant to happen, what actually happened, what can we learn, and what should we change or sustain?

Plan an After-Action Review Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 3-12
Time: 20–45 minutes after the event

Keep intent, actual events, explanations, and next changes distinct. The review is for learning, not individual performance rating.

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.

Intent
Clarify the goal and boundary
Describe the event, expected result, plan, and review boundary.
Sequence
Reconstruct actual events
Order observed events and decisions over time. Separate records, memory, and uncertainty.
Compare
Contrast intent and reality
Compare expected and actual results, handoffs, and timing.
Learn
Check conditions and lessons
Explore which decisions, information, or conditions contributed to outcomes.
Adapt
Set actions and a later check
Choose a few changes or practices to sustain and set owners, dates, and effectiveness checks.

Track agreed actions in the next relevant run. Show what to sustain, change, or investigate further.

A good fit when

Use an After-Action Review after a completed exercise, delivery, project phase, or managed event when participants can learn together.

Ideal for

Project closeout
Incident learning
Team learning

Not good for

Strategic long-form debates
Performance reviews

Outputs

Shared event account
Intent, timeline, differences, and uncertainty.
Improvement plan
A few lessons with owners, dates, and later review.

Review record in five sections

Fictional teaching example

Fictional review of a delayed booking test, separating intent, sequence, conditions, and actions.

Goal and plan

What should happen, by when, and with what expected result? Bound the period under review.

Fictional: Test the booking confirmation with two people from October 5; privacy approval by October 3.

Actual sequence

Which observable events, decisions, and dates are supported? Mark what is unknown.

Fictional: The text was ready. The review had no confirmed owner; testing began on October 9.

Comparison and conditions

What differed from the plan? Which helpful or difficult conditions are supported by sources?

Fictional: Four-day delay. The task list showed the review but no owner field. The cause remains open.

Lessons and hypotheses

What should we sustain or change? Which explanation is evidenced, and which still needs a check?

Fictional: Complete review steps help; an explicit assignment may improve planning. Hypothesis.

Actions and later check

Which few changes have an owner, date, and observable signal in a relevant future event?

Fictional: Sam adds an owner and review window. Before the next test, check that every review step is scheduled.

The Army guide structures a review around intended execution, actual events, assessment, and next improvement. This civilian blueprint adds evidenced work conditions, actions, and a later effectiveness check; it is not military operating guidance.

U.S. Army, NTC EXOP Annex A: After Action Review Standards, adapted for civilian work

First step

Choose one completed event and a clear learning purpose. During an active threat, protect people and operations and follow required reporting first.

Open the method guide

Where to go next?

Operations

5 Whys

Digs into a named gap between plan and actual course to its root.

DevOps

Blameless Postmortem

Deepens a technical event from the review systemically.

Deep dive

Purpose

After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.

How it works

A shared picture of the situation reconstructs the course from memory and facts and sets expectation against reality. Differences are read as mechanisms at work rather than individual mistakes. This produces concrete changes in behavior and process that get checked again at the next similar case.

In detail

An After-Action Review turns lived practice into shared learning without getting lost in justifications. The process needs a clear separation of plan, actual course, and causes so differences aren't explained away prematurely. The value comes when lessons turn into concrete behavior or process changes and get checked again at the next similar case.

Facilitation

Before the conversation, gather expectation, actual course, and the key facts from the event so memory doesn't dominate everything. The productive moment comes when differences between plan and reality become legible as patterns rather than personal weakness. Close with a few behavior changes to apply deliberately at the next similar case.

The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Learning Operations Improvement

Sources

Annex A: After Action Review Standards - National Training Center EXOPhome.army.milOffizieller Army-Leitfaden: vier Kernfragen zu Erwartung, tatsächlichem Verlauf, Bewertung und nächstem Vorgehen; betont Fakten, Lernen und offene Diskussion.Training Management Directorate publishes training circular - U.S. Armyarmy.milErgänzende Army-Quelle zur institutionellen Anwendung von AARs als Trainings- und Lernpraxis.

In playbooks

Improve the Deployment and Platform FlowMove from a simulated outage through practiced incident response to a documented, improved learning loop.

Artifact templates

After-Action Review: WorksheetPlan a protected review of a completed event with an intent, timeline, and follow-up.

markdown

after-action-review-working-template.md

Plan a protected review of a completed event with an intent, timeline, and follow-up.

After-Action Review: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Review one event together Time: 20–45 minutes after the event; investigation and implementation are additional

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Goal or plan, timeline data and relevant work records; a safe conversation space, facilitator, and shared notes.
Roles: Facilitation keeps the questions clear and invites participation. Participants reconstruct events. A recorder captures lessons, actions, owners, and a later review.
Advance information: Gather the goal, plan, timeline, decisions, and observable facts. Mark uncertainty explicitly.
Overall time needed: 20–45 minutes for a bounded review. Deep investigation, formal incident reports, and implementation take additional work.
Setup: Start with four questions: What was supposed to happen? What actually happened? What worked or hindered the task, and why? What will we change next time? Compare the plan and event before explaining causes. Ask open questions, separate facts from hypotheses, and finish with a few owned actions. Army doctrine is the historical reference; adapt the process and language to civilian contexts.