An after-action review is a short, structured team discussion of work that has just ended. In a survey run by Ernst & Young in October 2006, reported by the Project Management Institute, 91 percent of people said lessons learned reviews were helpful. Only 13 percent held them. That gap, between what teams believe and what they actually do, is the subject of this piece.
What is an after-action review?
An after-action review is a short, structured team discussion about a workflow that just ended. It asks four things. What did we plan? What did we get? Why? What will we change? The US Army built it, and teams can use it after any mission.
The name sounds heavier than it really is, which is one reason teams tend to over-do it. An after-action review is supposed to be a short, structured team discussion that turns finished work into a lesson the team can act on. It needs no software, no outside facilitator, and no budget line. Done well it takes less time than the status meetings most teams are already running.
The US Army developed the methodology in the 1970s, as Wharton executive education notes, and it spread from there into fire crews, emergency medicine, aid work and then into business. The National Wildfire Coordinating Group still frames the aim in close to the original words: the point is to enable a team to "discover for themselves what happened, why it happened." That phrase carries the whole design, because it's not a briefing handed down by whoever happened to be in charge, and it's not a report written for a file that nobody ever opens. It's a group working out its own lessons, together, out loud, and while the details are still fresh.
You'll see the same practice under other labels, including the debrief which is, actually, more structured; as well as a hot wash, a post-project review and possibly a lessons learned event. The label matters far less than the habit, and teams that argue about which title to use are often dodging the harder question of whether or not they'll actually do it.
We teach our proprietary version, the F-4 Debrief, as the closing step in the team lifecycle of plan, brief, execute and debrief. It's enabled by planning correctly by way of the E.A.G.L.E. Planning methodology. It's supported by a V.I.P.E.R. Pre-Mission Brief prior to execution. The order here matters, because if the team hasn't planned correctly, it does not have the right to practice accountability. A Debrief is only as good as the plan it is measured against, and a team that never planned has no standard against which to assess.
What are the four after-action review questions?
The four after-action review questions are simple: What did we set out to do? What actually happened? Why did it turn out that way? What will we do next time? Ask them in that order. Skipping the first one wrecks the rest.
The four questions have held their shape for fifty years, which is rare for any management idea, and it tells you something about how sound the design actually is. The National Wildfire Coordinating Group frames the same sequence around standards, so that a team builds on what it does well rather than just listing errors.
Variants exist, and most of them are sensible: Asana wraps the questions in four phases of design, prepare, implement and share. Other published models have evolved to five steps by splitting up the write-up from the talk. The National Police Institute, working with the US Department of Justice, lays out eight steps for major incidents. This makes sense given a context where their findings may be made public.
The variation matters far less than the order. The first question, what did we set out to do, is the one teams skip, because everyone assumes the answer is obvious and shared. Often, it is neither. When five people in a room give four different versions of what the goal was, we start to see where things began to fall apart.
Some versions split the last question in two, asking what to keep and what to change. That small choice shifts the tone of the whole meeting, because it forces the group to account for what worked instead of building a list of only faults. For a walkthrough of the debrief methodology, and the ground rules that keep it useful, see our separate article about the “no-blame debrief.”
Do after-action reviews actually work?
Yes. After-action reviews work when they're run with structure. A meta-analysis of 46 samples covering 2,136 people, conducted by Tannenbaum & Cerasoli and published in Human Factors, found a clear gain. Teams that ran them outperformed teams that didn't. The benefit was consistently measured at 20 to 25 percent, and it held for teams and individuals alike.
The newest hard evidence comes from the critical care field. A 12-month study in the American Journal of Critical Care tracked 653 shift teams at a teaching hospital as they embraced a standardized debrief format. At the start, 45.4 percent of teams said they had thought about holding a debrief; after the change to the standardized format, that number jumped to a range of 65.4 percent to 95.0 percent. Use of the standardized format rose from 0 percent to 100 percent, reported barriers fell from 25 percent to 0 percent, and teams held a mean of 7.2 debriefings a week.
The core evidence for why this study was so successful traces back to the original Tannenbaum & Cerasoli report from 2013. In their meta-analysis, published in Human Factors, they drew on 46 samples covering 2,136 people, and concluded that organizations can lift both team and individual performance by 20 to 25 percent through properly conducted debriefs. For a change that costs nothing but time, that's an incredibly compelling bottom line.
That word 'properly' stands out, and the study is clear as to why this matters. Two things bolstered the effectiveness of debriefs: how closely the debrief matched the work under review, and the presence of structure and skilled facilitation. This is also the part most teams miss. A loose chat about how everyone felt the project went isn't a weaker form of the same thing. It's a different thing altogether with a much different, and "smaller" effect. Treating the two as the same is how a firm ends up deciding that debriefs simply don't work here.
How many teams actually run after-action reviews?
Far fewer teams run these reviews than say they value them. In one survey, most people called such reviews helpful. However, only a small share said their own team held them. Hospital data identified the same gap. Good intentions abound; actual practice is the part that's largely missing.
The Ernst & Young numbers reflect the same reality: 91 percent of people rated lessons learned reviews as helpful, and yet only 13 percent actually did them. That survey ran in October 2006, and is a bit dated; one might expect two decades of lived experience to have closed the gap. The evidence says this hasn't happened.
Separate PMI research asked what stopped people from putting more effort into capturing lessons. A lack of time was the primary culprit at 67 percent, accompanied by a lack of support from management at 62.5 percent. A lack of reward, resources, and clear guidance were each named by more than 50 percent, while only 8.4 percent agreed their own firm already put in enough effort. This is the brutal reality as reported by the people actually doing the work.
Clinical settings show the same results. A single-site study in the British Journal of Anaesthesia followed 460 surgical lists and found that debriefing was completed on 23.3 percent of them at the start. This number rose to 39.0 percent at six months after a deliberate push. This is a real gain, achieved in a setting with a strong safety culture and an existing checklist habit. And yet, it still highlighted that the majority of events went without debriefs.
The pattern across all three sources is consistent and, frankly, a little unsettling, given that everyone seems to agree that the practice is a net positive, one that yields real results. Teams simply don't do it, and the reasons they give are less telling than the ones they leave out.
Why do most after-action reviews fail?
Most after-action reviews fail for two reasons. First off, teams simply don't hold them. And the reason why they don't is time. They say there's not enough of it. In the British Journal of Anaesthesia study, barriers were reported on 17.6 percent of opportunities, and time constraints made up 70 percent of these missed opportunities to debrief.
The second failure flies a bit more under the radar yet yields a more devastating result, because it highlights that the truth is often absent from these sessions. Mental Health First Aid England, polling 2,000 UK workers between December 2025 and January 2026, found that 45 percent of people surveyed don't feel safe raising a mistake or highlighting a risk at work. Tied to this, Gallup's 2025 research found just 3 in 10 employees strongly agree their opinions count.
Put those two findings together, and you get the after-action review most managers have sat through without perhaps knowing or labeling it. The room is full, the conversation is polite, a few real but minor points get written down. And yet, the one thing that drove the outcome is never said aloud. The meeting itself isn't broken, per se. One could argue that the system is working, reporting back the exact level of candor the organization has earned.
Why do after-action reviews fade away after a few months?
After-action reviews fade from the forefront because nobody keeps them alive. One study saw use of AARs climb for a bit, and then slip back after six months.
Adoption happens because it's mandated by leadership. Left to our own devices we'll skip the thing we know works, because it's just easier to not do the work. The British Journal of Anaesthesia data offers us a bit of this insight. Debriefing rose from 23.3 percent of surgical lists at the start of the study to 39.0 percent adoption at six months. Then it dropped off, though adoption rates stayed above the start point through 18 months. The study is clear that holding the gain took steady support, training, and pressure. Without all of this, the new habit, the one that's a shift from the everyday norm, decays rapidly.
The critical care study shows a subtler version of the same problem. As teams thought about debriefing more often, the gap between wanting to hold one and holding one grew wider, and the main reason given was a sense that there were no issues to discuss. This would be a stunning conclusion in any field, as there's always something to learn...but critical care?
And this belief is for sure a trap, one worth naming, because it sounds on the surface like good news. A week with no incidents feels like a victorious week worth celebrating, when in fact it's the week with some of the richest material a team has to learn from. This is because figuring out why a mission went well is the only way to win on purpose the next time out. Teams that only debrief their losses build a fine catalog of what to avoid but very little understanding of what to repeat.
This leads to a secondary challenge: every skipped after-action review makes the next one a little easier to skip. Suddenly, the small deviation becomes the old norm again, and within a quarter or two the AAR has quietly slipped back to being that dreaded thing that only happens after a disaster. Arresting this drift is really a matter of making the AAR THE priority. Not a, but THE priority. The thing that happens after every mission, period.
How is an after-action review different from a retrospective?
An after-action review and a postmortem share commonalities: Look at the system. Measure execution of the system and look for gaps. The difference is all about when the two processes are run, and how.
The after-action review was created by the US Army in the 1970s. The core question: what was meant to happen versus what did? Best fit: military, specifically the US Army, because it's what they use after their missions.
A no-blame debrief and a postmortem also share these commonalities. But a debrief takes place regardless of whether the team wins or loses. The postmortem only takes place after a crash. The debrief is about building capability in a positive, forward-focused manner. The postmortem harnesses fear of a repeat failure to drive behavior change. The following list shines additional light into how the different accountability mechanisms work:
NO-BLAME DEBRIEF (VMax Group's F-4 Debrief): Used by high-performance military teams like US Air Force Fighter Squadrons, and taught by VMax Group. The core questions: Why did we, or didn't we achieve what we set out, and what can we learn from this to make the next iteration even better? Best fit: any team, after any mission.
POSTMORTEM: Site reliability engineering. Core question: how did the system allow this? Best fit: perhaps software incidents and outages? We would recommend transitioning to a true Debrief.
RETROSPECTIVE: Agile space. Core questions: What went well, what didn't, and how can we improve. Best fit: allegedly in software engineering. However, we believe it should be replaced with a true Debrief.
LESSONS LEARNED: Project management practice. Core question: what should the next project know? Best fit: we truly believe it should be replaced by a true Debrief.
The vocabulary blurs quite a bit in daily use, and often these terms are considered relatively synonymous. Asana, Atlassian and the Project Management Institute all use these terms in slightly different senses, and the postmortem in particular was shaped by software incident response rather than general management. Atlassian's guidance assumes everyone involved acted with the best intentions available to them at the time, and that assumption is the shared root of every format in the list.
A few things set the no-blame debrief apart, making it useful for every single business team out there. The first is that it is designed for ordinary work as opposed to only a crisis, which means it can be used constantly and, because of the frequency, very efficiently. The second is that it is short and repeatable by design, so that it organically becomes part of how the team operates rather than a special event that gets convened when something has gone badly wrong. Tied to this, and most importantly, it leads to the development of a culture of accountability made possible with high psychological safety...and it perpetuates that safety. This is in contrast to those systems that only follow fault or failure.
Frequent debriefs lead to more positives than might initially be obvious. The Human Factors meta-analysis found that both structure and skilled facilitation increased the size of the effect, meaning that the difference between a wandering conversation and a tightly run debrief isn't cosmetic, but rather substantive. And this combination of structure and frequency yields the true value. The other systems are much more fuzzy, happen much less frequently, and therefore, aren't as useful.
In summary
- Most say after-action reviews help. But few teams actually run them.
- Time is the primary excuse. But a lack of trust is the cause.
- Structure enables success. A general chat is a waste of time.
- After-action reviews tend to drop off at six months. One must work to keep them alive.
- A quiet week holds lessons to be learned from. Learn from these.
- Book the after-action review before the work starts.
The evidence here is stunningly clear: after-action reviews deliver results. The obstacle to overcome isn't a lack of knowledge. Teams know these reviews work yet still don't hold them, and when they do hold one, the truth often remains unspoken. Both of those are things a leader can change, and neither costs anything but attention and a willingness to go first.
Here's the bottom line: if your team knows it should be doing AARs, but somehow they never do, we can help. We know how to help them bridge this gap and implement the new habit. Just book a call. We'll examine how your team learns today and help equip you with a better way, all in very short order.
