When Your Team is Too Quiet
what silence actually means, and what to do about it
I reference psychological safety a lot. In my newsletter on Quality as a System, I argued that a system grounded in accountability creates psychological safety, and that psychological safety is what makes teams adaptable. In The Five Reasonable Mistakes, I described how leaders who make raising concerns expensive quietly poison the systems they’re trying to build. In The Voice, I wrote about what happens when leaders haven’t examined their own insecurity, and how that closes off the people around them.
Every time I write about quality, culture, or leadership, psychological safety shows up somewhere in the argument. So it’s probably time to write more about it directly.
The Belief
Psychological safety is the belief that you can speak up, share an idea, raise a concern, admit a mistake, or ask a question without being punished or humiliated for it.
That’s it. It’s not about being comfortable. It’s not about being nice. It’s not about avoiding difficult conversations. In fact, psychological safety is what makes difficult conversations possible, because people can have them without fear of what happens next.
Amy Edmondson, who has done more to research and define this concept than anyone, describes Psychological Safety as a belief about what will happen if you take an interpersonal risk. The key word is belief. It’s not about whether the leader intends to punish people for speaking up. It’s about whether the team believes they will.
This distinction matters enormously in practice.
Why Organizations Get This Wrong
I once worked with a leader who declared that psychological safety existed on their team, and by saying this, that it would magically exist. It obviously doesn’t work that way, and their team was actually toxic.
In fact, an extremely common mistake I see in a lot of organizations is treating psychological safety as a culture initiative. A leader decides that the team needs more of it, puts it on a slide at an all-hands, and announces that the organization values open feedback and honest communication.
And nothing changes.
What changes the belief is consistent behavior over time, not declarations. Every time a leader responds to bad news by shooting the messenger, they make a deposit into the “it’s not safe to speak up here” account. Every time a leader responds to an honest concern with curiosity instead of defensiveness, they make a deposit into the opposite account. The balance of that account, built up over months and years of repeated small interactions, is what the team actually believes.
You can’t declare your way out of a bad balance. You have to transact your way out.
On Practice
Here are the specific behaviors that I use to try and build psychological safety in organizations. None of them require a slide deck, an initiative, a budget, or a consultant.
React to bad news with curiosity. When someone brings you a problem, your first response matters enormously. If your first response is to question why it happened, assign blame, or express frustration, you’ve just taught everyone in earshot that bad news is dangerous. If your first response is “tell me more” or “what do you think is causing this?”, you’ve taught them the opposite. Do this consistently enough and people will start bringing you problems earlier, which is exactly when problems are cheapest to fix.
Normalize not knowing. Say “I don’t know” in public. Leaders who perform certainty they don’t have create organizations where admitting uncertainty feels like weakness. When you model intellectual honesty, saying things like, “this is what I know”, “this is what I don’t know”, “here’s how I’m thinking about it now”, you give everyone around you permission to do the same.
Too many leaders fall back on projecting confidence and pretending to be smarter than they are rather than admit they don’t know something.
Make it safe to disagree with you specifically. This is often the most difficult. It’s pretty easy to say you want honest feedback. It’s much harder to receive disagreement from a team member without becoming defensive, dismissive, or cold afterward. People are watching what happens to the person who pushed back. If that person gets quietly sidelined, everyone learns the lesson. If that person gets heard and respected even when you don’t change your mind, everyone learns a different lesson.
In fact, I’d say that as a leader, until you have people from any level of your organization speaking up with ideas, pushing back on decisions, or asking hard questions in group meetings, you do not yet have anything close to a psychologically safe organization.
Treat mistakes as information, not verdicts. The culture you build around failures tells your team everything about how safe it is to take risks. If every outage ends with someone being blamed, people will start optimizing to avoid blame rather than to avoid outages. If every post-mortem ends with systemic learning and no individual punishment, people will start surfacing near-misses before they become real incidents.
I once led an organization where teams would often open incident channels in Slack before a tricky deployment, just so they could track and capture any nuance and failures more easily for future learning.
The Signal
The absence of psychological safety is almost always invisible until it’s too late
When your team doesn’t feel safe, they don’t tell you. They stay quiet in meetings. They say “sounds good” when they really mean “I have serious concerns.” They stop raising issues because they’ve learned that raising issues is more trouble than it’s worth. The problems are still there, they’re just underground, where they grow until they surface as something much more expensive to fix.
In What Is Your System Teaching You, I wrote that every organization is running an educational program whether it intends to or not. The question isn’t whether your system teaches. It’s what it’s teaching.
If your team is too quiet during discussions, that’s your system teaching. The question is what lesson it’s been running.
Where to Start
If you’re reading this and wondering whether your team feels safe enough to be honest with you, the solution is definitely not to ask them if they feel psychologically safe.
Instead, look closely at behavior. Do people bring you bad news early or late? Do they disagree with you in meetings or only in hallways afterward? Do they admit mistakes or do they hide them? Do they ask questions or do they pretend to understand?
The answers to those questions tell you more about the actual state of your team’s psychological safety than any survey or direct question will.
And if you don’t like what you see, the path forward is the same one it’s always been. Not a declaration. Not an initiative. Just a long series of small moments where you consistently choose curiosity over defensiveness, honesty over performance, and the long-term health of the team over the short-term comfort of being right.
That’s how the balance changes. One transaction at a time.
If this is something you’re working through in your organization, I’d love to talk.