How to debrief an experiential session so the learning sticks

A simulation produces about ninety minutes of shared, observable behaviour. Everybody in the room saw the same thing happen. That is a rare asset in corporate learning, and most sessions waste it in the first four minutes of the debrief by telling people what it meant.

The transfer does not happen during the game. It happens when a participant says, out loud, in front of colleagues, that what they just did is what they always do. You cannot say that on their behalf. You can only build the conditions in which they say it themselves.

Take notes on behaviour, not on outcomes

Scores are the least useful thing you will carry out of the room. Every team knows the score already, and nothing that matters is in it.

What you want is specific, timestamped behaviour:

• Who spoke first in each team, and whether that changed across rounds
• The moment a team stopped planning and started executing, and what triggered it
• Who was not consulted on a decision that affected their role
• A plan that was abandoned, and whether anyone said so out loud or it just quietly stopped
• The first time a team traded with another team, and how long they spent deciding to

Four or five of these, written down as they happen with the round number attached, will carry an entire debrief. Without them you are reduced to asking how people found it.

Run it in four movements

The order matters more than the questions. Each movement only works if the one before it has actually happened.

One: what happened

Purely factual, and shorter than feels natural — five minutes at most. Ask each team to state what they did, not why. You are establishing a shared account of events before anybody starts defending theirs.

This step exists because teams frequently disagree about the facts. Two teams remember the same trade differently. Surfacing that early is useful; discovering it mid-argument twenty minutes later is not.

Two: what it felt like

Now you go to reaction, and this is the only part of the debrief where feelings are the point. Frustration, relief, the specific irritation of watching another team take a resource you had planned around.

Keep it brief but do not skip it. Participants cannot analyse their own behaviour while they are still annoyed about it. The naming discharges enough of that to make the next movement possible.

Three: why you did that

This is the debrief. Everything before it was preparation.

Take your notes and put a single specific behaviour on the table without judgement attached:

In round two, your team spent eleven minutes planning and then abandoned the plan in under a minute when the event card came out. What happened there?

Specific, timestamped, and it does not tell them what it means. That question routinely produces ten minutes of genuine conversation. "How did your team handle change?" produces nothing, because it is not a question about anything that happened.

Follow the answers. If a team says they abandoned the plan because nobody owned it, you have a conversation about decision rights. If they say they abandoned it because one person spoke louder, you have a different one. Neither is the conversation you planned, and both are better.

Four: where else does this happen

The transfer question, and the only one worth a full slide.

Where does that same pattern show up here, outside this room?

Then wait. This is the longest silence in the session and facilitators consistently break it too early. Ten or fifteen seconds feels unbearable from the front of the room and is completely ordinary from a chair.

When somebody does answer, they will name something real about their own organisation. That is the moment the session earns its fee. Write down what they say — verbatim, in their words — because it belongs in the report to the sponsor more than any score does.

The four failures

Summarising. The facilitator explains what the group learned. The group agrees politely, because agreeing is easier than arguing, and nothing transfers. If you find yourself talking for more than ninety seconds at a stretch, you have stopped debriefing.

Only debriefing the winners. The winning team's behaviour is usually less interesting, because success hides the decision process. The team that collapsed in round three has more to say, and saying it in front of the room is the most valuable thing that happens all day. Protect them while you do it.

Debriefing the game instead of the work. Long conversations about strategy inside the simulation. Enjoyable, and worth nothing on Monday. The game is a pretext; if you are still talking about resource cards at minute thirty, you never left it.

Running out of time. Almost universal, and it is a design decision, not an accident. A session that overruns will always overrun into the debrief, because the game has a clock and the debrief does not. Give the debrief its own protected slot and end the game early if you have to. A truncated game with a full debrief beats a complete game with a rushed one, every time.

A note on group size

Everything above assumes a room you can hear. Above roughly forty people, plenary debriefing stops working — the people at the back stop contributing and the conversation narrows to the same four extroverts.

Past that size, run the third movement in the teams themselves, with a written prompt and a nominated reporter, then take two or three reports into plenary for the fourth. It is less rich and it is the only thing that scales. For a five-hundred-person session, expect table-level debriefing with a facilitator guide, and design the game so the pattern is obvious enough to survive being reported second-hand.

---

Every HDX simulation ships with a facilitator guide that includes the debrief structure, the questions that reliably work for that game, and the behaviours worth writing down while the rounds run. See the catalogue, or book a call if you are considering licensing.