Debriefing

Most definitions stop at "a review held after an event". Accurate, and it hides the part that matters. A debrief is not a summary of what happened. It is the work of turning what happened into something usable. Two teams can run the same exercise, or survive the same failed launch, and only one of them will be better next time. The difference is almost always the quality of the conversation afterwards.

Why the simple definition misleads

Calling it a review makes it sound like reporting, so people report. Someone recounts the sequence of events, the facilitator adds a few observations, everyone agrees it was interesting, and the session finishes on time. Nothing in that changes how anyone behaves on Tuesday.

A debrief is a reasoning exercise, not a recounting exercise. The useful question is rarely "what happened" on its own. It is "what were you thinking when you did that". People make decisions that are sensible given what they believed at the moment they made them. If you only surface the action, you fix nothing, because the belief that produced it is still sitting there intact. Surface the belief and the correction holds.

The exercise is not the training. The exercise is the raw material. The debrief is the training.

This is the mechanism underneath experiential learning. David Kolb described learning as a cycle: a concrete experience, reflection on it, a principle drawn from that, then a test of the principle in the next attempt. The debrief is where the middle two steps live, and they are the two that get cut when the day runs late. Without them you have run an activity, not a learning process, which is why so much outbound training produces a good day out and nothing measurable. The full cycle is worth understanding before you design anything.

The word also gets confused with its neighbours. Feedback is one person telling another how their behaviour landed, and doing that well is a separate skill; a good debrief contains surprisingly little facilitator feedback. A post-mortem is a debrief narrowed to a failure. A retrospective debriefs a period of work rather than a single event. And psychological debriefing after a traumatic incident is a different practice with different evidence, covered further down.

What a real debrief looks like

You can hear the difference from the back of the room. Participants talk far more than the facilitator. People describe their own reasoning unprompted, including the parts that turned out to be wrong. Disagreements about what happened get settled by evidence rather than by rank. Someone says "I assumed the client had approved it" and someone else says "I assumed the opposite", and the room goes quiet, because that gap is the actual finding.

A worked example. A team runs a timed build task and misses the deadline by four minutes. The weak debrief: the facilitator says communication broke down, everyone nods, the flipchart says communicate better. The real one: you ask when each person first knew the plan would not fit the time. Three of them say minute six, and none of them said so out loud. You ask what stopped them and get three different answers, one of which is that the person leading had already committed to the plan in front of everyone. Now you are debriefing something worth the hour, and it has stopped being about the exercise.

Debriefing vs a recap

Read the right-hand column as a checklist. Almost every team believes it debriefs. Considerably fewer pass that list.

How to run one properly

• Frame it in one sentence before you start. Say what the debrief is for, how long it will take, and that it is not an assessment. Skip that and people spend the first ten minutes working out whether they are being judged.
• Fix the facts before you touch the meaning. Rebuild the timeline briefly first. Debriefs collapse when two people argue about interpretation while holding different accounts of what occurred.
• Ask about decisions, not outcomes. "Why did that go wrong" invites defence. "What were you seeing at the point you split the group" invites information, and gets you the answer to the first question anyway.
• Pair an observation with a genuine question. State what you saw and the effect it had, then ask what led to it, and mean the question. This pairing of advocacy and inquiry is standard practice in medical simulation, and it is the line between a debrief and a telling-off.
• Borrow the After Action Review when you need a structure. What did we expect to happen, what actually happened, what caused the difference, what will we do differently. Developed for military use and short enough to run standing up.
• Or use what, so what, now what. Facts, then meaning, then action, in that order. The three-question form is usually traced to Terry Borton's work in the 1970s.
• Ask, then wait. Most facilitators break a silence within about four seconds. The answers worth having often arrive later than that. Least sophisticated technique in the trade, and the one that changes the most.
• Debrief the wins too. A team that only debriefs failure learns to hide failure, and never finds out why the good days were good, so it cannot repeat them on purpose.
• Finish with less than you want. Three specific changes with owners beat fifteen insights on a flipchart. A debrief that produces no decision was a discussion.

None of this survives a room where honesty is expensive. If admitting you were lost at minute six carries a career cost, nobody admits it, and the session becomes a performance of learning. Psychological safety, the condition Amy Edmondson has spent her career researching, is the input here, not the bonus. The other prerequisite is plain active listening: most poor debriefs are poor because the facilitator was waiting to make a point rather than listening for the one on offer. If you run these regularly, learn the wider craft of facilitation properly.

How to tell whether yours are working

1. Does anyone volunteer their own mistake before someone else names it? That single behaviour tells you more about the health of your debriefs than any survey will.
2. What is the talk ratio? Have a colleague tally it. If the facilitator holds more than a third of the airtime, it was a lecture with pauses in it.
3. Do the agreed changes appear? Take the actions from your last three debriefs and check what actually happened next. This is the only hard test, and most organisations never run it.
4. Do people bring their own material? When participants start asking to debrief incidents you did not schedule, the practice has taken hold.

Be honest about the limits of measurement. End-of-session ratings capture how the session felt, which is what Donald Kirkpatrick called the reaction level, the shallowest of his four, and a weak predictor of behaviour change. A debrief that felt uncomfortable and shifted one habit is worth more than one everybody enjoyed. The only credible evidence is behavioural, takes weeks to observe, and cannot be collected in the room, which is precisely why so few organisations look for it.

Myths and common mistakes

• "The debrief is the wrap-up." It is the main event. When time runs short, cut the activity, not the conversation about it.
• "A debrief means telling people what they did wrong." If the facilitator supplies the insight, the facilitator owns it. Insight people reach themselves is the kind that survives the car park.
• "Longer is better." Twenty focused minutes on one real moment beats ninety minutes of general reflection. Attention is a resource and it decays.
• "Debrief everything." Scale the debrief to the event. Two minutes after a routine task is proportionate. A full session after everything teaches people to switch off in advance.
• "Debriefing helps after a traumatic incident." Different practice, different evidence. Reviews of single-session psychological debriefing after trauma have not supported it, and several clinical guidelines advise against routine use. Do not blur it with a learning debrief, and do not run trauma support you are not qualified to run.
• "Everyone must share." A forced round of contributions produces polite noise. Ask sharper questions instead, and go to the quiet people with something specific you watched them do.
• "We debriefed it, so it is closed." A debrief with no owner and no review date is a conversation you will be having again in six weeks.

The through-line is simple enough. A debrief is not a summary of what happened. It is the deliberate act of finding out what people were thinking when it happened, and agreeing what to think next time. Get that right and almost any experience becomes training. Get it wrong and even good training stays an anecdote.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.