Brief #001 — The Psychological Safety Myth: What Leaders Get Wrong About Trust

Psychological safety has become the most misused phrase in leadership.

Every consultant sells it. Every HR deck mentions it. Every team-building workshop claims to build it. And yet the data shows that only 43% of employees say their team actually has it. That gap — between how much leaders talk about it and how little actually exists — is exactly what I want to talk about today.

Because I've seen what happens when psychological safety breaks down. Not in a conference room. In rooms where the consequences weren't a bad quarter or a missed deadline.

The Weight of Responsibility

I led people in the Army for 14 years. Three combat deployments — Kosovo, Iraq, Afghanistan. At one point I was responsible for 33 people. Not managing them. Responsible for them. There's a difference. Managing is a function. Responsibility is weight. When you're responsible for 33 people in an environment where the decisions you make — or fail to make — can get someone killed, you learn very quickly what trust actually means. And it has nothing to do with making people feel comfortable.

Psychological safety as it's currently being sold in the corporate world has been stripped of its actual meaning. The original framework, developed by Harvard researcher Amy Edmondson, defines it as the shared belief that a team is safe to take interpersonal risks — to speak up, admit mistakes, challenge assumptions, without fear of punishment or humiliation. That's a precise, useful definition.

What it has become in practice is something else entirely. It has become shorthand for "be nice." For "don't have hard conversations." For "make sure nobody feels bad." And that version — the sanitized, feelings-first version — doesn't build trust. It destroys performance while pretending to support people.

What Trust Actually Requires

Here's what I learned leading soldiers: psychological safety is not the absence of pressure. It is the presence of clarity.

When people know exactly what is expected of them, when they understand the mission, when they trust that their leader will tell them the truth even when the truth is hard — they perform. They take risks. They surface problems early because they know surfacing problems is what gets rewarded, not what gets punished.

When people don't know what's expected of them, when the rules shift based on who's in the room or how the leader is feeling that day, when honesty gets punished and compliance gets rewarded — they go quiet. They stop raising their hands. They start managing up instead of solving problems. And the whole system starts running on false information.

That's not a culture problem. That's a leadership problem. The leader created those conditions.

What the Research Actually Says

PwC found that 61% of employees say a perceived lack of trust from leadership directly impacts their ability to do their jobs. Not their desire to do their jobs. Their ability. Trust isn't a soft outcome. It's an operational input.

And yet most leaders address trust the wrong way. They do team-building retreats. They mandate vulnerability workshops. They ask people to share their feelings in a circle and call it culture-building.

Those things don't build trust on their own. Trust is built through consistency. Through demonstrated accountability. Through leaders who say what they mean, mean what they say, and hold the standard even when it's uncomfortable.

You cannot ask your team to take interpersonal risks if you as the leader are not willing to take them first. You cannot ask people to admit mistakes in an environment where you've never admitted one. You cannot build psychological safety by announcing that psychological safety is important. You build it by modeling it — every day, in every decision, in every conversation.

The Real Starting Point

This is the core argument of SEIZED. Leaders break systems under pressure not because they're bad people but because their internal state — their regulatory capacity, their clarity, their honesty with themselves — degrades under load. And when the leader degrades, the system degrades with them.

The team reads the leader's state before they read any memo or mission brief. If the leader is reactive, the team becomes defensive. If the leader is unclear, the team becomes paralyzed. If the leader is dishonest with themselves, the team stops being honest with the leader.

Psychological safety starts inside the leader. Not in the team offsite. Not in the HR policy. Inside the person who holds the responsibility.

One Thing This Week

Think about the last time someone on your team told you something you didn't want to hear. How did you respond? Not what you said — how did you respond? Did your body language close? Did you get defensive? Did you punish them subtly by pulling back support or freezing them out of a decision?

If any of those things happened, you just answered your own question about why people on your team aren't speaking up.

Psychological safety isn't a program. It's a daily practice. And it starts with you being the kind of leader whose team knows — not believes, knows — that the truth is always welcome.

You don't eliminate chaos. You learn to lead through it.

That's the brief.