What psychological safety actually means and how to build it in your team
Psychological safety has become one of those phrases that gets used so frequently it has started to lose its edges.
In some organisations it has become shorthand for a nice place to work. A culture where people get along, where the office has good snacks and a ping pong table, where nobody raises their voice. That is not what it means. And the confusion matters because it leads to well-intentioned organisations doing the wrong things in pursuit of it.
Amy Edmondson, the Harvard researcher who developed the concept, defines psychological safety as the belief that you will not be punished or humiliated for speaking up with ideas, questions, concerns or mistakes. It is not about comfort. It is not about absence of conflict or challenge. It is specifically about whether the people in a team believe it is safe to be honest.
That is a much harder thing to create than a good office culture. And it has much larger consequences.
Why it matters more than most organisations realise
Google's Project Aristotle, a years-long internal study into what made teams effective, found that psychological safety was the single most important factor. More than individual talent. More than clear goals. More than team composition.
Teams where people felt safe to speak up, admit mistakes and raise concerns consistently outperformed teams where they did not. The mechanism is fairly intuitive once you see it. When people can be honest, problems surface early. When they cannot, problems hide until they are too large to ignore.
This plays out in small ways constantly. The junior team member who spots a potential issue but does not say anything because they are not sure it is their place. The manager who knows a project is in trouble but does not escalate because the culture does not reward honesty about setbacks. The employee who is struggling but does not say so because the unspoken message is that struggling means you are not up to it.
Every one of those silences has a cost.
What it is not
Because the concept gets misunderstood so often, it is worth being explicit.
Psychological safety is not the same as everyone being nice to each other. Teams with high psychological safety often have robust, direct disagreements. The difference is that those disagreements are about ideas and work, not about whether it is safe to participate in the conversation at all.
It is not about protecting people from accountability. In fact, Edmondson's research suggests that psychological safety and high standards of performance work together rather than in tension. Teams where people feel safe tend to hold each other to higher standards because feedback can be given and received honestly.
It is not something you can create with a single initiative. A team away day, a workshop, a values document. These things are not meaningless but they do not build psychological safety on their own. Safety is built through accumulated experience of how the leader responds when people are honest. It is rebuilt or eroded with every interaction.
How leaders build it
The behaviours that create psychological safety are not complicated. They are just easy to skip when you are busy or under pressure, which is most of the time.
Responding to honesty without punishing it. When someone raises a concern or admits a mistake, the response they get is the data point the whole team is using to decide whether it is safe for them to do the same. A leader who reacts with frustration, dismissal or blame when things go wrong trains their team, quickly and thoroughly, not to tell them when things go wrong.
Admitting what you do not know. Leaders who project certainty about everything create teams where uncertainty feels like weakness. Leaders who say I am not sure about that or I was wrong about this give their teams permission to do the same, which tends to result in better decisions and more honest conversations.
Asking and then actually listening. Questions like how is this going or what would make this work better are useful when the leader genuinely wants to hear the answer. When the question is performative, people clock that quickly and answer accordingly.
Following up. If someone raises something and nothing happens, the message is clear. If you raise it and something does happen, or at least gets properly acknowledged, the message is equally clear. Consistency between what you say you value and what you actually do with information you receive is where trust is built or lost.
What low psychological safety looks like
Teams with low psychological safety tend to have a particular texture to them.
Meetings where the discussion that actually matters happens in the corridor afterwards, not in the room. Feedback that flows downwards but not upwards. People who are skilled at managing their visibility, saying the right things to the right people, rather than focusing on the work. A lot of apparent agreement that does not reflect what people actually think.
The leader in this environment is often the last to know when something is wrong. Not because people are hiding things out of malice but because the environment has taught them that honesty about problems is riskier than absorbing them quietly.
By the time a problem becomes impossible to hide, it has usually been developing for a long time.
The question worth asking yourself
If you lead a team, the most useful thing you can do with this is not to assess your team's psychological safety in the abstract but to think about a specific recent situation.
When something went wrong in the last few months, how did you find out about it? Did someone come to you early, when something could still be done about it? Or did you find out late, when the options had narrowed?
The answer to that question tells you more about the environment you have created than any survey or framework.