After-Action Reviews (AARs): Structured Process for Lessons Learned

After-Action Reviews (AARs): 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. The primary goal is to reinforce learning and improve future performance by applying the insights gained from the review. AARs are typically conducted at the end of a project or after significant milestones to capture lessons learned and inform future activities.

Why It Matters for the Exam

The PMI exam frequently tests AARs in questions about continuous improvement, lessons learned, and team performance domains. Questions appear in situational scenarios where you must identify the correct tool for capturing knowledge after project phases or at project closure. The structured four-question format is a common memorization point.

Key Points to Remember (for the exam)

  • Main Purpose: Reinforce learning and improve future performance by applying insights gained from the review
  • When Conducted: At the end of a project OR after significant milestones
  • Key Tool: Four structured questions (memorize these exactly):
    • What was supposed to happen?
    • What actually happened?
    • Why were there differences?
    • What can we learn?
  • Participant Involvement: ALL team members involved in the project participate in the review
  • Diagnostic Process: Diagnoses what went well AND what did not, identifying both strengths and weaknesses
  • Documentation: Findings are documented and shared with relevant stakeholders to ensure valuable lessons are captured and disseminated
  • Common Confusion: AARs are NOT the same as performance reports—AARs focus on learning and improvement, not status reporting

Typical PMI Exam Example

A project team completes a major milestone in a software development project. The project manager schedules a meeting where all team members gather to answer four questions: What was supposed to happen? What actually happened? Why were there differences? What can we learn? The findings are documented and shared with stakeholders.

Question: What tool is the project manager using? Answer: After-action review (AAR)

PMI Exam Traps

  • Trap: Confusing AARs with lessons learned register updates

    • Reality: AARs are the STRUCTURED PROCESS that PRODUCES lessons learned; the register is where they are stored
  • Trap: Thinking AARs are only conducted at project closure

    • Reality: AARs are conducted at the end of a project OR after significant milestones
  • Trap: Assuming only the project manager conducts the review

    • Reality: ALL team members involved in the project participate
  • Trap: Confusing AARs with root cause analysis

    • Reality: AARs use four structured questions focused on learning and improvement; root cause analysis is a different diagnostic technique

Important PMI Connections

Related ConceptRelationship TypeExam Attention Point
Lessons Learned RegisterOutput of AARsAARs produce lessons learned that are documented and shared
Continuous ImprovementPrimary GoalAARs are a tool for continuous improvement in project management
Project ClosureTimingAARs are conducted at project end or after milestones
Stakeholder EngagementDocumentation & SharingFindings are shared with relevant stakeholders

Quick Review Questions

  1. What are the four questions asked during an After-action review?

  2. When should an After-action review be conducted during a project?

  3. Who participates in an After-action review?

  4. What is the primary goal of conducting After-action reviews?

  5. What must happen to the findings from an After-action review?

PMBOK v8 Reference

Section 2.4.2 - Data Gathering and Analysis (After-action reviews) and related content on continuous improvement and lessons learned processes.