After-Action Reviews: Structured Process for Lessons Learned

PMBOK v8 Definition

After-action reviews (AARs) are a simple, structured process used to analyze what happened, why it happened, and how it can be done better by the participants and those responsible for the project or activity. Originating from the U.S. Army, AARs are designed to improve team performance by reflecting on actions taken and outcomes achieved. The primary goal is to reinforce learning and improve future performance by applying the insights gained from the review.

Why It Matters for the Exam

The PMI exam frequently tests AARs as a key tool for continuous improvement and lessons learned capture. Questions typically appear in the Executing and Monitoring and Controlling process groups, asking you to identify when AARs are conducted, what their structure is, and how they differ from other review techniques like postmortems or inspections.

Key Points to Remember (for the exam)

Main Purpose: Analyze what happened, why it happened, and how to do better
When Conducted: At the end of a project OR after significant milestones
Core Participants: All team members involved in the project participate
Four Key Questions (MEMORIZE THIS):
1. What was supposed to happen?
2. What actually happened?
3. Why were there differences?
4. What can we learn?
Primary Goal: Reinforce learning and improve future performance
Key Distinction: AARs are participant-driven (team members analyze their own work), not imposed by external auditors
Output: Captured lessons learned that inform future activities

Typical PMI Exam Example

Your project team just completed a major software release. The project manager schedules a two-hour meeting where the team discusses what was planned versus what actually occurred, identifies root causes for schedule variances, and documents recommendations for the next sprint. This is an After-action review because it follows the structured four-question format and involves all team members in the diagnostic process.

PMI Exam Traps

Trap: Confusing AARs with Postmortems Reality: AARs can be conducted periodically throughout the project (after milestones), while postmortems are typically held only at project end. PMBOK v8 distinguishes "In-progress postmortems" as periodic reviews, but AARs are specifically structured around the four key questions.
Trap: Thinking AARs are only for failed projects Reality: AARs analyze both successes and failures. The focus is on understanding differences between what was supposed to happen and what actually happened, regardless of whether the outcome was positive or negative.
Trap: Confusing AARs with Inspections Reality: Inspections examine work products against documented standards (conformance checking). AARs examine team performance and processes through structured reflection and team discussion.
Trap: Believing AARs require external facilitators Reality: AARs involve all team members who participated in the project. The review is conducted by the participants themselves, not by external quality auditors.

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Lessons Learned	Direct output of AARs	AARs are a primary method to capture lessons learned; lessons learned are documented and applied to future projects
Continuous Improvement	Primary goal	AARs feed into organizational process assets and improve future project performance
In-progress Postmortems	Similar technique	Both are periodic reviews, but AARs follow the specific four-question structure; postmortems may be less structured
Affinity Diagram	Complementary tool	Affinity diagrams can organize causes of defects identified during AARs into groups for focused analysis
Diagnostic Process	Core component	AARs include a diagnostic process to understand why differences occurred between planned and actual results

Quick Review Questions

A project manager wants to capture lessons learned after each sprint in an agile project. Which technique should be used, and what are the four key questions it asks?
During an after-action review, the team discovers that actual costs were 30% higher than planned. Which of the four AAR questions is the team answering when they investigate the root causes of this variance?
A new project manager schedules an AAR but only invites the project sponsor and key stakeholders. Is this correct according to PMBOK v8? Why or why not?
What is the primary difference between an after-action review and an inspection?
After completing a project milestone, the team conducts an AAR and identifies several improvements. Where should these findings be documented, and how should they be used?

PMBOK v8 Reference

Section 4.6.2.2 - Data Gathering and Analysis: After-action reviews (AARs)