Managing
A debrief is where an activity turns into learning, and it has a shape: describe what happened, work out what it meant, decide what changes. Your job is to ask, wait and connect, not to announce the lesson. Here is the sequence, the questions in the order they work, and the actual sentences to say when the room stalls.
Most activities teach nothing on their own. A team builds the tower, plays the simulation, survives the crisis exercise, everyone claps and goes to lunch. The learning lives in the twenty minutes afterwards, and that conversation is a skill in its own right. Run it well and people leave with something they will do differently on Monday. Run it badly and you have hosted a nice game.
This is the structure I use, the questions in the order they work, and the wording to steal. Nobody has ever complained that a facilitator was too clear.
The group does the thinking. You ask, you wait, you connect what people say to each other, and you keep your own conclusions in your pocket. The moment you announce the lesson, you have taken it off them. They will nod, write it down, and forget it by Thursday, because it was your insight and not theirs. That handover of the thinking is the whole point of experiential learning, and the debrief is where it either happens or doesn't.
If you finish a debrief hoarse, you ran it wrong. The people who did the activity should do most of the talking.
Nearly every workable debrief structure is a version of the same three moves. The best-known phrasing is "What? So what? Now what?", which comes from Terry Borton's writing in 1970 and has been adapted many times since, notably for reflective practice in nursing and education.
A rough split: after a sixty-minute activity, run twenty-five to thirty minutes of debrief, giving five minutes to the first move, fifteen to the second and the rest to the third. If you are short on time, cut the first move, never the third.
The opening decides whether you get real answers or polite ones. Do four things, in this order.
Most bad debriefs are not caused by bad intentions. They are caused by four or five habitual questions that quietly close the room.
| Instead of | Say | What changes |
|---|---|---|
| "So, what did we learn?" | "Walk me through the last ten minutes. Just the sequence." | Opens on facts anyone can supply rather than on a graded answer |
| "Did everyone feel included?" | "Who spoke least in that round, and what would have made it easier to speak?" | A yes/no question becomes a specific, answerable one |
| "What I noticed was that you all ignored Sam's idea." | "Sam suggested something around minute four. What happened to it?" | You describe the observable event and hand the interpretation back |
| "Great job, team." | "That worked. What made it work, exactly, and could you do it again on purpose?" | Turns praise into a mechanism the team can repeat |
| "Any final thoughts?" | "One sentence each: what will you do differently in your next team meeting?" | Closes with a commitment instead of a shuffle towards the door |
Keep these on a card. Never work through them like a checklist, but having a dozen good questions in your pocket is what lets you stop improvising and start listening.
That fourth question is the hinge of the whole debrief. Everything before it is about a game. Everything after it is about the team. Ask it plainly, then wait, because the first honest answer usually arrives after an uncomfortable pause.
New facilitators fill silence in about two seconds, usually by answering their own question. Count to ten instead. If it still hangs there, name it rather than rescuing it: "I'm going to leave that in the room for a moment." Then look at the floor, not at anyone's face. Staring at people makes silence a standoff; looking away makes it a thinking pause. Most of the work of a debrief is active listening with your mouth shut.
Four failure modes cover most of what goes sideways. Each has a recovery move that you can run without breaking the mood.
One more: occasionally somebody is genuinely upset, because the activity touched something real. Do not push, and do not perform concern in front of everyone. "That's fair. Do you want to say more now, or catch me afterwards?" gives them a dignified exit either way.
Endings drift unless you run them. Two minutes before the finish, say so: "Two minutes left, so let's land it." Then take one commitment per person, out loud, one sentence each. Spoken commitments outlast anything written on a flipchart nobody photographs.
And resist the summary speech. If you have run the three moves properly, the group has already said everything you were planning to say, better than you would have said it, and in their own words. A thank you and a clear stop is enough.
Debriefing is a performance skill, not a knowledge one. You can know every question on this page and still freeze the first time fourteen people look at you and say nothing at all, or fold the moment someone senior gets defensive. The questions are the easy part. The waiting, the redirecting, the refusal to explain the lesson yourself: those only change through repetition, with somebody watching you and telling you honestly what you did. That is the argument for facilitation practice generally, and for putting teams through real activities rather than slides. Behaviour moves through rehearsal and feedback. It has never moved much through reading.
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.
Questions
A debrief is the structured conversation after an activity, exercise or incident where the group works out what happened, what it meant and what should change. It is not a summary delivered by the facilitator. The value comes from the participants doing the analysis themselves, out loud, while the experience is still fresh.
Start factual: "Walk me through what happened, in order." Move to meaning: "What did that cost us?" and "Is that how it goes at work too, or was that just the exercise?" Finish with transfer: "What is one thing we do differently in the next fortnight, and who owns it?" Open questions only, and one at a time.
Roughly a third to a half of the activity itself. A twenty-minute exercise deserves ten minutes; an hour-long simulation deserves twenty-five to thirty. If you are squeezed, cut the descriptive opening rather than the closing commitments, because a debrief without a "now what" rarely changes anything on Monday.
A three-stage reflective sequence: describe what happened, interpret what it means, then decide what to do next. The phrasing traces back to Terry Borton's work in 1970 and has been widely adapted since, including by Rolfe and colleagues for reflective practice. Most debriefing structures are variations on the same three moves.
Shrink the audience before you shrink the question. Send people into pairs for thirty seconds each, then take answers from pairs rather than individuals. Also check your own habits: count to ten before filling a silence, ask one question rather than three stacked together, and start with something factual that anyone in the room can answer.
Largely context. A retrospective is a recurring team review of a work period, usually a sprint. A debrief follows a single specific event: an exercise, a launch, an incident, a training activity. The mechanics overlap almost entirely, and a good retrospective is essentially a debrief run on real work instead of a designed experience.
Keep reading
The wider skill set the debrief sits inside, defined without the jargon.
GuideWhy the activity is only half of it, and the debrief is the other half.
GuideActivities worth debriefing, with the point of each one spelled out.
Get in touch
Book a 30-minute discovery call and we'll shape an experiential programme around your goals.
Book a discovery call →