The scenario has just ended. Four learners are standing around a manikin that has stopped talking, adrenaline still up, each privately replaying the moment the monitor changed and nobody said anything for what felt like a very long time. The facilitator opens the door. What happens next will decide whether the last hour was education or theater.
Educators who run simulation well tend to say the same thing: the scenario is the stimulus, the debrief is the intervention. The INACSL Healthcare Simulation Standards of Best Practice include a standard devoted to the debriefing process, and the evidence base for simulation, summarized in our article on why simulation builds confident clinicians, comes from programs that debriefed with trained facilitators. Yet debriefing is the part most likely to be cut short when the schedule slips, and the part facility buyers most often forget to price.
This article is for both sides of the glass. For learners, it explains what a good debrief is trying to do and how to get more from one. For educators and facility buyers, it explains what structured debriefing requires, the named frameworks, how facilitator competence is assessed, and why the debrief should be budgeted before the manikin.
A scenario produces experience. Experience on its own does not reliably produce learning; people can run the same situation several times and draw the same wrong conclusion each time. What converts experience into changed practice is structured reflection: naming what happened, examining why, and deciding what to do differently. This is Kolb's experiential learning cycle in a clinical setting, and the debrief is where the reflection happens.
The INACSL standard on the debriefing process makes this explicit. It asks that debriefing be planned, be led by someone trained in the method, be based on a framework, be grounded in the session's objectives, and take place in an environment that supports honest reflection. Those requirements exist because an unstructured "so, how did that go?" conversation reliably produces the same result: the loudest learner speaks, the quiet ones nod, and the facilitator lists what went wrong.
Named frameworks exist so that facilitators do not have to invent a method under pressure. Debriefing with Good Judgment, developed at the Center for Medical Simulation in Boston, gives the facilitator a stance and a questioning technique. PEARLS, which stands for Promoting Excellence and Reflective Learning in Simulation, is a blended framework that lets the facilitator choose among learner self-assessment, focused facilitation and directive feedback depending on the objective and the time available. What the frameworks share matters more than what separates them.
A debrief only works if learners tell the truth about what they were thinking. That will not happen in a room where a wrong answer costs status. The faculty at the Center for Medical Simulation describe the goal as a safe container: a set of agreements, made in the prebrief and honored in the debrief, that make it possible to examine a mistake in detail without the person who made it feeling attacked.
The agreements are simple to state and hard to keep. Everyone in the room is assumed to be capable and trying to do well. The discussion is about reasoning and behavior, not about anyone's worth as a clinician. The facilitator is curious rather than critical. What is said in the room stays in the room. And the facilitator models the standard by admitting their own uncertainty when it exists.
For learners, psychological safety is not the same as comfort. A good debrief will make you uncomfortable in a specific and productive way: you will be asked to explain a decision you would rather not revisit. The safety lies in knowing that the question is about the decision, not about you, and that everyone in the room will get the same kind of question.
Strip the frameworks back and nearly all of them move through the same three phases. The names vary between frameworks; the sequence does not.
Reaction. The debrief opens by letting learners say how the scenario felt. This is not small talk. Strong emotion left unspoken occupies the attention that analysis needs, and the first thing a learner blurts out is often the most important thing the facilitator will hear all session. The facilitator listens, acknowledges, and notes what to return to.
Analysis. This is the long middle. The facilitator picks the moments that matter most for the objectives and explores them: what happened, what each person noticed, what they assumed, what they were trying to achieve. The goal is to reach the frame that produced the action. Some frameworks, PEARLS among them, add a short description step before analysis, in which the team agrees on what actually happened before anyone examines why.
Summary. The debrief closes by asking each learner to name what they are taking away and what they will do differently. A summary that ends with "great job, everyone" has failed. A summary in which each person states one specific change has done its work.
Facilitators face a genuine dilemma in the analysis phase. If they say plainly what they saw and what they think of it, they get compliance without learning. If they hide their view behind neutral questions, learners hear the judgment anyway and learn to guess what the facilitator wants. Debriefing with Good Judgment resolves this with a technique its authors call advocacy-inquiry.
The facilitator states what they observed, states their own view or concern about it, and then asks a genuine question about the learner's reasoning. Something like: "I noticed that after the monitor changed, some time passed before anyone spoke. I was concerned, because the objective was recognizing change early. I am curious what was going through your mind at that point." The observation is specific, the judgment is owned rather than hidden, and the question is real.
Learners can use the same structure in reverse: if you are unsure why a facilitator is asking something, ask what they saw. The technique works because it makes the facilitator's frame visible too, and because it produces the answer that matters: what you were thinking.
Debriefs go wrong in predictable ways, and each failure has a name. Knowing the names helps facilitators catch themselves and helps learners say what is happening.
Lecturing. The facilitator uses the debrief to deliver the content they wanted to teach anyway. Learners sit, nod and retain very little, because nothing has connected the content to the decision they actually made.
Rescuing. The facilitator sees a learner becoming uncomfortable and smooths it over before the reasoning has been examined. It feels kind. It removes the moment the learner most needed to sit with.
Judging. The facilitator asks questions that are really verdicts, or lets one learner's error become the group's example without their consent. Psychological safety collapses, and everyone in the room learns to say less.
Running out of time. The scenario overran, the next group is waiting, and the debrief becomes a brief list of what went wrong. This is the most common failure, and it is the one facilities can prevent by scheduling rather than by skill.
Learners who know these patterns can name them without being rude. Asking to come back to the escalation decision before time runs out is a legitimate request, and a facilitator working to the INACSL standards will take it as one.
Debriefing is a skill, and like any skill it is learned, practiced and assessed. The INACSL standards expect facilitators to be trained in the debriefing method they use, and the Society for Simulation in Healthcare's Certified Healthcare Simulation Educator credential exists partly to recognize that training. An excellent clinician is not automatically an excellent debriefer, for the same reason our article on preceptor development gives for preceptors: expertise makes your own reasoning invisible to you.
There is a validated instrument for assessing debriefing itself. The Debriefing Assessment for Simulation in Healthcare, known as DASH, was developed at the Center for Medical Simulation and describes the behaviors an effective debriefer shows, from establishing an engaging learning environment through to helping learners identify and sustain good performance. It exists in versions for trained raters, for facilitators rating themselves, and for learners rating the debrief they received. Programs use it for facilitator development and quality review, not to grade learners.
For facilities choosing a training partner, the useful questions follow directly: which framework do your facilitators use, how were they trained in it, and how do you assess your debriefing? A partner who can answer all three will produce learning rather than an afternoon with a manikin.
Arrive with your reasoning available. During the scenario, notice what you are noticing and what you are assuming, because the debrief will ask.
Speak in the reaction phase. The thing you most want to keep quiet is usually the thing the group most needs to hear, and saying it first makes honesty easier for everyone else.
Answer the actual question. A question about what you were thinking is not an invitation to defend yourself. Describe the frame, including the assumptions that turned out to be wrong.
Ask for the observation. If feedback feels vague, ask what the facilitator saw and when. Specific observations are the raw material of learning; verdicts are not.
Leave with one change. Write it down in the summary phase and take it to your next clinical day, or to your preceptor if you are in orientation. One concrete change per learner is worth more than a lecture's worth of slides.
When a facility prices simulation training, the visible costs are equipment, space and the scenario itself. The invisible cost, and the one that determines whether the training works, is facilitator time for debriefing. Our article on simulation fidelity and what the money buys makes the point that a program which funds the manikin and not the facilitator has bought a prop. The same logic applies to schedules.
A session plan that gives most of its time to the scenario and squeezes the debrief into whatever remains is a plan to produce the fourth failure above. Facilities should ask a training partner for the session plan with debrief time stated, should expect the debrief to be at least as long as the scenario and often longer, and should treat a plan that cannot show that as a warning sign. Small-group debriefing also caps the number of learners a facilitator can serve per session; a partner who claims to debrief a whole department in the same slot is describing a lecture.
The return on this time is what shows up on the unit. Behaviors examined in a debrief transfer; behaviors merely performed in a scenario often do not. Our article on measuring the ROI of clinical training shows how to make that argument to a finance team; the short version is that debrief time is the part of the training that produces the outcome you are paying for.
What is the difference between a debrief and feedback? Feedback is information given to you about your performance. A debrief is a structured conversation in which you examine your own reasoning with a facilitator's help. Good debriefs include feedback, usually in the form of specific observations, but their purpose is to surface the frame behind your actions so that it can change. The INACSL Healthcare Simulation Standards of Best Practice describe the debriefing process as a facilitated, framework-based reflection rather than a report card.
How long should a debrief last? It depends on the objectives, the number of learners and the framework, so there is no single figure. As a working principle, educators expect the debrief to last at least as long as the scenario it follows and often longer, because analysis takes time and each learner needs a turn. If a session plan gives the debrief a fraction of the scenario's time, ask why; running out of time is the most common way a debrief fails.
What should I do if a debrief feels like a lecture or an interrogation? Name it, politely and specifically. Ask to go back to the moment that mattered and say what you were thinking at the time; that turns a lecture back into a debrief. Ask what the facilitator saw at that point; that turns a verdict back into an observation. Facilitators trained in advocacy-inquiry will welcome both. If the pattern persists across sessions, raise it with the program through its usual feedback route.
Can a facility run debriefs with its own staff educators? Yes, provided those educators have been trained in a debriefing framework and have the scheduled time to use it. Many facilities pair an external simulation partner with their own educators for exactly this reason: the partner brings trained facilitators and a session plan with debrief time built in, and the facility's educators learn the method alongside their staff. Ask any training partner how it develops facility educators as debriefers.
Wahero's simulation training, in our own simulation lab and on site at facilities across Texas, is built with the debrief as the core of every session: trained facilitators, a stated framework, and debrief time scheduled in writing. For students and new graduates that means scenarios that change what you do next; for facilities, competency validation and workforce training that produce learning rather than a signature.
Related reading
Educational content only
This material is published by Wahero Health Institute for professional education and is not individual medical advice, a care protocol, or a substitute for clinical judgment. Always follow your facility's policies, your state's nurse practice act, and your own scope of practice, and confirm medication doses against a current authoritative reference before administration. See our Terms of Use.
