DEBRIEF
How to run a debrief
A debrief is a deliberate stop to walk through something that just happened and pull the lessons out of it. It's the less formal side of the after-action review — and the two terms often get used interchangeably.
You run it with five questions, in order:
- 1. What was the plan?
- 2. What actually happened?
- 3. What worked?
- 4. What needs to change?
- 5. What's the specific action coming out of this?
The first two set the picture. The middle two pull lessons out of it. The last one turns the lessons into something you'll actually do. It works the same whether you're alone after a meeting, with a team after a hard week, or looking back on a whole role.
Why it matters
You just finished something — a meeting, a week, a project, a role. The lessons are sitting right there in what happened. Most of them disappear if you don't stop and pull them out.
That's the difference a debrief makes. Without it, you start every new situation from zero. With it, each pass makes the next one better. It's how people who step into hard roles get faster at it every time.
Honesty is the whole thing
A debrief without honesty is worse than no debrief. It creates the look of growth without the substance — and it tells everyone in the room that this is what passes for improvement here.
The hard part is ego. Getting called out in front of a group for a mistake is uncomfortable, and people protect their reputation instead of learning. The shift is simple to say and hard to do: improvement has to matter more than how you look.
The fastest way to set the tone: name your own miss first. Your bad call, your slow reaction, the thing you didn't see. The room reads that signal. It tells everyone honesty is what this runs on — and no one is exempt, including the person running it.
The five questions, step by step
1. What was the plan?
How you expected it to go. Sometimes that's a written plan. Sometimes it's just the picture you had in your head walking in. Either counts. Say it quickly, start to finish, so everyone — including you — is working from the same baseline.
No picture going in? That's fine. Move on. More debriefs will teach you the value of having one.
2. What actually happened?
This is where most of the work gets done. Walk through it in order — phase by phase, day by day, whatever fits. As you go, name two things in the moment:
- Sustains — what worked and should keep happening.
- Improves — what didn't work and should change.
Don't list everything. Name the sustains that were new, special, or had outsized impact, and the improves that will actually move performance next time.
In a team, this step does a second job: most people only saw their slice. The debrief is where everyone gets the whole picture.
Capture as you go. Get someone writing, or take your own notes. Sustains and improves disappear fast.
3. What worked?
Read the sustains back. Tighten them. Keep the ones you can repeat on purpose — if you couldn't reproduce it, it's not usable yet. In a team, call people out by name for what they did well. It reinforces the behavior and shows everyone what right looks like.
4. What needs to change?
Read the improves back. Some are simple: we won't do that again. Others are worth a minute on why it didn't work — the why is what makes your next decision better.
5. What's the specific action?
Picking an action is easy. Following through is the hard part.
- Solo: leave with one or two things to work on, written somewhere you'll actually see again.
- Team: name the action, assign one owner, set a report-back date. Without all three, actions evaporate.
Got more actions than bandwidth? Prioritize the highest-payoff ones you can actually do. Park the rest for the next debrief.
And if life gets in the way and you don't get to an action, don't stop debriefing. Just knowing something needs to improve moves the needle the next time you face it.
Debrief template
Copy this and use it today.
DEBRIEF Event: ______________________ Date: ________ 1. WHAT WAS THE PLAN? How did I/we expect this to go? 2. WHAT ACTUALLY HAPPENED? Walk it through in order. Mark as you go: + Sustain (worked — keep doing it) – Improve (didn't work — change it) 3. WHAT WORKED? (sustains to repeat on purpose) • • 4. WHAT NEEDS TO CHANGE? (improves — and why) • • 5. SPECIFIC ACTION Action: ______________________ Owner: _______________________ Report back by: ______________
The book walks through two full debriefs — a ten-minute one after a job interview, and a new team lead running one after their team missed the week's goal.
How often to debrief
- Solo: daily is a strong default. Ten minutes at the end of the workday. Tie it to something you already do — the drive home, closing your laptop. The bar is low. The compounding is high.
- Team: after important events and pushes, or at the end of the week. The closer to the event, the better the recall.
- A whole role: the same five questions, over months instead of hours. Write things down early — you'll forget the original plan. It's harder to be honest about months than about yesterday, and it's where careers actually shift.
Debriefing every small thing is overhead. Debriefing nothing is malpractice. The right cadence gives you more signal than it costs in time.
Common questions
What's the difference between a debrief and an after-action review?
They're close. A debrief is the less formal version — quick, often right after the event. An after-action review is the formal process of reviewing, and debriefs feed into it. People mix the two up, and that's fine: both are a structured look back so the next time goes better.
How long should a debrief take?
As long as it's useful. A solo debrief can take five to ten minutes. A team debrief after a hard week might take thirty. Spend the time it earns and no more.
What if my team won't admit mistakes?
Go first. Name your own miss out loud, ask for help in front of others, and make it visible that honesty is safe. People don't want to be the one who stands out — showing them the new normal gives them cover to follow.
Running reviews across an organization
One debrief improves one team. Across an organization, it's a different job. Event debriefs roll up into organization-level reviews and one consolidated after-action review, and every recommendation gets tracked until it's closed. Without that, the system depends on whoever still remembers.
The Multi-Level After Action Review System →
Where this comes from
The debrief is one of five parts of The Operator's Method — the part that makes everything else compound. The method comes from 20 years as an Air Force Special Tactics Combat Controller.
The first time you walk into something hard, the question is am I an imposter? After enough debriefs, it becomes: I know where the gaps are. I have a plan.