Your Training Partner
Techniques Toolbox
Four steps from left to right: Planned, Actual, Gap and cause, Lesson. Each step carries its question. An orange marker shows the gap between Planned and Actual. A bracket under the first two steps marks a turn round the table. A bracket under the last two marks a group discussion. An arrow leads from Lesson to the lessons-learned register.

After-Action Review

An after-action review (AAR) is a short and structured review. In it, the people who ran an activity compare what was meant to happen with what happened. They look for why the two differ and draw a lesson for next time. According to the PMBOK Guide, the technique comes from the US Army. Four questions drive it in a fixed order. The team records its findings, shares them with the relevant stakeholders and adds them to the project's lessons-learned register.

Goal

An after-action review is a structured review in which the people who ran an activity analyse what happened, why it happened and how to do better. It aims to improve team performance. The PMBOK Guide lists it among the tools of project knowledge management, beside in-progress postmortems and retrospectives.

The review addresses one problem: the team does not know why an activity departed from its plan. When the participants' expectations diverge, the review exposes the weaknesses of the system the team works in. Its findings guide future activities. Before the next comparable activity, the team uses them to decide what it keeps or changes. The AAR findings feed the lessons-learned register, which project knowledge management also produces.

According to the PMBOK Guide, the team usually holds an AAR at the end of a project or after a major milestone. Walker et al. describe a wider use at University College London Hospitals. Teams there hold an AAR after almost any event. The range runs from a five-minute exchange on a treatment that departed from plan to a two-hour review after a department relocation. The length follows the size of the event.

The boundary with lessons learned and the retrospective

Lessons learned takes stock of a project or phase and produces the register that the organisation draws on. The retrospective recurs at every iteration and examines how the team works. The AAR compares the plan and the outcome of a defined activity.

After-action reviewLessons learnedRetrospective
SubjectAn activity or an event: the plan set against the outcomeThe completed project or phaseHow the team works
TriggerEnd of project or milestone according to the PMBOK Guide; almost any event in the hospital practice that Walker et al. describeClose of a project or phaseEnd of each iteration or release
ParticipantsThe people who took part in the activity, as equalsThe team, the sponsor and representatives of the business and of operationsThe whole team
OutputFindings that the team records, shares and adds to the lessons-learned registerLessons-learned register that later projects draw onA few actions, each with an owner and a deadline
The AAR set against lessons learned and the retrospective.

The AAR and lessons learned overlap at closure, since the PMBOK Guide places the AAR at the end of a project or after a milestone. At closure, the question each technique asks is what separates them. The AAR sets a specific intention against its result. Lessons learned reviews the whole project.

Usage

When to use it

  • Milestone or end of project: the point where the PMBOK Guide places the AAR; set the milestone's plan against its result.
  • Event that departed from plan: a go-live, a cutover or a workshop cut short; find the cause of the gap with those who lived through it.
  • Unexpected success: understand what worked so as to repeat it on the next activity.
  • Hierarchical or cross-functional team: going round the table gives everyone the same speaking time, whatever their rank.
  • Distributed team: four questions and a shared document are enough.
  • HERMES project: feed the outcome "Lessons learned" that the team collects throughout the project.

When not to use it

  • Serious incident that requires a formal investigation: run the investigation and a root cause analysis; the AAR complements it without replacing it.
  • Recurring review of the team's process: hold a retrospective at every iteration.

Description

The questions and their order

The PMBOK Guide sets these questions and their order:

  1. What was supposed to happen?
  2. What actually happened?
  3. Why were there differences?
  4. What can we learn?

The first question sets the baseline. The plan can be the usual course of events, the protocol or the participant's own expectation. A review often starts with an account of the facts. The AAR starts with each person's expectation. Walker et al. judge an expectation less emotionally charged than an account of the facts. For that reason the discussion opens more easily. When the answers diverge, the review already holds a finding: the team did not share the same plan.

The second question establishes the facts. Each participant says what they saw from where they stood.

The facilitator opens the third question only once the first two are exhausted. The facilitator then invites the group to explain each gap. If the group discusses causes before it has established the gap, it debates a problem that nobody has described.

The fourth question draws the lesson: what the team will do again and what it will change. The review diagnoses what worked and what failed.

The participants and the facilitator

According to the PMBOK Guide, every team member who took part in the activity takes part in the review. Walker et al. add that all participants take part as equals. In a group, people of higher status speak more often and for longer. The facilitator, whom the article calls the conductor, therefore asks everyone the same questions and gives everyone an equal share of the floor.

Any team member can facilitate an AAR. A formal AAR needs more: a trained facilitator, a private room where everyone can speak without fear, reserved time and equality among all present.

Running the review

  1. Open. The facilitator names the activity under review and restates the four questions. The facilitator gets the group to accept the rules: learning before blame, equal rank, one answer per participant per round.
  2. The plan. The facilitator puts the first question to each participant in turn. Everyone knows they will have the floor.
  3. The outcome. The facilitator puts the second question in the same way.
  4. The gap. Once all the expectations and facts are on the table, the facilitator opens the discussion on the cause of each gap.
  5. The lesson. The facilitator helps the group settle on the best of the proposed solutions. The group decides on the actions that follow.
  6. Record and share. A participant records the findings. The team shares them with the relevant stakeholders and adds them to the lessons-learned register.

What makes an AAR fail

Looking for someone to blame

Walker et al. sum up the technique in one principle: learning comes before blame. A sentence that starts with "who" shuts the discussion down because the person targeted defends themselves and the others fall silent. The facilitator rephrases the sentence as a question about the step: why did the procedure let the error through?

The group follows the first speaker's account

When the line manager answers first, their account of the facts becomes the one the others work from. The others add to it instead of contradicting it. Going round the table prevents this: everyone gives their plan and their outcome before the group debates them.

The lesson with no record and no owner

The PMBOK Guide counts documentation among the features of an AAR. A review without a record benefits only the people present. A lesson that nobody owns enters the register without changing the next activity. Like every recommendation in the lessons-learned register, each lesson names the person who will apply it.

AI considerations

Before the review, a language model reconstructs the timeline of the event from the tickets, the logs and the team's messages. The facilitator uses it to check the facts behind the second question. The timeline shows what the systems recorded. Going round the table yields what the participants expected and what they saw.

After the review, the model sorts the notes under the four questions and drafts the register entries. It flags a finding with no lesson and a sentence that names a person instead of a step. A cause that it proposes remains a hypothesis until the group confirms it.

The PMBOK Guide points out the risks of AI in project knowledge management: unintended exposure of sensitive information and hallucinations. AAR notes name colleagues and describe their mistakes. They are personal data under the Federal Act on Data Protection (FADP). A team that feeds them into an unauthorised external AI service breaks the confidentiality that the frankness of the session depends on.

Examples

An AAR record gives each point one row and takes it from the plan to the lesson. This record covers the cutover of a canton's online building-permit portal.

PlannedActualWhy the gapLessonOwner
Building department: portal back online at 13:00. Operations: portal back online at 15:00.Portal back online at 14:10. The notice to users said 13:00.The cutover plan set no time. Each side worked to its own time.The cutover plan sets the reopening time. The department announces it once operations agree.Project manager
Migration of the 1'840 open applications finished at 11:00.Migration finished at 13:30.The 212 applications with plans over 20 MB migrated one at a time. The trial migration contained none of these applications.The trial migration includes the heaviest applications.Head of operations
Hotline: calls handled within two days.The hotline settled the 27 Monday calls the same day.Two architecture firms reviewed the FAQ during acceptance testing.External users review the FAQ during acceptance testing.Acceptance test lead
Record of the AAR held after the cutover. Each row takes one point from the plan to the lesson.

In the first row, the gap already sits in the Planned column: two reopening times were circulating before the cutover. The third row records a success. The Owner column names the role that applies each lesson.

Visualisations

The facilitator puts the first two questions round the table. The group then discusses the last two.

Planned
What was supposed to happen?
Actual
What actually happened?
Gap
Gap and cause
Why were there differences?
Lesson
What can we learn?
Round the table
Group discussion
Lessons-learned register
The facilitator puts the first two questions to each participant. The group then discusses the gap and the lesson.
Iteration 1
Retro
Iteration 2
Retro
AAR: major milestone
Iteration 3
Retro
Iteration 4
AAR: incident
Retro
Iteration 5
Retro
AAR: go-live
Iteration 6
Retro
AAR: end of project
Lessons-learned register
Closure: lessons learned
The retrospective follows the iteration cadence. The AAR follows milestones, events and the end of the project. The team adds the findings of each AAR to the register that it consolidates at closure.

Cost

PhaseLevelJustification
PreparationLowName the activity under review and bring together those who took part. A formal AAR also needs a trained facilitator, a private room and reserved time.
ExecutionLowThe size of the event sets the length: from five minutes to two hours.
DocumentationMediumRecord the findings, share them and add them to the lessons-learned register in a form that the next project can draw on.

Tools

The review fits on a whiteboard or a flipchart with one column per question. Remotely, a shared document or a digital whiteboard (Miro, Mural) takes the same form during the video call. A five-column record template saves the facilitator from rebuilding the structure at every session.

The team keeps the lessons-learned register in a shared spreadsheet or in the organisation's document space (Confluence, SharePoint), where each AAR record becomes one or more rows. After an operations incident, the team attaches the record to the incident ticket in its incident management tool (ServiceNow, Jira Service Management).

Sources

  • PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th edition, §2.1.6.6 Manage Project Knowledge (figure 2-8): the AAR among the process tools, the lessons-learned register among its outputs, the risks of AI in knowledge management. The After-action reviews (AARs) entry in Section 5 Tools and Techniques: the definition, the origin in the US Army, the timing of the review, the four questions, the diagnosis, documentation and team participation. The In-progress postmortems and Retrospectives entries: the neighbouring techniques.
  • Walker, Andrews, Grewcock, Halligan, "Life in the slow lane: making hospitals safer, slowly but surely", Journal of the Royal Society of Medicine, 105(7), 2012, pp. 283-287: pmc.ncbi.nlm.nih.gov/articles/PMC3407393. The AAR at University College London Hospitals: the questions, the facilitator and the rules set at the opening, the equality of participants, the length from five minutes to two hours.
  • Swiss Confederation, Federal Chancellery, HERMES 2022, Project management module: hermes.admin.ch. The outcome Lessons learned (4.4.1.32) that the team collects throughout the project.
Affinity Map
All techniques
Agile Release Planning