Psychological Safety: Create a Team Climate To Make Honesty Feel Safe
Psychological safety helps managers create a team climate where people raise problems, admit mistakes and challenge ideas early, using nonviolent communicati…
Topic: Teamwork & Collaboration
Why It Matters
A project slips by three weeks. In the review, it emerges that two people on the team saw the problem coming in week one, and neither said anything. When you ask why, the answers are vague: they assumed someone else had flagged it, they weren't sure it was their place, and the last person who raised a concern in a team meeting was shut down.
Silence like this is expensive, and it rarely shows up on a dashboard until the damage is done.
Psychological safety is the name for the condition that prevents it. It describes a team climate in which people believe they can speak up, ask questions, admit mistakes and challenge ideas without being punished or humiliated.
It is not about being nice or lowering standards. It is about making sure the information, concerns and ideas that already exist inside your team actually reach the people who need them.
The concept matters more now because work has become more interdependent and less predictable. Hybrid teams, cross-functional projects and fast-moving markets mean no single manager can see every risk.
Your team's willingness to tell you what they see is one of your most valuable early-warning systems, and one of the clearest signals of your credibility as a leader.
A few questions can help you judge whether this deserves your attention right now.
When something goes wrong, do you usually hear about it from your team first, or from someone outside it?
In your last few meetings, did anyone other than you or your most senior person disagree with a proposal?
When a team member makes a mistake, does the conversation that follows focus on learning or on blame?
Origin & Underlying Logic
In formal terms, it is a shared belief, held by members of a team, that the team is safe for interpersonal risk-taking.
The idea first appeared in organisational change research by Edgar Schein and Warren Bennis in the 1960s, but it was Harvard professor Amy Edmondson's study of hospital teams in the late 1990s that brought it into mainstream management thinking.
Edmondson found, unexpectedly, that better-performing teams reported more errors, not fewer. They weren't making more mistakes; they were more willing to talk about them.
Google later reinforced the idea through its Project Aristotle research, which identified psychological safety at work as the strongest factor distinguishing its most effective teams.
The underlying logic is simple: learning and performance depend on information flow, and information flow depends on whether people judge the interpersonal cost of speaking up to be worth paying.
Two design assumptions sit underneath the concept.
It operates at the team level: two teams in the same company can have very different climates.
It is not the opposite of accountability. Edmondson pairs safety with high performance standards. Teams with safety but no standards drift into comfort, while teams with standards but no safety drift into anxiety and silence.
This is where nonviolent communication (NVC) becomes useful. Developed by psychologist Marshall Rosenberg, NVC gives managers a practical language for addressing problems without triggering defensiveness. Its four components (observations, feelings, needs and requests) separate what happened from judgements about the person.
That separation is exactly what a team needs to see, repeatedly, before it trusts that honesty won't be punished. Related schools of thought include Timothy Clark's four-stage model, Kim Scott's Radical Candor and the blameless review practice used in engineering and healthcare.
Structure & Application
Psychological safety is not a tool you deploy; it is a condition you build through repeated behaviour. Edmondson describes the manager's role as three linked moves, and NVC gives you the language to carry out each one consistently.
Setting the stage. This means framing work explicitly as uncertain or interdependent, so speaking up is positioned as part of the job rather than a personal risk. When you say "this plan has gaps we haven't found yet, and I need your help finding them", you change what silence means.
Inviting participation. Asking genuine questions, acknowledging the limits of your own knowledge and creating structured moments for input all signal that contributions are wanted. Invitation matters because people don't assume permission; they need to see it given.
Responding productively. This is where most of the climate is decided. How you react when someone brings bad news, admits an error or disagrees with you teaches the whole team what speaking up costs. Here NVC does its heaviest lifting.
Instead of "you dropped the ball on the client report", an NVC response sounds like this: "The client report went out two days after the deadline (observation). I'm concerned (feeling), because we committed to that date and I need the client to trust our timelines (need). Can we talk through what got in the way, so we can plan around it next time? (request)".
The problem is still addressed directly, but the person is not attacked.
The three moves depend on each other. Invitations without productive responses feel like traps, and productive responses rarely get the chance to happen without invitations.
Some teams formalise the approach with blameless reviews or team working agreements; others build it informally through the manager's daily conduct.
Either way, it works best at the team level, where one manager's behaviour shapes the climate most directly.
In format, the concept usually appears in two ways: as a 2x2 matrix (safety against accountability) for diagnosing a team's current state, and as a conversation structure (the four NVC components) for day-to-day practice.
Quick-start: In your next one-to-one, ask one team member: "What's something you've noticed on the team that you haven't felt able to raise?" Then listen, and thank them, whatever you hear. The harder question, and the one that decides whether that conversation builds trust or erodes it, is what you do with their answer over the following week.
FAQ
Q: What is psychological safety in simple terms?
A: It is a shared belief within a team that you won't be punished or embarrassed for speaking up with ideas, questions, concerns or mistakes. It describes the team's climate rather than any individual's personality. A psychologically safe team still holds high standards; its members simply feel able to be candid about what is and isn't working.
Q: Is psychological safety the same as being nice or avoiding conflict?
A: No. Teams that avoid conflict to keep things pleasant usually have low psychological safety, because people are holding back disagreement. A safe team can debate hard, challenge decisions and give blunt feedback, because members trust that candour won't damage their standing or relationships. The difference is that disagreement stays focused on the work, not the person.
Q: How is nonviolent communication related to psychological safety?
A: Nonviolent communication is a method built on four components: observations, feelings, needs and requests. It helps a manager address problems without blaming or labelling people. Because team members watch closely how their manager responds to bad news and disagreement, consistent use of NVC is one of the most direct ways to show that honesty is safe. Applying it under pressure is covered in the deep dive.
Q: Can psychological safety exist in a small team or a high-pressure environment?
A: Yes. Team size matters less than the manager's behaviour, and small teams can shift their climate quickly because every interaction is visible. High-pressure settings such as hospitals and emergency services are where the concept was first studied in depth, precisely because silence in those environments carries a real and immediate cost.
Q: How do I know if my team needs to work on psychological safety?
A: Look for patterns of silence rather than complaints. If problems surface late, meetings produce little disagreement, the same few people do most of the talking, or mistakes are discovered rather than reported, your team's climate is worth examining. A short anonymous pulse survey can then confirm or challenge what you are observing.