Psychological Safety

A team performs better when its members share a belief that it’s safe to take interpersonal risks, admitting a mistake, asking a question, raising a concern, without expecting to be punished or embarrassed for it.

3 min read

What Is It?

Organizational behavior scholar Amy Edmondson introduced the concept in a 1999 paper studying hospital teams, defining psychological safety as a shared belief, held at the team level rather than as an individual trait, that the team is safe for interpersonal risk-taking. Her original study produced a counterintuitive pattern: better-functioning teams appeared to report more errors. Edmondson’s explanation was that psychologically safer teams were more willing to notice, discuss, and report mistakes, meaning the observed error counts likely reflected differences in openness as much as differences in underlying error frequency. Psychological safety isn’t the same as being comfortable or free of pressure or accountability, a team can hold each other to a very high standard, still deliver hard feedback, and still reject ideas, and remain psychologically safe, the safety is specifically about whether raising a problem, admitting uncertainty, or challenging an idea is likely to trigger humiliation, punishment, or status loss simply for having raised it. Google’s internal Project Aristotle research, published in 2015, later highlighted psychological safety as the most prominent factor associated with team effectiveness in its internal analysis, adding organizational weight to Edmondson’s academic finding, though as internal observational research rather than a controlled experiment, it established association rather than clean causal proof.

Why Does It Matter?

Information an organization needs, an early warning about a flaw, an honest status update, a challenge to a flawed plan, often lives inside individual employees before it ever becomes visible to anyone who can act on it. Whether that information surfaces depends heavily on whether the person holding it expects speaking up to be treated as a contribution or a liability. A team with low psychological safety doesn’t necessarily have fewer problems, it has fewer problems that get said out loud, which means leaders in that environment are making decisions on a systematically incomplete picture without any signal that the picture is incomplete.

This connects directly to several other patterns in the Field Guide. Low psychological safety can amplify Groupthink, Abilene Paradox, and Pluralistic Ignorance, since it raises the interpersonal cost of surfacing information that would disrupt apparent consensus, though each of those patterns also has mechanisms of its own beyond psychological safety alone.

What Changes Once You See It?

You start treating the absence of dissent, questions, or reported problems as something to investigate rather than something to take at face value, since silence is consistent with both “everything is fine” and “nobody feels safe saying it isn’t.”

You start paying close attention to how mistakes and bad news are actually received in the room, not just what’s said about how they should be received, since the gap between stated openness and the real reaction to the last person who spoke up is what people actually calibrate to.

You also get more deliberate about modeling the behavior yourself, visibly admitting your own mistakes and uncertainties, since psychological safety is established more by what leaders demonstrably do with bad news than by what they say they want to hear.

Common Misunderstandings

It isn’t the same as being nice, comfortable, or free of accountability. High-performing psychologically safe teams often hold each other to demanding standards, the safety is about whether raising a concern is treated as valuable, not about lowering the bar.
It isn’t a fixed personality trait of individual team members. It’s a property of a specific team and its recent history, the same person can behave very differently across two teams depending on how past instances of speaking up were actually received.
It doesn’t mean every idea or objection is treated as equally valid. Disagreement and rigorous challenge are part of a psychologically safe team, the safety is about not being punished for raising it, not about every objection automatically prevailing.
It isn’t established permanently once achieved. A single visible harsh reaction to someone raising a legitimate concern can damage psychological safety disproportionately, because everyone who observes it updates their own expectations about what will happen if they speak up next, which is why safety typically has to be maintained continuously rather than assumed to persist on its own.

Diagnostic Question

What actually happened the last time someone on this team raised a concern, admitted a mistake, or challenged a decision, and is that the outcome we’d want repeated?

Explore Further

Field Notes

None yet.

Related Field Guide

Origin

Amy C. Edmondson, “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly (1999), based on a study of hospital medical teams; later given broader organizational visibility through Google’s internal Project Aristotle research on team effectiveness, published in 2015.