Use an After-Action Review (AAR) for debriefing a project, program, or other initiatives. Some call an After-Action Review a Hot Wash, an After-Action Debriefing, a Look Back, or a Postmortem, among others. In the Agile community, some call it a Retrospective. Above all, an AAR is reflected by those involved to learn what happened so that we can improve future performance.

Purpose of an After-Action Review Meeting, aka Hot Wash or Look Back or Retrospective

An After-Action Review (frequently called a Hot Wash) is NOT intended to critique, grade success, or failure. Rather, it identifies weaknesses that need improvement and strengths that might be sustained.

An After-Action Review answers four “learning culture” questions:

1. (Purpose) What was supposed to happen?
2. (Results) What did happen?
3. (Causes) What caused the difference?
4. (Implications) What can we learn from this?

The After-Action Review provides a candid discussion of actual performance results compared to objectives. Hence, the engagement participants contribute their input and perspective. They provide their insight, observation, and questions that help reinforce strengths and identify and correct the deficiencies of the completed project or action.

Learning cultures highly value collaborative inquiry and reflection. Therefore, the U.S. Armed Forces use After-Action Reviews extensively, relying on a variety of means to collect hard, verifiable data to assess performance. The U.S. Army refers to the evidence as “ground truths.”

Participants identify mistakes they made as well as mistakes made by others. They prohibit any other use of candid discussions, including performance reviews.

Focus on WHAT can be learned, not WHO can be blamed.

The U.S. Army’s approach may use five basic guidelines that govern its After-Action Reviews, namely:

Guidelines for an After-Action Review Event, Meeting, or Workshop 

1. Call it as you see it
2. Discover the “ground truth”
3. No sugar coating
   

   After Action Review Focuses on Listening

4. No thin or thick skins
5. Take thorough notes

After-action reviews value openness, candor, and frankness. Not many groups open up and provide complete candor, but you should encourage full disclosure. Participants identify mistakes they made as well as observations about others. Discourage or prohibit any other use of confidential discussions, such as supporting performance evaluations.

An After-Action Review workshop typically takes from a partial day to an entire week. It may include twenty to thirty people or more, but not necessarily everyone at once. Hence, participation varies throughout the workshop.

Agenda for an After-Action Review Event, Meeting, or Workshop

 

• Introduction

Begin with the MGRUSH introduction and emphasize the project objectives and expected impact of the project on the organizational holarchy. Carefully articulate and codify key assumptions or constraints.

 

• Success Objectives

Results are compared to the SMART objectives. Items that worked or hampered provide input for later discussion. Be immediately cautious about scope creep. Questions that may be out-of-bounds at this time include why certain actions were taken, how stakeholders reacted, why adjustments were made (or not), what assumptions developed, and other questions that need to be managed later.

 

• Goals and Considerations

Compare the project results to the fuzzy goals and other considerations. Be cautious to avoid scope creep. Manage other questions later such as why certain actions were taken, how stakeholders reacted, why adjustments occurred (or not), and what assumptions developed.

 

• What Worked & Hampered

Results-focused discussion (or lack thereof) stimulates talk about options and conditions to leverage in future projects.

• • • • How stakeholders reacted
      • What assumptions developed
      • What worked and hampered
      • Why certain actions took priority
      • What adjustments worked (or not)
      • Other questions as appropriate.

• Issues and Risks

Assess or build a risk management plan and other next steps or actions (e.g., Guardian of Change) based on actual results.

 

• Wrap-up

Use the four activities in the MGRUSH review and wrap-up

 

Special Ground Rules for an After-Action Review Event, Meeting, or Workshop

An AAR workshop can handle more than twenty people, with frequent use of break-out groups. Do not hesitate to partition the workshop so that participants may come and go as required. You may need to loop back, cover material built earlier, and clarify or add to it. Above all, the approach shifts the culture from one where blame is ascribed to one where learning is prized, yet team members willingly remain accountable.

Conduct After-Action Reviews consistently after all significant projects, programs, and initiatives. Therefore, do NOT isolate “failed” or “stressed” projects only. Additionally, ground rules and guidelines that have proven successful in the past include:

• Do NOT judge the success or failure of individuals (i.e.; judge performance, not the person)
• Encourage participants to raise any potentially important issues and lessons
• Focus on the objectives first

 

For learning organizations

For learning organizations, the following also supports cultural growth:

• Some of the most valuable learning derives from the most stressful situations
• Transform subjective comments and observations into objective learning by converting adjectives such as “quick” into SMART criteria (i.e., Specific, Measurable, Adjustable, Relevant, and Time-Based) such as “less than 30 seconds.”
• Use facilitators who understand the importance of neutrality and do not lecture or preach
• Teach the team to teach itself

Therefore, effective use of After-Action Reviews supports a mindset in organizations that are never satisfied with the status quo—where candid, honest, and open discussion evidences learning as part of the organizational culture. In conclusion, learning is everyone’s responsibility and it begins with hard data used to analyze actual results.

______

Don’t ruin your career by hosting bad meetings. Sign up for a workshop or send this to someone who should. MGRUSH workshops focus on meeting design and practice. Each person practices tools, methods, and activities daily during the week. Therefore, while some call this immersion, we call it the road to building high-value facilitation skills.

Our workshops also provide a superb way to earn up to 40 SEUs from the Scrum Alliance, 40 CDUs from IIBA, 40 Continuous Learning Points (CLPs) based on Federal Acquisition Certification Continuous Professional Learning Requirements using Training and Education activities, 40 Professional Development Units (PDUs) from SAVE International, as well as 4.0 CEUs for other professions. (See workshop and Reference Manual descriptions for details.)

Want a free 10-minute break timer? Sign up for our once-monthly newsletter HERE and receive a free timer along with four other of our favorite facilitation tools.