methodatlas
Operations

After-Action Review

Turns workflows, data, causes, and improvements into a tangible result through naming objectives, describing actual execution, and defining actions.

Core question
What was intended, what actually happened, why were there gaps, and what should the team do next time?
LowWorkshop + async20-45 min
Open runsheetEstablish practiceStart comparison
Purpose

The method helps clarify workflows, data, causes, and improvements concretely. It identifies patterns, causes, bottlenecks, and weaknesses and derives actions. The outcome is captured as lessons learned, action items, and event summary.

How it works

The team follows the steps: name the objective, describe actual execution, explain deviations, gather lessons, and define actions. Each step is captured visibly. At the end, lessons learned, action items, and an event summary are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

After-Action Review · AAR Learning BoardPlan, Realität, Abweichung, Lernen und nächste Anpassung sichtbar verbinden
After Action Review Learning BoardDie Skizze zeigt ein Review Board, das geplante Absicht, tatsächlichen Verlauf, Abweichung, Lessons und nächste Actions verbindet.Lernen direkt aus dem Ereignis sichernKurz vergleichen, was geplant war, was wirklich geschah und welche Anpassung folgt.Event SummaryZiel, Kontext und beobachtetes Ergebnis in einem kurzen gemeinsamen Review festhalten.PlanWas war beabsichtigt?RealityWas ist passiert?LearningWas lernen wir daraus?GapAbweichungZielPlanIstFaktenLessonMusterActionsNächste AnpassungOwner setzenPlaybook ändernKeepWas beibehalten?ChangeWas anpassen?TryWas testen?

Flow

  1. 1Name objective
  2. 2Describe actual execution
  3. 3Explain deviations
  4. 4Gather lessons
  5. 5Define actions

The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Project closeout
  • Incident learning
  • Team learning

Not good for

  • Strategic long-form debates
  • Performance reviews

Deep dive

In detail

After-action review follows a clear working logic: name the objective, describe actual execution, explain deviations, gather lessons, and define actions. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. The result is lessons learned, action items, and event summary that makes decisions, learning, or further planning actionable.

Facilitation

Prepare a clear focus question, the right information, and a visible workspace. Plan about 20-45 minutes with 3-12 people and use the format in a workshop or asynchronously. The facilitation stays lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions help.

Output artifacts
Lessons learnedAction itemsEvent summary
Tags
learningoperationsimprovement

Sources

After (film series) - Wikipediaen.wikipedia.org
Artifact templates
After-Action Review Working TemplateCompact working template for After-Action Review with context, input, output artifacts, and next step.
markdown

after-action-review-working-template.md

Compact working template for After-Action Review with context, input, output artifacts, and next step.

After-Action Review Working Template

Goal

A short review of what was intended, what happened, and why.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Lessons Learned:
  • Action Items:
  • Event Summary:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

Sprint Retrospective

Statt After-Action Review, wenn ihr Teamarbeit am Ende eines Sprints strukturiert reflektieren wollt.

Similar methods

All methods
Operations
Learning Review

Turns workflows, data, causes, and improvements into a tangible result by clarifying scope and stance, reconstructing the timeline, and deriving learning actions.

Operations
Fishbone Diagram

Turns workflows, data, causes, and improvements into a tangible result by defining the problem, choosing cause categories, and prioritizing likely causes.

Agile
Sprint Retrospective

Turns sprint backlog, sprint execution, and team flow into a tangible result through reflecting on the sprint, collecting positives and challenges, and carrying actions into the next sprint.

Statt After-Action Review, wenn ihr Teamarbeit am Ende eines Sprints strukturiert reflektieren wollt.

Operations
Accountability Ladder

Turns workflow, data, causes, and improvements into a tangible result by describing the situation, identifying the current accountability level, and agreeing on follow-up.

Operations
Gemba Walk

Turns workflows, data, causes, and improvements into a tangible result by selecting a process, going to the place of work, and recording improvements.

Operations
Root Cause Tree Analysis

Clarifies workflows, data, causes, and improvements by framing the problem precisely, branching possible causes, and defining countermeasures.