Rupert Picardo · Facilitation · April 2026
Quick answer
The experiential learning debrief is the structured, facilitated conversation that follows a simulation, team challenge, or experiential exercise — in which participants examine what happened, why it happened, and what that tells them about how they work. It is not a feedback session. It is not a review. It is the process through which the experience becomes learning.
Without a debrief, participants have had an interesting activity. With one, they have had a development experience. The quality of the debrief determines, more than any other single factor, whether an experiential intervention produces lasting behaviour change. You can run the best simulation in the world and produce nothing if the debrief is handled poorly. You can run a relatively simple activity and produce a genuinely important insight if the debrief is done well.
This is not a secondary consideration. The debrief is the product.
Why the activity is not the development
David Kolb's experiential learning cycle is often cited in facilitation circles, and for good reason: it articulates precisely why experience alone is insufficient. The cycle has four stages — concrete experience, reflective observation, abstract conceptualisation, active experimentation. The simulation or activity covers the first stage. The debrief covers the next two. Without them, the cycle does not complete, and the experience does not produce transferable learning.
A treasure hunt with no debrief is entertainment. A well-run Resource Paradox simulation with no debrief is a competitive game that people remember as fun. Neither is experiential learning in any meaningful sense. The activity creates the raw material — behaviour under pressure, visible in real time. The debrief is where that raw material becomes something the participant can use.
The reason this matters is that the experience is already expensive. You've brought people together, you've run a facilitator, you've carved three or four hours out of a workday. Cutting the debrief short to stay on schedule — or worse, skipping it entirely because the activity ran long — means you've spent the budget and produced none of the development. In twenty-four years of running these programmes, I have never seen a team that didn't need the debrief. I have regularly seen teams try to skip it.
The three-phase debrief structure
The most robust debrief structure I know is three phases: What happened, So what, and Now what. Each phase has a distinct purpose, and conflating them — moving to insight before the observation is made, or jumping to action planning before the meaning is clear — is the single most common debrief failure mode.
Phase 1 — What happened? This phase focuses on observable behaviour, not interpretation. "What did you notice?" not "What went wrong?" The facilitator's job here is to gather data from the room without editorialising it. Participants describe what they saw, heard, and did. The facilitator reflects it back without judgment. This phase takes longer than most facilitators allow it to.
Phase 2 — So what? This is the meaning-making phase. What does the behaviour that just became visible tell us about how we operate? This is where analogies emerge — where someone connects a decision made in the simulation to a pattern in their actual organisation. The facilitator's job is to deepen the connection, not to provide it. The best insights in this phase are not given by the facilitator. They are surfaced from the room.
Phase 3 — Now what? This is the application phase. Not "what should people do in theory" but "what will you specifically do differently, in which situation, by when." This is the phase most often handled superficially — a round of generic commitments that nobody tracks. The facilitator's job is to push for specificity. "Communicate better" is not an action. "In the Monday team meeting, I will share the rationale for my decision before asking for input" is.
The facilitator's job in a debrief
A debrief facilitator is not a summariser, a trainer, or a therapist. Their specific function is to help the room see what the room already knows but hasn't yet articulated. This is harder than it sounds, because the facilitator usually has a clearer view of what happened than the participants do — they observed from outside the activity — and the temptation is to tell them.
Telling them is the failure mode. When the facilitator provides the insight, it belongs to the facilitator. When the insight emerges from a participant's own observation, it belongs to that participant. The latter is far more likely to produce behaviour change.
The most useful facilitator tool in a debrief is the question that opens — one that cannot be answered with a yes, no, or fact. "What made you decide to allocate the resource that way?" opens. "Did you feel pressure in that moment?" closes. One of these advances the debrief. The other terminates it.
The silence before an insight — the moment when a participant pauses because they are genuinely processing something — is valuable. Most facilitators fill it. The discipline is to wait. What comes after a genuine pause is usually more useful than what was about to be said before it.
What makes a debrief fail
Most debrief failures follow one of four patterns.
The first is rushing to the lesson before the observation is established. If participants haven't yet clearly described what happened — what decisions were made, what behaviour was visible — they cannot make meaning of it. Jumping to "so what this tells us about your organisation" before "here's what I saw myself do" produces abstract discussion that doesn't land.
The second is the "here's what this was about" facilitator move — where the facilitator explains the insight rather than surfacing it. This is usually well-intentioned and almost always counterproductive. It makes the debrief feel like a lecture. People disengage, and the observation that was about to become theirs becomes the facilitator's.
The third is group dynamics that suppress honest observation. A senior leader in the room who drove a particular decision is unlikely to be challenged about it, even in a debrief. The facilitator has to create conditions where observation is safe — which sometimes means naming the dynamic directly. "I'm noticing we're only hearing from some people. What's everyone else seeing?"
The fourth is action planning that nobody follows through on because it's too vague. The debrief ends on energy and the commitments dissolve by the following Monday. The fix is specificity in Phase 3, combined with a follow-up structure — even something as simple as asking participants to share their commitment with one other person in the room who will check in with them in two weeks.
The debrief question bank — 12 questions that work
The following questions are organised by debrief phase. They are not scripts — they are starting points. Use the ones that fit the room.
Phase 1 — What happened?
- "Walk me through the decision you made at that point. What information did you have, and what did you do with it?"
- "What did you notice about how the group was communicating during that phase?"
- "Who wasn't being heard in that sequence? What was happening that made that possible?"
Phase 2 — So what? 4. "What does this tell you about how your team handles situations where the priorities conflict?" 5. "Where have you seen this pattern before — not in the simulation, in your actual work?" 6. "What would have had to be different in the simulation for a different outcome? What's actually in your control?" 7. "What surprised you about how you operated under that kind of pressure?"
Phase 3 — Now what? 8. "What's one thing you'll do differently in the next month based on what you've just observed about yourself?" 9. "What would your team need to see from you to know that this conversation produced something?" 10. "Who in this room is going to hold you to that?" 11. "If you were to describe this debrief insight to a colleague who wasn't in the room, what would you say?" 12. "What condition needs to change in your organisation for the behaviour you've just identified to be possible?"
The full 12-question Debrief Question Bank is available as a download above.
Rupert's Take
The sign that a debrief has worked is specific: at least one participant says something about the simulation that is also true about their organisation. Not analogous. Actually true.
"In the simulation, we allocated the resource to the team that asked loudest, not the team that needed it most. That is exactly what we did in Q3 last year."
That moment — where the simulation becomes a mirror — is what a debrief is designed to produce. Everything before it is setup. When it happens, you don't need to do anything. The room does the work.
When it doesn't happen, it's usually because the facilitator moved too fast, or the group was too polished, or the debrief ran into lunch. None of those are the participants' fault.
Frequently Asked Questions
How long should a debrief take?
A debrief should be at minimum one-third the length of the activity it follows. For a two-hour simulation, that means at least forty minutes for the debrief. Most organisations underallocate this time and overestimate how much can be covered quickly. A good debrief cannot be rushed; if time is short, it's better to run fewer phases deeply than all three phases superficially.
Who should facilitate the debrief?
The debrief should be facilitated by someone who was not a participant in the activity and who does not have a line reporting relationship with anyone in the room. This is why external facilitators are often used even when the organisation has internal L&D capability — the power dynamics of an internal facilitator can suppress the observations that matter most. If using an internal facilitator, they should be explicitly briefed to observe rather than evaluate.
What questions should you never ask in a debrief?
Avoid questions that can be answered with a yes, no, or single word. Avoid questions that contain the answer ("Don't you think the problem was the communication breakdown?"). Avoid questions that direct blame toward a specific individual ("Why did you make that call?") rather than exploring behaviour ("What was behind that decision?"). And avoid "how did that make you feel?" as an opening question — it tends to produce polished emotional responses rather than honest observation.
Can you debrief without having observed the activity?
Yes, but the debrief will be shallower. When the facilitator has observed the activity, they can use specific moments as entry points: "I noticed at about the fifteen-minute mark, two of you stopped contributing to the main discussion. Can you tell me what was happening for you then?" Without that specific reference, the facilitator is working from what the participants volunteer. The debrief can still work, but it is harder to surface what wasn't being said.
What's the difference between a debrief and a feedback session?
A feedback session is evaluative — it tells participants how they performed. A debrief is exploratory — it helps participants understand their own behaviour. The facilitator in a feedback session has answers. The facilitator in a debrief has questions. The outcomes are different: feedback produces judgement about performance; a debrief produces insight about patterns. Both have a role in development. They are not the same thing.