How to Debrief a Medical Simulation

Reviews of simulation education keep arriving at the same conclusion: the debrief is where most of the learning happens. Remove it and the effect largely disappears, which makes it slightly odd that it is the component most often shortened when a session overruns.

The good news is that the evidence does not favour any single elaborate method, and it does not require a trained facilitator to produce most of the benefit. What it requires is a structure, a psychologically safe setting, and a focus on reasoning rather than outcome. This article gives you a structure short enough to actually use.

If you need a case to debrief, run one in the app first.

The five questions

Run these in order. Ten minutes for a twenty-minute case. Written down, they fit on an index card.

1. "What happened?" — establish the shared account first

Let the participants describe the case before anyone evaluates it. Two minutes, uninterrupted. This sounds like a formality and is not: people frequently have materially different accounts of the same case, and discussing decisions before agreeing on events produces an argument about facts rather than a discussion about reasoning.

2. "How did that feel?" — clear the emotional load

One minute. If someone found it stressful, frustrating or embarrassing, that needs saying before analysis starts, because an unspoken feeling distorts everything said afterwards. This is also where a facilitator earns trust: acknowledging that a case was hard makes the next eight minutes possible.

3. "What were you thinking when you decided X?" — the core of the debrief

Four or five minutes, and this is where the value is. Pick two or three specific decision points and ask about the reasoning behind each. Not "was that right" — "what were you weighing up". The purpose is to make the reasoning visible, because the reasoning is what transfers to the next case and the action does not.

The best version of this question includes your own observation and your own genuine curiosity: "I noticed you went back to check the airway after starting the fluids — I was curious what prompted that." That formulation, sometimes called advocacy paired with inquiry, states what you saw and asks about the thinking, and it consistently produces more honest answers than a bare question.

4. "What would you do differently, and what would you keep?" — both halves

Two minutes. The second half is not politeness. Naming what worked is how a behaviour becomes deliberate rather than accidental, and a debrief that only produces corrections teaches people that everything they did was wrong.

5. "What is the one rule you are taking away?" — force a generalisation

One minute, and everyone answers. It must be transferable and specific: "check the QRS width before reading the ST segments" rather than "be more careful with ECGs". Write it down. A debrief that ends without a portable rule tends to be forgotten within a week.

Four mistakes that make a debrief useless

• Judging by outcome. "It worked out, so that was fine" and "the patient died, so you got it wrong" are both errors. Decisions are assessed against the information available at the time. Good outcomes conceal bad reasoning, and that is the more dangerous of the two, because nobody investigates a success.
• The facilitator talking. A debrief where the person running it speaks for most of the time is a lecture. A reasonable target is that participants do seventy per cent of the talking. Silence after a question is usually someone thinking; wait it out.
• Quizzing instead of debriefing. "And what is the dose of that?" turns the room into an examination and shuts down disclosure of uncertainty immediately. Knowledge gaps found during a case are worth noting and addressing separately, not interrogating in front of the group.
• Skipping it because the case went well. The most common and most costly. A smooth case still contains decisions made for the wrong reasons, and those recur on a case that is less forgiving.

Debriefing yourself

Most practice happens alone, and a solo debrief is genuinely worthwhile, though it needs a modification: you cannot ask yourself what you were thinking and get a reliable answer, because you will reconstruct a more coherent version than the one you had.

The fix is to write during the case rather than after it. Before you act, note the action and one line of reasoning. Six or seven lines across a case. Then debrief against the notes rather than against your memory.

Two questions replace the five-question structure when you are alone. Where did my notes show hesitation? That is the gap worth reading about. And which decision would I make differently on the same information? That is your rule for the week.

Making it safe enough to be honest

A debrief only works if people will say what they actually thought, including that they were confused. Three things establish that, and all three are set before the case starts rather than during the discussion.

State the purpose explicitly. "This is practice, not assessment, and nothing said here goes anywhere." Say it every time, even with people who have heard it before.

Have the most senior person go first with a mistake. Not a token one. If the person leading the session describes a decision they got wrong and why, the room follows. If they do not, it usually does not.

Separate the person from the decision, in the language you use. "That decision had a risk attached" and "you were careless" describe the same event and produce completely different sessions. Being clear and direct about a problem is compatible with being decent about it; the two are not in tension.

Ten minutes, every time

If you take one thing from this: build the debrief into the time you allocate rather than treating it as what happens if there is time left. Twenty minutes of case plus ten minutes of debrief beats forty minutes of case, and the difference is not marginal.

Keep the five questions somewhere you can see them for the first few sessions. After about five debriefs the structure stops needing to be visible, and what remains is a habit of asking about reasoning rather than answers — which turns out to be useful well beyond simulation.