Debriefs Boost Performance by 20–25% – the Meta-Analysis
What separates pilots, surgical teams, and elite athletes from most project organizations? Not that they make fewer mistakes – but that they systematically talk through what happened afterwards. The structured after-action conversation, often called a debrief, is as natural in those environments as the performance itself.
In 2013, researchers Scott Tannenbaum and Christopher Cerasoli published a meta-analysis – a study that statistically combines the results of many earlier studies – in the journal Human Factors. The question: do debriefs actually improve performance, for individuals and teams? The answer was unusually clear.
What does the research say?
Across the studies, Tannenbaum and Cerasoli found that structured debriefs improve performance by an average of around 20 to 25 percent. The effect held for both individuals and teams, and it appeared even though a debrief often takes only a short while. Few interventions in professional development deliver so much impact per minute invested.
So what counts as a debrief? Not a casual chat afterwards, but a deliberate, structured conversation about a just-completed performance: what was supposed to happen, what actually happened, why did it turn out that way, and what do we do differently next time? The researchers stressed that quality matters – debriefs work best when they focus on learning rather than blame, when participants actively reflect for themselves instead of just listening to a run-through, and when the conversation is about concrete events rather than general impressions.
The underlying mechanism is that experience by itself does not automatically become learning. It is the reflection afterwards that turns what happened into something you can use next time. Without a debrief, even experienced teams repeat the same mistakes – with one, every execution becomes a training opportunity. That explains why professions where mistakes cost lives, such as aviation and healthcare, have made the debrief mandatory rather than optional.
What does this mean for you as a project manager?
Don't wait until the end of the project to capture lessons. The classic "lessons learned" workshop after closure comes too late to help the project that's still running. Instead, build in short debriefs after key events: after the steering committee meeting, after the delivery, after the difficult client conversation. Ten minutes is often enough, and the benefit goes to the current project instead of being archived in a report nobody reads.
Keep the structure simple and stable: What was the intent? What happened? Why? What do we take with us? The same four questions every time make the conversation safe, predictable, and quick to run even under time pressure. And keep blame out of it – the moment a debrief turns into an interrogation, people stop telling you what actually happened.
Debrief yourself, too. After a conversation that didn't sit right: take three minutes and walk through the same questions in your notebook. It sounds trivial, but that very habit is what separates someone with ten years of experience from someone with one year of experience ten times over.
How to practice this
This study is why the debrief is the core of Project-simulator, not an appendix. After every practice conversation you get a structured review that quotes your own lines and connects them to what the research says works – so every simulation becomes a completed learning opportunity. Try it free for a week at project-simulator.com.
In Project-simulator you practice these conversations against an AI counterpart and get feedback grounded in research like this.
Try free for 7 days