The silence that costs you

I want you to imagine yourself sitting in a project meeting. A junior engineer notices something that looks a little off in the plan. There's a quiet voice in her head saying, "Oh, it's probably nothing. And if I'm wrong, I'll look stupid in front of everybody." So, she says nothing. Three weeks and a six-figure rework later, it turns out she was right the first time. 

As it turns out, what the junior engineer's silence has a name. It's the absence of psychological safety, and it's quietly draining teams of their best thinking every single day. The good news? We can name it, measure it, and build it. Let's start with what it actually is.

A clear definition

Psychological safety is a concept developed by Dr. Amy Edmondson, a Harvard Business School professor who has studied it since the 1990s. Her definition is deceptively simple. Psychological safety is "a shared belief held by members of a team that the team is safe for interpersonal risk-taking."

Let's unpack that and the two words that carry the most weight. Shared means that it is the property of the team, not a feeling one confident person happens to have. And interpersonal risk is the small, everyday risk of being seen as ignorant, incompetent, intrusive, or negative. Every time you ask a question, you admit that you don't know the answer, offer a raw idea, or disagree with someone more senior than you. These are all one of those risks. On a psychologically safe team, you take these risks freely because you trust that you won't be punished or humiliated for it. 

What it is NOT

This is what most leaders get wrong, and why the idea of psychological safety gets a bad reputation. Psychological safety is not about being nice. We don't lower our standards, avoid conflict, have endless consensus, or protect people from tough feedback. In fact, it's the opposite. A "safe" team where no one is ever challenged isn't safe; they're simply comfortable, and comfortable teams coast.

Edmondson maps this on two axes: psychological safety and motivation/standards. Low safety plus high standards produces anxiety. High safety plus low standards produces a comfort zone. Low on both is apathy. The goal is the fourth quadrant, where high safety and high standards, together, is what she calls the learning zone. That's the paradox worth sitting with: Safety is what makes it possible to hold a high bar, because people can admit mistakes, ask for help, and challenge each other honestly enough to actually meet it. 

The evidence: why this isn't soft

If this still sounds like a "nice-to-have," I want you to consider Google. In its Project Aristotle study, Google set out to find what made some of its teams dramatically more effective than others. They expected that it would come down to the mix of talent (i.e., whether they had the smartest people, the right people, the right combination of educational and professional experience, etc.). As it turns out, it didn't. The single most important factor derived from the best teams across every dynamic measurement was that more effective teams had higher levels of psychological safety. How team members felt about one another mattered more than who was on the team. 

The mechanism is intuitive once you see it. Teams that feel safe report more errors, not because they make more mistakes, but because they surface more. They also end up asking more questions, sharing more information— openly—experimenting and innovating more, and catching problems faster. In fast-moving or high-stakes work, like healthcare, aviation, software, anything involving real high-risk situations, the willingness to say, "I'm not sure about that" or "Hey, I think this is wrong," is the difference between a near-miss, saving a life, or avoiding the next news cycle. 

So how do we build it?

Here's what we know: psychological safety isn't created with a poster on a wall or a recommitment to the organization's value statements. It's built in micro-moments in how a leader reacts the instant someone brings bad news, asks an obvious question, or disagrees in front of the group. Here are a few practical starting points:

• Frame the work as a learning problem, not an execution problem. Say out loud that the work is complex, you don't have all the answers, and everyone's eyes are needed to solve the problem. 
• Model fallibility. When a leader shares with the team, "I might be missing something" or "What am I not seeing," it gives everyone else permission to be human (and honest), too. 
• Respond to bad news with curiosity, not blame. Your reaction to the first mistake sets the price of honesty for the next year. Don't miss it.
• Ask genuine questions and reward the messenger. You should thank people for expressing their concerns, especially when it would have been easier to stay silent. 

The bottom line

Psychological safety is not the opposite of high performance in a team or an organization. It's actually the precondition for a high-performing team or organization. We're not talking about making the work comfortable; it's all about making candor safe, so your team's best thinking makes it into the room. The teams that win aren't the ones who argue less; they are the ones who argue well, because everyone trusts it's safe to do so. 

This week, we're unpacking psychological safety from every angle. If your team has ever gone quiet when it mattered the most, follow along, and I'll share a free worksheet to measure where your team stands right now.