Specialty Digest

DISCOVER IDEAS THAT SHAPE OUR WORLD

What Is Psychological Safety at Work?

Amy Edmondson's research shows the highest-performing teams aren't the ones with the fewest problems — they're the ones safe enough to talk about them.

Share
Link copied

Psychological safety at work is the shared belief among a team that speaking up, admitting a mistake, or challenging an idea won’t get someone punished or humiliated for it. It’s not about being nice or avoiding disagreement; it’s the split-second calculation behind whether a junior engineer who spots a flaw in a senior colleague’s plan says so in the meeting, or stays quiet and hopes someone else raises it.

Where the concept comes from

The term comes from Harvard Business School professor Amy Edmondson, who defined it in 1999 research as a shared belief among team members that the team is safe for interpersonal risk-taking. Her studies of hospital units found something counterintuitive at the time: the teams that reported more errors weren’t necessarily making more mistakes, they were the teams safe enough to actually talk about the mistakes they made rather than burying them, which is what let those units catch and fix problems that other units simply never surfaced. Edmondson later expanded the idea into her book “The Fearless Organization,” arguing that psychological safety isn’t a soft add-on to good management but a precondition for teams to learn and improve at all.

Why it became a mainstream business priority

The idea moved from academic research into everyday management conversation largely after Google’s internal research project, known as Project Aristotle, studied dozens of its own teams to figure out what separated the highest performers from the rest. Team composition, seniority, and even how extroverted members were mattered far less than how team members treated each other; psychological safety consistently emerged as the factor underlying the other traits of effective teams, reinforcing what Edmondson’s academic work had already found in a very different setting.

What it isn’t

It gets misread constantly as a synonym for comfort, consensus, or lowered standards, a workplace where no one is ever challenged. Harvard Business Review’s coverage of the concept is explicit that this is a misunderstanding: psychologically safe teams still disagree, still deliver hard feedback, and still hold each other accountable. The difference is that criticism gets aimed at the work, not the person, and raising a problem is treated as a contribution rather than a complaint, which is why teams with real psychological safety tend to show more visible conflict, not less. They simply handle it productively instead of avoiding it.

How leaders actually build it

Psychological safety isn’t installed with a values poster; it’s built through how a leader responds in the specific moments that test it. That means visibly rewarding someone who flags a mistake or a risk instead of letting the message get lost in who delivered it. It means a leader admitting their own errors first, since people calibrate how much honesty is safe by watching what happens to the leader when they’re wrong. And it means asking real, non-rhetorical questions in meetings and waiting long enough for someone to actually answer honestly.

Teams that get this right catch problems earlier, because someone is willing to say “I think this is going to fail” before it does rather than after, and they learn faster, since near-misses and outright failures get discussed openly instead of quietly shelved. None of that requires a dramatic culture overhaul; it starts with a leader consistently making it clear, in small daily moments, that speaking up is safer than staying silent.

Sources & References
  • Harvard Business Review, “What Is Psychological Safety?” Article.
  • Amy C. Edmondson, “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly (1999). Overview.
  • Photo: userpilot1, CC BY 2.0, via Flickr.
Share
Link copied

Leave a Comment

Your email address will not be published. Required fields are marked *