What Psychological Safety Really Means (and Why Most Leaders Get It Wrong) 

When a leader asks me what psychological safety is, I usually start by telling them the name is wrong. Not slightly off. Wrong in a way that does real damage. 

“Safety” suggests protection from harm. What the term describes is actually closer to the opposite. It’s an environment where saying the difficult thing is still risky, and people say it anyway, because the team has made that risk survivable.  

The word points leaders toward comfort when they should be aiming at candor, and most of the failed attempts I’ve seen trace back to that one misread. 

A better working definition is a team where people speak their minds and respectfully challenge ideas without fear of retribution. Nobody gets gaslit. Disagreement is expected, not merely tolerated. 

You also can’t force it. Psychological safety is a by-product of getting other things right. 

Four ways “psychological safety” is misunderstood 

Amy Edmondson’s 1999 research on team learning gave us the modern concept of psychological safety. Google’s Project Aristotle turned it into a boardroom phrase around 2015. Popularity brought on the misinterpretations of the concept. These are the misreads I run into most: 

  • The right to say whatever you want, whether or not it’s respectful. Safety is not a license to behave badly.  
  • The absence of critical feedback. An environment with no critical feedback is not safe, it is quiet. Those are very different conditions that look identical from the org chart. 
  • A mandatory state of openness, where people are expected to disclose personal experiences, feelings or preferences. Nobody owes their employer access their personal life. Requiring disclosure is itself a form of pressure. 
  • The right to retribution when you don’t get what you want. When “I did not feel safe” becomes the way to relitigate a decision that went against you, the concept stops being about candor and becomes a lever. 

That last one gets almost no airtime and does the most harm. Once teams see the concept used for retribution, they learn fast. Then, nobody raises anything real again. All four treat safety as an entitlement the organization hands to individuals. It works better understood as a condition a team produces together. 

How leaders get it wrong 

Many leaders mandate safety, but you can’t require something only trust produces. They open with “How do we create a psychologically safe environment?” when the better first question is “What is actually true about our culture right now?” Or they declare “This is a safe space, speak your mind” in a room where several people are visibly uneasy. In each case, leadership is announcing safety instead of demonstrating it. 

The trickier situation comes from leaders who are trying. I worked with a leadership team that routinely asked for ideas, listened carefully, thanked everyone, and then did exactly what they’d planned anyways. Everyone was perfectly pleasant about it, but it was devastating. The organization learned that input was welcome but didn’t matter.  

Smaller habits send the same signal: A leader who nods more at the person who agrees with them. One who speaks first and narrows the range of acceptable answers. Your lead running the conversation about their own team’s performance. Leaders rarely notice themselves doing these things. Meanwhile, everyone else notices right away.  

The three conditions that empower psychological safety 

Psychological safety isn’t manifested from thin air. It shows up once certain conditions are in place. 

In the teams I’ve coached, safety follows these three conditions: 

1. Shared purpose and context. Ask three people separately what the team is trying to accomplish this quarter. If you get three different answers, every disagreement turns personal, because there’s no common standard to disagree against. 

2. Feedback loops built to surface hard conversations. Picture a retrospective where an engineer says the roadmap is wrong, and the product manager changes it right there in front of everyone. One visible moment like that teaches a team more about whether speaking up is worth it than any statement of values. 

3. High expectations, stated plainly. Leaders tend to skip this one because it sounds like the opposite of safety. It isn’t. When nobody knows what “good” looks like, staying quiet is the rational move. Clear expectations give people something concrete to push against. 

Be careful not to mistake comfort for safety. You can get a pleasant, conflict-free team just by lowering the stakes. Psychological safety means raising the stakes and making them survivable. A team that never argues hasn’t arrived somewhere healthy. It has stopped bothering. 

What to do Monday morning 

Start by looking in the mirror. When did someone last change your mind in a meeting? Then look at your own habits and be specific about which ones make it easier to hear bad news and which make it harder. 

Next, talk with your direct reports. Have conversations, not a survey. And don’t ask how safe they feel. You’ll get a polite answer, and that politeness is exactly what you’re trying to detect. Ask about things that already happened: 

  • “Think about the last time you had a concern and didn’t raise it. What stopped you?” 
  • “When did you last tell me I was wrong, and what happened after?” 
  • “What are we doing right now that you think is a mistake?” 

The first question assumes the moment happened, which it did for everyone, so nobody has to confess first. If nobody can answer the second, that’s your finding. The third is the most uncomfortable. If it’s met with silence, that’s an answer in itself.  

One condition applies to all of this. Don’t ask unless you’re willing to change based on what you hear. Most organizations I see with a visible safety problem didn’t get there by never asking. They got there by asking often and acting rarely. 

When to bring in the experts 

Leaders are rarely the best judges of their own culture, because they’re the people others are being careful around. An outside facilitator can run the honest conversation the leader can’t. And they can help turn what comes out into changes people can actually see. 

That’s a big part of what we do at Sprightbulb: helping teams get clear on purpose and build feedback loops that work. The goal isn’t a safer-sounding culture. It’s a team that tells you the truth early enough for it to matter. See our services that help teams work better together.  

More Blogs

Why is Agile Scaling So Hard
blog

Why Is Scaling Agile So Hard?

Agile scaling is always a hot topic for students and organizations dealing with the complexities of multi-team execution. The question I get asked most often is one that sounds the simplest: “Why does Scaling make everything so hard?”

Read More »