When people stop speaking up, silence can look like alignment.

Why the way leaders respond to disagreement can determine what their teams are willing to say next.

Inspired by Leaders Eat Last by Simon Sinek

When silence looks like agreement

The meeting is almost over. A leader has just presented an important decision. The rationale seems clear, the direction is explained, and the team has been invited to share its thoughts.

“Any concerns before we move forward?”

Nobody speaks. A few people nod. Someone says it sounds good. The leader closes the meeting feeling confident that everyone is aligned.

But later, different conversations begin. One colleague questions the timeline. Another sees a risk nobody discussed. Someone else admits they had doubts but didn't think challenging the decision would change anything. What looked like agreement in the meeting turns out to be something more complicated.

The absence of disagreement isn't always evidence of alignment. Sometimes, it's simply the absence of voices willing to disagree. And for leaders, distinguishing between the two can be surprisingly difficult.

What people learn when they speak up

Most leaders would say they welcome different opinions. They encourage people to be open, challenge assumptions, and speak honestly.

But here's an uncomfortable question: What happens when someone actually does?

Imagine that a team member questions a proposal during a meeting. The leader immediately explains why the concern isn't relevant. Perhaps they interrupt before the person finishes, or respond with visible impatience. The decision may still be reasonable. The leader may even be right.

Yet something else has happened. Everyone in the room has witnessed what it feels like to challenge the person in charge.

Now imagine the same situation with a different response. The leader pauses. “That's an important concern. Tell me what you're seeing.”

They listen, ask questions, and explore the implications before responding. The decision might ultimately remain unchanged. But the interaction sends a different message. Disagreement is something we can examine together, rather than something we need to defend ourselves against.

People learn what is safe to say not only from what leaders invite, but from how leaders respond.

What Leaders Eat Last teaches us about safety

In Leaders Eat Last, Simon Sinek explores the importance of creating environments where people experience trust, belonging, and mutual support. Central to his argument is the Circle of Safety: the idea that leaders have a responsibility to help people feel protected from threats within the organization, so they can direct more of their energy toward working together and responding to challenges outside it.

It's a compelling leadership principle. But safety isn't created simply by telling people they're safe. It develops through experiences. Whether people feel able to acknowledge mistakes, ask for help, question an assumption, or raise an uncomfortable concern depends partly on how those moments are handled.

And this is where Sinek's perspective connects with research on psychological safety. Amy Edmondson describes team psychological safety as a shared belief that a team is safe for interpersonal risk-taking. Her research found an association between psychological safety and learning behavior in teams.

Elizabeth Morrison's research on employee voice and silence further explores why employees sometimes withhold potentially useful ideas, concerns, or information.

These perspectives reinforce an important distinction. A team can appear cooperative while important information remains unspoken.

That doesn't mean every quiet meeting signals a problem. People may genuinely agree, need more time to think, or have nothing additional to contribute. But leaders who automatically interpret silence as endorsement may overlook valuable information.

Safety doesn't mean avoiding difficult conversations

Psychological safety is sometimes mistaken for an environment where everyone feels comfortable all the time. But that's not the point. A team where nobody challenges poor reasoning, questions unrealistic expectations, or addresses performance concerns isn't necessarily safe. It may simply be avoiding discomfort.

Real collaboration requires room for constructive tension. People need to be able to disagree respectfully, raise concerns without being humiliated, and challenge an idea without turning the discussion into a personal conflict.

Leaders play an important role in shaping that experience. Not by agreeing with every objection. Not by allowing every discussion to continue indefinitely. But by demonstrating that a different perspective deserves to be considered on its merits.

Making disagreement welcome doesn't mean surrendering the responsibility to decide. It means taking that responsibility seriously enough to seek information that might challenge your initial view.

The moment that matters most

Consider two responses to the same concern. A team member says: “I'm not convinced we can deliver this within the proposed timeline.”

The leader responds: “We've already discussed the timeline. We need to move forward.”

Now consider: “What makes you concerned about the timeline? Is there something we're underestimating?”

Both leaders may eventually make exactly the same decision. But the second creates an opportunity to uncover information the first might miss.

There's a subtle but important leadership skill here: remaining curious when your judgment is being questioned. That isn't always easy. Especially when deadlines are pressing, you've invested considerable effort in a proposal, or you're being challenged in front of others.

The natural temptation may be to explain, justify, or defend. But sometimes, the most useful leadership response is to delay that impulse long enough to understand what the other person is trying to tell you. Because the way you respond today may influence what someone chooses to share tomorrow.

A final thought

Leaders often pay close attention to what people say. Perhaps they should pay just as much attention to what happens when someone says something difficult.

Because every response carries a message. An interruption. A defensive explanation. A moment of impatience. Or a pause, an honest question, and a willingness to listen.

None of these moments determines a team's culture on its own. But repeated over time, they contribute to what people come to expect.

The real test of whether you welcome disagreement isn't what you say when you invite it. It's what you do when someone takes you up on the invitation.