Psychological safety has become one of the most talked-about concepts in engineering leadership. It's often described as a key ingredient for high-performing teams, and that's true.
But it's also widely misunderstood.
In many teams, psychological safety is interpreted as being nice, avoiding conflict or making sure no one feels uncomfortable. That version sounds appealing, but it doesn't lead to better outcomes. In some cases, it does the opposite.
Psychological safety isn't about removing tension. It's about making it safe to deal with the right kind of tension.
It's not comfort
The most common misunderstanding is equating psychological safety with comfort.
A team can feel comfortable and still underperform. People avoid difficult conversations, hesitate to challenge decisions or stay silent when they disagree. There's no visible conflict, but there's also no real progress. That quiet harmony often masks problems that are growing underneath.
Psychological safety isn't about making work feel easy. It's about making it safe to speak up when something is unclear, risky or wrong. That often involves discomfort. It means questioning a technical approach in a design review, pushing back on a timeline that doesn't account for real constraints, or telling a senior engineer their solution has a flaw.
A team that never feels tension is usually not addressing the hard parts of the work.
It's not the absence of conflict
Another common mistake is trying to eliminate conflict in the name of safety.
High-performing teams have more disagreement, not less. They challenge assumptions, question approaches and explore alternatives. That's how better decisions get made. Amy Edmondson's research on psychological safety supports this: the teams that perform best tend to be ones where people feel safe enough to disagree openly, not the ones where disagreement is absent.
The difference is how conflict is handled. In teams with low psychological safety, disagreement becomes personal or is avoided entirely. In teams with high psychological safety, disagreement stays focused on the work. You can challenge an idea without it being taken as an attack on the person.
Avoiding conflict doesn't create safety. It creates silence. And silence hides the problems that eventually surface as incidents, missed deadlines or attrition.
It's not low standards
There's a real risk that psychological safety gets interpreted as lowering expectations.
You might avoid giving direct feedback because you don't want to make someone uncomfortable. Performance issues go unaddressed. Standards become inconsistent. The rest of your team notices, and their trust in the system starts to erode.
This isn't safety. It's ambiguity.
Psychological safety works together with high standards, not instead of them. People should know what's expected, what good looks like and where they need to improve. The difference is how feedback is delivered: direct, specific and focused on behavior and impact, not on the person. "Your pull requests have had recurring issues with error handling this sprint, let's look at what's causing that" is both safe and high-standard.
This is exactly the balance described in Low Performance: How to Handle It with Clarity and Support, where support and accountability need to coexist.
It's not consensus
Another misconception is that a safe team always agrees.
That's neither realistic nor desirable. Your team needs to make decisions, and not everyone will agree with every decision. Psychological safety doesn't mean everyone gets their way. It means everyone has the opportunity to contribute before a decision is made.
Once a decision is taken, the team moves forward. Without that, you get stuck in endless discussions or default to the loudest voice in the room. Safety is about the quality of input, not about requiring universal agreement on output.
What it actually is
Psychological safety is the belief that you can speak up without negative consequences.
You can ask questions when something is unclear. You can admit mistakes without fear of blame. You can challenge ideas, even when they come from more senior people. You can raise risks early instead of hiding them.
It doesn't remove accountability. It enables it. When people feel safe to surface problems early, your team can respond before those problems grow. When people feel safe to admit mistakes, learning happens faster. When people feel safe to disagree, decision quality improves. For a deeper look at how to build this in practice, see Culture, Psychological Safety and Team Health.
How you shape it
Psychological safety isn't created through a single workshop or statement. It's built through consistent behavior over time, and your reactions as a leader set the tone.
If someone raises a concern and is dismissed, others will stay silent next time. If someone admits a mistake and is blamed, people will hide issues in the future. If someone challenges a decision and gets labeled as "difficult," disagreement goes underground.
The opposite is also true. When you respond with curiosity, acknowledge input and treat mistakes as information rather than failure, your team adapts to that. Small moments matter more than big declarations. A single reaction in a tense situation teaches your team more about what's actually safe than any values statement on a wiki.
The balance that matters
The real challenge is holding psychological safety and accountability together.
Too little safety leads to silence. People avoid risk, hide problems and defer decisions. Too little accountability leads to drift. Expectations are unclear and performance suffers.
High-performing teams have both. People speak up early and are expected to follow through. They challenge ideas and commit to decisions. They admit mistakes and take responsibility for fixing them. This is the same balance that runs through ownership without micromanagement: clear expectations with real room to be honest.
Final thought
Psychological safety is often described as making it safe to fail. A more useful framing is making it safe to be honest.
Honest about uncertainty. Honest about mistakes. Honest about disagreement. Honest about what isn't working.
That honesty is what allows teams to improve. It's not always comfortable and it's not always easy. But it's what makes the difference between a team that looks calm on the surface and one that's actually getting better.