Complete firstCompleted event
The event is over or the reviewed segment has a clear end.
Interrupting active work can distort the account and leave facts provisional.
Method guideOperations
After-Action Review
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityLow
Time20-45 min
Participants3-12
FormatWorkshop + async
MaturityEstablished
01
Prerequisite
What needs to be finished first
Complete firstParticipation and sufficient facts
Participants and available records can reconstruct the sequence together.
Memory alone is not enough to explain differences.
02
Preparation
What needs to be ready before start
Materials
Goal or plan, timeline data and relevant work records; a safe conversation space, facilitator, and shared notes.
People / roles
Facilitation keeps the questions clear and invites participation. Participants reconstruct events. A recorder captures lessons, actions, owners, and a later review.
Pre-read
Gather the goal, plan, timeline, decisions, and observable facts. Mark uncertainty explicitly.
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.
03
Core question
The one question this method answers
What was meant to happen, what actually happened, what can we learn, and what should we change or sustain?
04
Flow
Phases with goal, actions, output and pitfall
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.
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
- 1
Intent
Clarify the goal and boundary
Goal
The group shares the intent and period being examined.
Inputs for this step
- Plan, goal, context
Actions
- Read out facts and the standard
- confirm participants and a safe setting.
Output
Shared starting point
Without a clear expectation, differences are hard to interpret.
Quality check
The review opens with general opinions about the event.
Pitfall
The expected execution or review boundary is unclear. Make the goal and time period concrete.
Timing: 4–6 minutes
- 2
Sequence
Reconstruct actual events
Goal
The group has a shared picture of what happened.
Inputs for this step
- Timestamps, records, participant perspectives
Actions
- Collect a factual sequence
- mark unknown facts
- do not explain causes prematurely.
Output
Evidence-based timeline
A plausible explanation is not yet a verified event.
Quality check
Memories conflict and are judged immediately.
Pitfall
The timeline and memory are mixed without checking sources. Name sources and leave open facts visible.
Timing: 5–8 minutes
- 3
Compare
Contrast intent and reality
Goal
Differences and helpful conditions become visible.
Inputs for this step
- Shared intent and timeline
Actions
- Record specific differences
- label expectations as intended and events as actual
- include successful steps.
Output
Comparison with differences
A difference is a learning prompt, not personal blame.
Quality check
Discussion jumps from a difference to an accusation.
Pitfall
Differences are attributed to people instead of work conditions. Ask which work conditions and information mattered.
Timing: 5–8 minutes
- 4
Learn
Check conditions and lessons
Goal
Lessons relate to work and evidenced conditions.
Inputs for this step
- Comparison, causal hypotheses, evidence
Actions
- Ask about relationships
- allow several contributing factors
- distinguish facts, hypotheses, and unknowns.
Output
Lessons and open questions
A single explanation can miss systemic or situational conditions.
Quality check
The first explanation is accepted as the cause.
Pitfall
A plausible explanation is treated as an evidenced cause. Look for evidence or label the statement as an open hypothesis.
Timing: 5–10 minutes
- 5
Adapt
Set actions and a later check
Goal
Learning is tried in the next comparable event.
Inputs for this step
- Lessons, owners, follow-up event
Actions
- Write small observable actions
- assign owners and dates
- schedule the next review.
Output
Improvement plan
An action without a later check has no measured effect.
Quality check
The action list grows too long or lacks owners.
Pitfall
Sorted tasks receive no owned action. Prioritize a few feasible actions and check them later.
Timing: 4–7 minutes
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Review record with event and intent, expected and actual course, evidenced conditions, lessons, concrete actions, owners, and a later effectiveness check.
Versioning / ownership
Save date, reviewed period, sources, open factual questions, and actions. Revisit outcomes in the next comparable event.
Tool alternatives
- Event timeline and activity log
- Whiteboard for intended and actual sequence
- Action list with owner, date, and later check signal
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.
Prepare for the work steps
Intent: Clarify the goal and boundary
- Plan, goal, context
Sequence: Reconstruct actual events
- Timestamps, records, participant perspectives
Compare: Contrast intent and reality
- Shared intent and timeline
Learn: Check conditions and lessons
- Comparison, causal hypotheses, evidence
Adapt: Set actions and a later check
- Lessons, owners, follow-up event
Review record in five sections
Goal and plan
What should happen, by when, and with what expected result? Bound the period under review.
...
Actual sequence
Which observable events, decisions, and dates are supported? Mark what is unknown.
...
Comparison and conditions
What differed from the plan? Which helpful or difficult conditions are supported by sources?
...
Lessons and hypotheses
What should we sustain or change? Which explanation is evidenced, and which still needs a check?
...
Actions and later check
Which few changes have an owner, date, and observable signal in a relevant future event?
...
Blank worksheet: keep the prompts and record your own facts, observations, and actions. The fictional example is not copied over.
U.S. Army, NTC EXOP Annex A: After Action Review Standards, adapted for civilian work
Intent: Clarify the goal and boundary
Expected artifact: Shared starting point
Without a clear expectation, differences are hard to interpret.
Entry:
...
- The review opens with general opinions about the event.
Sequence: Reconstruct actual events
Expected artifact: Evidence-based timeline
A plausible explanation is not yet a verified event.
Entry:
...
- Memories conflict and are judged immediately.
Compare: Contrast intent and reality
Expected artifact: Comparison with differences
A difference is a learning prompt, not personal blame.
Entry:
...
- Discussion jumps from a difference to an accusation.
Learn: Check conditions and lessons
Expected artifact: Lessons and open questions
A single explanation can miss systemic or situational conditions.
Entry:
...
- The first explanation is accepted as the cause.
Adapt: Set actions and a later check
Expected artifact: Improvement plan
An action without a later check has no measured effect.
Entry:
...
- The action list grows too long or lacks owners.
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/after-action-review/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
after-action-review-beispiel.md
Concrete filled scenario, fictional example
Fictional teaching example: delayed start of a booking test
All participants, dates, and causes are invented. A small team planned to start testing its booking confirmation on October 5. Testing began on October 9.
What was supposed to happen? Privacy review by October 3, then a test with two people.
What actually happened? The text was ready. The privacy review had no confirmed owner and was scheduled only after a reminder. The first two tests happened four days later.
What worked or hindered the work? The task list revealed the missing review step but had no owner field. A fictional message and calendar entry support the timeline. The cause remains an open explanation, not a proven single cause.
What will we change or sustain? Sam adds an owner and planned review window to the release checklist. Before the next test, the team checks whether all review steps are assigned and scheduled. The review does not rate individual team members.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Clarify the goal and boundaryThe expected execution or review boundary is unclear.View in phase
- Reconstruct actual eventsThe timeline and memory are mixed without checking sources.View in phase
- Contrast intent and realityDifferences are attributed to people instead of work conditions.View in phase
- Check conditions and lessonsA plausible explanation is treated as an evidenced cause.View in phase
- Set actions and a later checkSorted tasks receive no owned action.View in phase
Trap
Clarify the goal and boundary
Symptom
The expected execution or review boundary is unclear.
What to do
Make the goal and time period concrete.
Trap
Reconstruct actual events
Symptom
The timeline and memory are mixed without checking sources.
What to do
Name sources and leave open facts visible.
Trap
Contrast intent and reality
Symptom
Differences are attributed to people instead of work conditions.
What to do
Ask which work conditions and information mattered.
Trap
Check conditions and lessons
Symptom
A plausible explanation is treated as an evidenced cause.
What to do
Look for evidence or label the statement as an open hypothesis.
Trap
Set actions and a later check
Symptom
Sorted tasks receive no owned action.
What to do
Prioritize a few feasible actions and check them later.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
The event is active or people are in danger: handle safety, operations, and required reporting first.
Intent and actual course cannot be reconstructed: gather sources and mark uncertainty.
Discussion assigns blame: return to observable work conditions and decisions.
An explanation is declared a cause without evidence: mark it as a hypothesis and plan a factual check.
Lessons create no change: agree a few actions with owners, dates, and a later effectiveness check.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.