The Meeting That Sounds Useful and Rarely Is
Your team just finished a high-stakes project. A product launch. A merger integration. A crisis response. Someone says, "We should do an after action review."
Everyone agrees. The meeting gets scheduled. Someone creates a slide deck with the four standard questions. What went well? What did not? What should we do differently? What did we learn?
The team gathers. People say safe things. A few brave souls name real problems. Someone captures the notes. The document goes into a shared drive.
Six months later, the same team makes the same mistakes on the next high-stakes project.
The after action review happened. Nothing changed.
Why Most AARs Fail
The failure is not in the format. It is in the conditions.
AARs conducted after the fact lack urgency. When the project is over, the emotional stakes are gone. People are relieved it is over. The instinct to understand what happened is weaker than the instinct to move on. The retrospective discussion is intellectual, not visceral.
AARs in hierarchical environments produce safe answers. When a VP is in the room, people do not say what they actually think. They say what sounds constructive. "Communication could have been better" is code for "leadership changed direction three times and never told us." The AAR captures the polished version, not the real one.
AARs rarely assign behavioral accountability. Lessons learned documents describe what the team should do differently. They rarely name who specifically will do it differently, when, and what changes in behavior. Without behavioral specificity, the lesson is just an observation.
AARs treat every project as unique. When teams believe their situation was unusual — "this project was especially complex" — they discount the lessons as not applicable to future work. The AAR becomes a historical document rather than a behavioral guide.
What a Good AAR Actually Does
A well-facilitated after action review does three things that a bad one does not.
It surfaces what people actually thought, not what they are willing to say in public. This requires a skilled facilitator, a structured format that makes truth-telling safe, and often some distance from the people most implicated by the honest answer.
It connects observation to behavior. The shift from "communication broke down" to "here is specifically what each team lead will do differently in the next project kickoff" is the shift from documentation to development.
It creates shared accountability. When the whole team hears the honest analysis together and commits publicly to specific behavioral changes, the chances of those changes actually happening increase significantly. The public commitment is what makes lessons stick.
The After Action Review Template
Use this structure. It runs in 60-90 minutes with a skilled facilitator.
---
SECTION 1: What Was the Intent? (10 minutes)
Before reviewing what happened, align on what was supposed to happen. This is more important than it sounds. Teams frequently discover in this section that they had different understanding of the goal — and that misalignment explains half of what went wrong.
Questions: - What were we trying to achieve? - What did we each understand the goal to be at the start? - Where did those understandings differ?
---
SECTION 2: What Actually Happened? (20 minutes)
Reconstruct the sequence of events factually. Not why things happened — just what happened and when. This creates a shared timeline that often surfaces facts people on the same team did not know about each other.
Questions: - Walk through the key moments in chronological order. - Where did the plan and reality first diverge? - What decisions were made, by whom, and with what information?
Do not allow opinions in this section. Only facts and sequences.
---
SECTION 3: Why Did It Happen? (20 minutes)
This is where most AARs go wrong. Teams jump to solutions before they understand causes. Causes are often systemic, not individual. They involve structure, incentives, information flow, and decision authority — not just individual performance.
Questions: - What caused the gaps between intent and outcome? - What structural or process factors contributed? - What information was missing, delayed, or misinterpreted? - Where did communication break down — and why?
Separate systemic causes from individual performance. Both matter. They require different responses.
---
SECTION 4: What Should We Sustain? (10 minutes)
Most AARs focus on failure. The best ones also analyze success. If the team navigated a crisis well, understanding why is as valuable as understanding why something failed.
Questions: - What specifically worked well? - What behaviors or processes produced that outcome? - How do we protect and repeat what worked?
---
SECTION 5: What Specifically Changes? (20 minutes)
This is the section most AARs skip or do too quickly. The output of this section is not a list of lessons learned. It is a list of behavioral commitments with owners and timelines.
Format:
| What changes | Who owns it | What behavior specifically | By when | |-------------|------------|---------------------------|---------| | 1. | | | | | 2. | | | | | 3. | | | |
The commitment must be behavioral and specific. "Improve communication" is not a commitment. "Before each milestone, the project lead sends a written summary of decisions made, changes from plan, and what each team needs to know next" is a commitment.
---
SECTION 6: Review at Next Project Start (5 minutes)
Schedule a 15-minute read-back of the AAR commitments at the kickoff of the next major project. This closes the loop. It signals that the review was real, not theatrical.
---
The Problem With Safe AARs
There is a particular failure mode that looks like a successful AAR. The team meets. People speak honestly — but only about topics that are safe. The real issues — the leader who made a decision that derailed everything, the political dynamic that prevented escalation, the process that everyone knew was broken but nobody would say — stay off the table.
This produces a lessons-learned document that is technically accurate and operationally useless.
Getting past the safe version requires two things: a facilitator who is not embedded in the team's hierarchy, and a format that normalizes truth-telling before the difficult topics arrive.
This is why the military's AAR process works better than most corporate versions. There is a structured norm that rank is irrelevant in an AAR. A lieutenant can challenge a colonel's decision. The format explicitly permits — and expects — disagreement with authority. That norm does not exist in most organizations.
The Simulation Approach: AAR in Real Time
There is a more powerful version of the after action review. It does not happen after the project. It happens *during* a high-stakes simulation where the team is under real pressure, making real decisions, and experiencing real consequences for their choices.
Save the Titanic is built on this principle. Teams run a 3.5-4 hour crisis simulation where they must save the Titanic from sinking. They make decisions under pressure. They fail in ways they did not anticipate. They discover exactly how they behave when the stakes are high and time is short.
The debrief that follows is the most powerful form of AAR a team can run. Why?
The emotional memory is fresh. The team just lived through it. The moments where communication broke down, where authority was misused, where a minority voice was ignored — everyone remembers exactly when it happened and how it felt. That specificity produces insight that a retrospective on a completed project rarely achieves.
The stakes were real within the simulation. Teams do not phone it in. They argue, they strategize, they override each other, they make bad calls under pressure. The behaviors they exhibit in the simulation are the behaviors they exhibit at work — stripped of the professional polish they normally maintain.
The consequences are visible. In the simulation, poor communication causes more damage. A missed signal means more passengers lost. The feedback loop is fast and unambiguous. In real projects, cause-and-effect are separated by weeks or months. In the simulation, they are separated by minutes.
Rank is genuinely irrelevant. When everyone is in a crisis together, the hierarchical protection that makes AARs safe and useless disappears. The data entry analyst and the VP are both accountable for the outcome. That equality of stake produces equality of honesty.
See what the simulation reveals that traditional assessments cannot and what the outcomes look like at 30 and 90 days after the experience.
Frequently Asked Questions About After Action Reviews
### How long should an AAR take?
For a standard project: 60-90 minutes. For a major initiative (multi-month, cross-functional, high-stakes): 2-3 hours. For a crisis or significant failure: half a day with a skilled external facilitator. The length should match the significance of what happened and the depth of behavioral change needed.
### Who should facilitate the AAR?
Not the project leader. Not anyone whose decisions are being reviewed. The facilitator needs enough distance to ask the uncomfortable question. An internal facilitator from another team works for routine reviews. An external facilitator is worth the investment for significant projects, failures, or teams with entrenched dynamics.
### How do you handle disagreement in an AAR?
Welcome it. Productive disagreement about what happened and why is how the team learns. The facilitator's job is to keep disagreement focused on events and behaviors — not on people's character or intentions. "What happened?" is productive. "Why did you decide that?" is productive. "That was a bad decision" is not productive.
### How do you make sure the commitments stick?
Two mechanisms. First, the read-back at the next project kickoff — 15 minutes, every team member reviews their specific commitment. Second, check in at 30 days: "Did the specific behavior change? What evidence do you have?" If the commitment is abstract, it will not survive 30 days. If it is specific and behavioral, with a named owner and a timeline, it has a chance.
### What if leadership is implicated in what went wrong?
This is the hardest case. The safest outcome for everyone in the room is to not name it. The most useful outcome requires naming it. An external facilitator, a structured format that normalizes challenge to authority, and leadership that has explicitly invited honest feedback before the session are all required. If those conditions are not present, the AAR will produce a partial truth.
Read more about how to build psychological safety so teams speak up for the conditions an AAR needs to work. See how to break analysis paralysis in one meeting for the decision speed problem AARs often reveal. And explore what team simulations reveal that traditional assessments cannot for why experiential feedback outperforms retrospective feedback.
The goal of an after action review is not to document what happened. It is to change what happens next. Save the Titanic is the team experience where the AAR happens in real time — while the stakes are still live, the emotions are still fresh, and the behavior change is still possible.
**See how teams use Save the Titanic for high-impact debrief →**
**View outcomes and results from leadership teams →**
**Book a 20-minute walkthrough to see the simulation and debrief process →**