What Is Silence Costing Your Company?
Building psychological safety in teams is how an organization stops paying the invisible cost of silence — the problems people know but never say, which are cheap to fix early and enormous by the time they surface. Amy Edmondson shows that safety can't be decreed; it's built team by team through leader behavior, using a repeatable playbook: set the stage by framing work as complex and expecting mistakes, invite participation with genuine questions and humility, and respond productively when people speak. Rewarding intelligent failure — while still addressing genuine violations — keeps people reporting instead of hiding. Daniel Coyle adds that safety is built by overcommunicating belonging cues, small signals repeated until people believe them. The goal is high safety paired with high standards, a learning zone rather than a comfort zone. This makes the Back movement of The Hanlon Potential Model™ — See, Grow, Back — an organizational system. Start by honestly measuring how safe it feels to speak.
Silence has a price, and it never shows up on a single line of your financials. It's the broken process everyone quietly worked around. The customer complaint that died two levels below you. The bad decision a dozen people privately doubted and no one questioned aloud. You cannot budget for what you never hear — which is exactly why the cost of silence is the most dangerous number in your business: the one you'll never see.
And here's the counterintuitive part. The most expensive cultures aren't the loud, chaotic ones where people argue. They're the quiet, agreeable ones where everyone nods, no one pushes back, and problems slip underground until they surface as disasters. Yesterday we made the case for psychological safety as a leadership skill. Today the question is organizational: what is silence actually costing you, and how do you build a company where the truth travels?
Key Takeaways
• The cost of silence never appears on a P&L — which is what makes it so dangerous.
• Psychological safety can't be decreed; Edmondson shows it's built team by team, through leader behavior.
• Her practical playbook: set the stage, invite participation, and respond productively.
• Rewarding intelligent failure — not punishing it — is how organizations keep learning.
• The goal is high safety paired with high standards, not comfort in place of accountability.
• This is how the Back movement of The Hanlon Potential Model™ becomes an organizational system.
Silence Is a Line Item You Can't See
Amy Edmondson's The Fearless Organization is, at its core, a catalog of what silence costs when it's allowed to become culture. Volkswagen and Wells Fargo built environments where succeeding at all costs mattered more than speaking honestly — and employees broke the law rather than raise a hand. Nokia's engineers watched the smartphone era arrive and said nothing inside a culture too proud to listen. In each case the bill came due later, enormous and public, for a silence that had felt free at the time.
Your organization is unlikely to make headlines, but the mechanism is identical at any size. Every problem that goes unmentioned is a cost deferred and usually multiplied — cheap to fix when someone first notices it, expensive by the time it forces its way into view. The quiet team that never surfaces bad news isn't low-maintenance. It's accumulating a liability you can't see on any report until it's too large to ignore.
You Can't Order People to Feel Safe
The instinct, once a leader is convinced safety matters, is to announce it — a new value on the wall, a line in the all-hands, an open-door reminder. Edmondson is clear that this doesn't work. Psychological safety isn't installed by decree; it's built at the level of individual teams, through the accumulated behavior of the person in charge. It's a leadership practice, not an HR program, and it can't be delegated to a poster.
That's actually good news, because it means the lever is in your hands, not in a budget line. It also means safety can vary wildly across one organization — thriving under one manager, absent under another two doors down — regardless of the company-wide policy. If you want to know how safe your culture really is, don't read the values statement. Watch what happens on each team when someone delivers news the boss doesn't want to hear.
Edmondson's Playbook: Set the Stage, Invite, Respond
Edmondson offers a practical, repeatable sequence. “First, set the stage: frame the work honestly as complex and uncertain, and tell people plainly that you expect problems and mistakes because that's the nature of hard work. When people know that errors are anticipated rather than punished, the cost of admitting one drops.
Second, invite participation — actively and specifically. Don't wait for people to come to you; ask what you're missing, demonstrate the humility of a leader who genuinely needs their input, and ask real questions rather than rhetorical ones. Third, and most important, respond productively when they do speak. Thank people for the courage, take the input seriously, and act on it — or explain honestly why you won't. This is the make-or-break moment: a single dismissive reaction teaches the whole team more about safety than any speech, and it teaches the wrong lesson.”
Reward the Failure That Teaches
Nothing signals safety — or destroys it — faster than how an organization treats failure. Edmondson draws a crucial line between “blameworthy failure (carelessness, violation of clear standards) and the far more common intelligent failure: a thoughtful attempt at something uncertain that didn't work. Punishing the second kind doesn't reduce failure. It reduces reporting — people simply hide their mistakes, and the organization stops learning.”
The strongest cultures do the opposite: they reward intelligent failure openly. Google's experimental unit publicly celebrates teams that shut down projects that weren't working, because that honesty focuses resources on what will. Practically, that looks like blameless after-action reviews — discussing what happened, what was learned, and what changes next time, without hunting for someone to punish. When people see that an honest failure is met with learning instead of blame, they stop hiding, and the whole system gets smarter. This isn't permissiveness; Edmondson is equally clear that “genuine violations of clear values still require a response.”
Overcommunicate Belonging
Daniel Coyle's research in The Culture Code adds the texture underneath the playbook. Safe cultures are saturated with what he calls belonging cues — small, repeated signals that say “you matter here, you're safe here.” They're not grand gestures; they're the leader who listens fully, thanks people generously, remembers to include the quiet voice, and admits their own uncertainty out loud.
Coyle's practical instruction to leaders is to “overcommunicate — to say the safety-building things far more often than feels necessary, because a single message doesn't register the way a steady drumbeat does. One vulnerable admission from a leader is a moment; a consistent pattern of them becomes a culture. Building safety at scale isn't about a landmark initiative. It's about the relentless repetition of small signals until people actually believe them.”
The Real Test: High Safety and High Standards
A caution, because “safety” is easily misread as “lower the bar.” Edmondson is emphatic that psychological safety and high standards are not opposites — they're two axes. Low safety with high standards produces anxiety, where people are driven but afraid, and the truth stays buried. High safety with low standards produces a comfortable place where not much gets done. It's the combination — high safety and high standards together — that creates a learning environment, where people feel free to speak and are held to excellent work.
That pairing is the goal to hold in front of you as a leader. You are not choosing between a demanding culture and a safe one; the best organizations are unmistakably both. Candor and excellence reinforce each other, because people who feel safe enough to tell the truth are the same people who can be pushed to do their finest work without fear making them hide.
The Hanlon Potential Model™: Systematizing the Back Movement
This is where The Hanlon Potential Model™ — See, Grow, Back — becomes structural. Backing your people isn't a sentiment; at organizational scale it's a set of deliberate practices that make it safe, across every team, to speak, question, and fail while learning. That's what protects the value of everything you built in the earlier movements.
Start by measuring what you can't currently see. This week, take a real read on safety — ask your team, honestly and specifically, how safe it actually feels to disagree with you, to admit a mistake, or to raise a concern. Edmondson suggests a simple survey; even a candid one-on-one question works if people trust the asker. Whatever the answer, resist the urge to defend, and respond productively. That single act — asking, and then honoring what you hear — is the first entry in the system that makes the rest of the model pay off.
Final Thoughts
The most expensive thing in your organization is the truth that never reaches you — and unlike most costs, this one is entirely within your control to change. It won't be fixed by a values statement or an open-door slogan. It's built team by team, in how you frame the work, how you invite the truth, and above all how you respond when someone is brave enough to tell it.
Tomorrow we bring this into the practice, where silence can cost far more than money — where an assistant who doesn't feel safe to speak up might be the difference between a caught mistake and a harmed patient. Backing your people, it turns out, is where leadership stops being about you and starts being about what you make possible for them.
Frequently Asked Questions
-
It's more measurable than it sounds. Edmondson recommends surveying teams with a simple scale on statements like “it's safe to take a risk on this team” or “mistakes are held against you here.” Even without a formal survey, patterns tell you a lot: who speaks in meetings, whether bad news reaches you early or late, how often people admit mistakes unprompted.
-
Only if you drop your standards at the same time, which isn't the goal. The target is high safety and high standards together — a learning zone, not a comfort zone. Safety is what lets you hold a high bar without driving the truth into hiding.
-
That's the most valuable answer you can get, and how you receive it is the entire test. Thank them, resist every urge to defend, and change something visible. The willingness to hear that particular truth without punishing it is itself the first proof that things are changing.
-
No — the distinction is intelligent failure versus blameworthy failure. You reward the thoughtful attempt that didn't pan out, and you still address carelessness and violations of clear standards. Rewarding intelligent failure is precisely what keeps people honest about mistakes instead of hiding them.