Six months into her role, a COO I once advised told me she had finally built a psychologically safe team. Nobody interrupted her in meetings anymore. Nobody pushed back on the roadmap. Decisions moved fast because no one argued.
Four months later, the product she had championed collapsed in the market within a single quarter. When she asked her team why nobody flagged the obvious flaw before launch, three people gave her the same answer. We saw it. We just didn’t think it was our place to say so.
That wasn’t psychological safety. It was a well managed silence, and she had mistaken it for trust.
Most executives use the two words interchangeably. They are not the same thing, and the confusion is expensive. It shows up as launches nobody challenged, hires nobody questioned, and strategies that quietly failed in the room before they failed in the market.
Is Psychological Safety the Same as Trust?
No. Trust is a belief one person holds about another person’s reliability, and it grows through consistent, predictable behavior over time. Psychological safety is a belief the whole group holds about what happens if someone takes a risk in front of it, like admitting a mistake or challenging the boss. A team can have high trust and zero psychological safety at the same time.
Amy Edmondson, the Harvard researcher who named psychological safety in 1999, built her original studies around hospital teams. The safer units did not report fewer errors. They reported more of them, because nurses felt able to say so out loud, and their managers didn’t punish the disclosure.
That distinction matters more than it sounds. Trust answers one question: will this person do what they said they would do. Psychological safety answers a harder one: what happens to me if I say the risky thing in this room, in front of these people, right now.
You can trust your CFO completely and still watch her stay quiet in a room where disagreement has, in the past, cost someone their next promotion. The two things run on separate tracks, and a leader who only monitors one of them is flying half blind.
Why a Quiet Team Feels Safe but Isn’t
I worked with a founder years ago who ran his leadership meetings like a well oiled machine. Everyone nodded. Everyone agreed on the plan by the end of the hour. He called it alignment.
What he had actually built was a room where the cost of disagreement had quietly become higher than the cost of staying wrong. Nobody decided this on purpose. It accumulated, meeting by meeting, every time a dissenting voice got talked over or filed under “not now.”
Gallup’s engagement research has found, for several years running, that roughly three in ten employees strongly agree their opinions count at work. That number should stop any executive mid-sentence. It means most people in your meetings have already concluded that speaking honestly isn’t worth the risk, and they’ve adjusted their behavior in response.
Google’s own internal research into team performance, the study widely known as Project Aristotle, reached a similar conclusion after examining hundreds of its teams. The single strongest predictor of a high-performing team wasn’t who was on it. It was whether members believed they could take a risk without being humiliated for it.
A quiet team can look like a high-trust team from the front of the room. From where the team sits, it often looks like compliance dressed up as maturity. The leader sees harmony. Everyone else sees a room where the smart move is to keep your head down and let the plan fail on its own schedule.
What a High-Trust, Low-Safety Team Actually Costs You
This isn’t an abstract culture problem. It shows up on the balance sheet.
The COO’s failed launch cost her company a full quarter of engineering time and a chunk of her credibility with the board. Neither of those losses appeared on a culture survey beforehand. Both were entirely predictable to at least three people in the building.
Every senior leader I’ve advised who suffered a preventable failure has, in hindsight, found someone who saw it coming. The information was almost never missing. It was sitting in someone’s head, unspoken, because speaking it had a cost the person wasn’t willing to absorb.
That is the real price of confusing trust for safety. You don’t lose the information. You lose access to it exactly when you need it most, and you find out only after the decision has already shipped.
The Remote Leadership Trap: When Distance Rewards Silence
Distributed teams make this harder to spot, not easier. On a video call, silence reads as agreement because there is no hallway conversation afterward to correct the record.
I advised a leadership team spread across four time zones that had, without meaning to, built an entire operating rhythm around status updates instead of real conversation. Everyone reported in. Almost nobody flagged risk. The founder assumed this meant the team trusted the plan.
What had actually happened was simpler and more troubling. Remote work had stripped out the informal moments where concerns used to surface, the corridor comment, the after-meeting aside, the quiet word before the elevator door closed. Without those channels, the only way to raise a problem was to interrupt a scheduled call in front of everyone, and almost nobody wanted to be the one who did that first.
So leaders respond the way leaders often respond to uncertainty. They add oversight: more check-ins, tighter trackers, dashboards that make activity visible even when trust in judgment is missing. That instinct is understandable, but it solves the wrong problem.
Surveillance can produce a version of reliability. It cannot produce the thing psychological safety actually requires, which is a team that believes speaking up will be rewarded rather than quietly punished. Watching people work harder is not the same as making it safe for them to tell you the truth, and distributed teams feel that gap first.
Why This Gap Is Widening Right Now
Two forces are making the trust and safety gap harder to see, not easier, and most leaders haven’t adjusted for either one.
The first is AI. As teams hand more first-draft thinking to tools instead of to each other, the informal back and forth that used to surface doubt quietly disappears. A recent Harvard Business Review piece on the subject noted that AI adoption is reshaping team dynamics in ways leaders haven’t fully mapped yet, and psychological safety is one of the first casualties, because people stop testing ideas out loud when a tool can generate a plausible answer alone.
The second is scale. As spans of control widen and middle managers absorb more direct reports without added support, the one-on-one moments where dissent used to get an outlet simply shrink. A manager with four direct reports can catch a hesitant voice. A manager with fourteen usually can’t, even with the best intentions.
Neither of these forces announces itself as a trust problem. Both show up first as a quiet team, which is exactly why so many leaders misread the signal and call it safety.
How Do You Know If Your Team Has Safety or Just Compliance?
Here’s a diagnostic I use with clients, and it takes less than a minute to run. Think of the last time someone on your team disagreed with you in front of others. Then answer honestly: what happened next.
If the honest answer is nothing changed, you were heard, and the person who disagreed is still comfortable doing it again, you likely have psychological safety. If the honest answer is the meeting moved on, the topic never came back up, or that person has been noticeably quieter since, you have trust at best. You do not have safety.
I call this the disagreement audit, and it works because it removes the self-report bias that ruins most culture surveys. Employees will rate their team as safe on an anonymous form and still stay silent in the actual meeting, because the form doesn’t carry consequences and the meeting does.
Run the audit on yourself before running it on anyone else. Ask which of your last five decisions someone privately disagreed with, and whether you ever found out. If you can’t answer that question, the silence in your meetings has already told you everything you need to know.
What to Do When You’ve Built Trust, Not Safety
Start by separating the message from the messenger, out loud and in front of others. The first time someone flags a real problem in a meeting, your reaction in that exact moment becomes the new operating rule for everyone watching, whether you intended it to or not.
Reward the act of surfacing bad news specifically, not just tolerate it. A brief, genuine acknowledgment, something as simple as “glad you caught that before we shipped it,” does more than any culture statement pinned to a wall.
Revisit what your incentive structure actually rewards. If promotions have historically gone to people who executed cleanly and never made the room uncomfortable, you have built a system that selects for silence, and no amount of stated values will override it.
Model the vulnerability first. Admit a misjudgment of your own before asking anyone else to admit theirs. Teams calibrate to the most senior person in the room, and they will not go first.
None of this happens in a single offsite or a values refresh. It happens the next time someone tells you something you don’t want to hear, and you decide, in real time, whether that was worth it for them.
What Happened After the Disagreement Audit
The COO from the opening of this piece ran her own disagreement audit after the launch failed. She found five decisions in the prior year where someone had quietly disagreed and never said so out loud. Two of them, she told me later, would have changed the outcome entirely.
Ask yourself the same question about your own team this week. Not whether they trust you. Whether they believe it’s safe to tell you when you’re wrong.
If this connects with something you’re navigating right now, my book The Thinking Trap goes further into the cognitive patterns that make smart leaders miss exactly these signals. It’s available on Gumroad: https://5402694886686.gumroad.com/l/lilbce