Psychological Safety in Simulation
Psychological safety is the belief that an environment is safe for interpersonal risk taking, so learners can speak up, ask for help, test an idea that may be wrong, and admit a mistake without expecting embarrassment or retribution. Amy Edmondson introduced the construct in organizational research on work teams in 1999, defining team psychological safety as a shared belief that the team is safe for interpersonal risk taking, and simulation educators later adapted it to the classroom and the sim lab. In healthcare simulation it is treated as a precondition rather than a courtesy, because a learner who is managing their professional image is not doing the reflective work the encounter was built for.
The lineage matters because it explains what the term does and does not mean. Edmondson studied work teams in a manufacturing company and found that team psychological safety was associated with learning behavior, and that learning behavior mediated between psychological safety and team performance. The learning behaviors she described are recognizable to anyone who has run a debrief: reflecting on action, seeking feedback, speaking up about what you think, asking for help, and testing ideas that might turn out to be wrong. Simulation borrowed the construct because those are exactly the behaviors a debrief depends on.
Jenny Rudolph, Daniel Raemer, and Robert Simon carried it into healthcare simulation with the idea of a safe container, an environment where learners face professionally meaningful challenges and are held to high standards in a way that engages them without intimidating or humiliating them. Their point is that safety and rigor are not opposites. A debrief can be direct about a missed diagnosis and still be psychologically safe, and the reason to build the container is precisely so that faculty can be honest about performance without triggering the defensive behaviors that shut a conversation down.
They name four practices, and all four belong to the presimulation briefing rather than the debrief. Clarify expectations, covering objectives, environment, roles, and confidentiality. Establish a fiction contract, the mutual agreement that everyone will engage with an imperfect simulation as if it were real. Attend to logistic details, which sounds minor until a learner spends the scenario hunting for equipment. Declare and enact a commitment to respecting learners and to caring about their psychological safety, and the enacting half is the one that gets skipped, since learners read the gap between what faculty say and what faculty do.
The Healthcare Simulation Dictionary defines it for simulation as a feeling, explicit or implicit, that participants are comfortable participating, speaking up, sharing thoughts, and asking for help without concern for retribution or embarrassment. The INACSL debriefing standard requires that the process maintain psychological safety and confidentiality, which makes it an accreditation-relevant condition and not a soft preference. It is also fragile in the way hierarchy makes things fragile. A resident who suspects the debrief will surface in an evaluation letter will manage what they say, and no amount of stated commitment fixes that if the program actually does it.
What this looks like in a program
- Separate formative practice from summative assessment in the learner's mind and in your records, because a debrief that feeds an evaluation is not a safe container no matter how it is introduced.
- State the fiction contract explicitly in the prebrief, then hold your side of it when the simulation does something implausible mid-scenario.
- Watch what happens when a senior physician is in the room. Learners calibrate to hierarchy, so co-facilitation and seating are part of the design, not details.
- Let learners rehearse privately with AI patients before a graded encounter. Low-stakes repetition takes some of the exposure out of the observed one.
Related terms
Read next
Last updated August 2026