Psychological Safety: Why the Best Teams Report More Mistakes
Psychological safety explained through Amy Edmondson's research and Google's Project Aristotle: a real example, and how to build it as a leader.
Psychological Safety
Psychological safety is a shared belief within a team that it is safe to speak up, ask questions, admit mistakes, or raise concerns without fear of embarrassment or punishment, distinct from simply being a comfortable or friendly place to work.
Psychological safety describes a specific, measurable team condition, not a general feeling of niceness: whether a person believes that taking an interpersonal risk, disagreeing publicly, admitting an error, asking what might be seen as a basic question, will be met with a reasonable response rather than humiliation or quiet punishment.
What does psychological safety mean?
The concept was developed by organizational researcher Amy Edmondson, who found in studies of hospital teams that higher-performing teams actually reported more errors, not fewer, because their culture made it safe to surface mistakes early rather than hide them. Lower-performing teams reported fewer errors while, on independent observation, actually making more, they were simply less safe places to admit them.
The concept gained wider attention through Google's internal Project Aristotle research on team effectiveness, which tested numerous factors, individual talent, team composition, working style, and found psychological safety was the single strongest predictor of a high-performing team, ahead of any factor related to who was actually on it.
Why does it matter?
Psychological safety matters directly to outcomes, not just team morale: teams without it tend to catch problems late, since the people who notice something early are the least likely to say so, and innovation suffers specifically because untested or half-formed ideas, which are how most good ideas start, feel too risky to voice.
It also matters because low psychological safety is often invisible from the top. A leader can feel entirely approachable while a team quietly filters everything it says to that leader, and the gap between the two only becomes visible once something has already gone wrong.
Example
A junior engineer notices a potential flaw in a deployment plan two days before launch but says nothing, having watched a colleague get publicly criticized for raising a similar concern months earlier. The flaw causes a costly outage on launch day, one the engineer could have flagged in time, in a team with a different reputation for how concerns get received.
Common misunderstanding
Psychological safety is often confused with comfort or the absence of conflict, as if a psychologically safe team never disagrees or challenges each other. Edmondson's research points the other way: the safest teams tend to have more direct disagreement and more visible mistakes, not less, because both become safe to surface rather than something to hide.
In practice
Building it usually starts at the top, specifically with how a leader responds the first few times someone raises a concern or admits a mistake. A single visible, calm, non-punitive response to bad news tends to do more than any stated policy, since teams learn what is actually safe by watching what happens, not by being told.
How did I actually respond the last time someone on my team raised a concern or admitted a mistake?
Is there a question or concern people in this room are likely quietly holding back right now?
What would it look like to visibly reward, rather than merely tolerate, the next person who speaks up early?
Common questions
Is psychological safety the same as low standards or no accountability?
No. Edmondson's own framing pairs psychological safety with high standards, not against them; the combination, not safety alone, is what produces strong performance.
Can one person build psychological safety on a team, or does it require the whole group?
A leader's response carries disproportionate weight, but genuine safety is a shared team property, and it can erode quickly if even a few members consistently punish candor.
Related concepts
Related glossary entries: Difficult Conversations, Leadership Under Pressure, Boundaries.
Continue exploring
Work through how a team actually experiences your leadership, not just how you intend it.
Explore coaching