The purpose of an After-Action Review (AAR) is to determine what worked and what didn’t for a specific action, event, or project and to extract lessons that can be applied to others.
These lessons are then documented in Lessons Learned (LL) and shared across an organization.
AARs are typically conducted immediately after an event or project to capture information while it is still fresh, while LLs are usually compiled at the end of a project or phase and may include information contained from multiple AARs.
The AAR should seek to answer six key questions:
- What was supposed to happen?
- What really happened?
- What went well?
- What did not go well?
- Why did it go wrong?
- What should be changed for next time?
After-Action Reviews can be either informal or formal, with the main difference between them is the time and resources needed to conduct the review.
Informal After-Action Reviews
- Conducted by internal or project staff
- Take less time
- Scheduled when needed
- Usually conducted at the event, project site, or project office
Formal After-Action Reviews
- Conducted by a leader or facilitator
- May include external observers
- Take more time
- Scheduled with adequate notice to participants
- Conducted where best supported
Project managers should plan for these meetings like you would for any other meeting.
Here are a few additional thoughts:
- Send meeting invitations to participants with adequate notice
- Create an agenda with a list of topics that will be discussed
- Prepare the meeting room with white boards or flip charts
- Designate a note taker and timekeeper
- Encourage participants to contribute to the discussion