Why Silence can Signal Resistance in Organisations

Introduction: When Quiet Means Crisis

In a previous role, I once watched a CEO navigate an acquisition that should have been straightforward – well, as straightforward as acquisitions can ever be! The target business was solid – good team, proven model, clear synergies with the parent company. The deal closed smoothly. Contracts were signed. Integration plans were approved.

And then the leader of the newly acquired business went quiet.

Not visibly resistant. Not making demands or pushing back. Just… less present. Fewer emails. Shorter responses. Less visible in meetings (if/when he turned up).

The acquiring CEO assumed it was natural. “He’s busy. The business is performing really well. He’s probably just adjusting.”

But that silence wasn’t adjustment. It was resistance.

By the time anyone realised what was happening, the leader had mentally checked out. One team member handed in their notice. Then another. Before long, the remaining staff had collectively decided that this acquisition was something to endure, not embrace. Trenches had been dug.

The business the CEO thought he’d bought – its culture, its energy, its leadership – was gone. What remained was a shell that looked fine on paper, and would keep ticking along in the short term, but it had lost the spirit that made it valuable in the first place.

This story isn’t unique. I’ve seen versions of it play out across mergers, restructures, leadership changes, and strategic pivots. And the pattern is always the same:

Silence gets misread as compliance. By the time you realise it’s resistance, the damage is done.

The Misreading of Silence

In business, we’re conditioned to focus on the visible: conflict, pushback, vocal disagreement. These are obvious problems that demand attention.

But silence? Silence feels like relief.

After a difficult deal negotiation, a contentious restructure, or an exhausting change programme, leaders often interpret quiet as a sign that things are settling down. People have accepted the new reality. The storm has passed. It often suits us to interpet it this way.

But silence is rarely neutral. In my experience, it’s almost always a signal – just not the one we want to believe.

What Silence Usually Means

Disengagement
People have stopped investing emotional energy in the outcome. They’re going through the motions, but they’ve mentally checked out.

Loss of trust
They don’t believe their input matters, so they’ve stopped offering it. Or they don’t trust that speaking up will be received well.

Strategic withdrawal
They’re quietly looking for other options – new roles, new opportunities, ways to protect themselves from uncertainty.

Passive resistance
They’re not openly opposing the change, but they’re not supporting it either. They’re waiting to see what happens before committing.

Exhaustion
Sometimes silence is simply burnout. They’re too tired to engage, too overwhelmed to process what’s being asked of them.

None of these are good. And all of them are easier to address early than late.

The Acquisition That Went Quiet: A Cautionary Tale

Let me return to that acquisition story, because the details matter.

The Setup

The acquiring CEO — let’s call him Jim — had done everything by the book. He’d run a thorough due diligence process. He’d negotiated fair terms. He’d developed a detailed integration plan with clear milestones.

The leader of the acquired business — let’s call him Pete — had been enthusiastic during negotiations. He’d talked about the opportunities for growth, the resources the parent company could provide, the strategic fit. He’d signed the deal without hesitation.

The First 90 Days

After the deal closed, Jim expected Pete to stay engaged. Weekly check-ins were scheduled. Integration meetings were set up. Everything was proceeding according to plan.

But Pete started to fade.

He attended meetings, but contributed less. He responded to emails, but tersely. One missed meeting a month became two. When asked how things were going, his answers were vague: “Fine.” “All good.” “Just busy getting things sorted.”

Jim didn’t push. The numbers were holding up – better than expected, actually. Pete’s team seemed to be delivering. Jim assumed Pete just needed space to adjust to the new structure.

The Unravelling

Five months in, Jim got a call from his HR director. Pete’s finance manager had resigned. No warning. No explanation beyond “pursuing other opportunities.”

Two weeks later, one of Pete’s operations team handed in notice. Then another.

By the time Jim sat down with Pete for a proper conversation, it was too late. Pete was polite but distant. He’d already started looking for his next role. He didn’t trust that the acquisition would work out. He felt like he’d lost control of his business. And he’d convinced his team – subtly, through his own disengagement – that the future was uncertain.

Within twelve months of closing the deal, Pete was gone. Half his senior team had followed. The business Jim thought he’d bought no longer existed.

What Went Wrong

Looking back, the problem was obvious: Jim mistook silence for consent.

Pete’s quiet wasn’t adjustment. It was withdrawal. And the signs were there from the beginning:

Shorter, less detailed responses
Declining energy in meetings
Subtle deflection when asked how he felt about changes
Reduced visibility with his own team

But Jim was busy. The integration plan was moving forward and there were more acquisitions to focus on. The P&L looked fine. So he didn’t lean in. He didn’t create space for difficult conversations. He didn’t check whether Pete’s silence was contentment or concern.

By the time he realised what was happening, the relationship – and the acquisition – was beyond saving.

The Hindsight Question: Could It Have Been Saved?

I’ve thought about this case a lot. And I believe there was a window – probably in those first 60 days – where Jim could have turned it around.

Not through better integration plans or clearer KPIs. Through relationship.

What Could Have Been Different?

More presence, not more process
Jim needed to show up more often, not send more emails. Coffees, not Computers. Asking “how are you feeling about all this?” not “are you on track with the integration milestones?”

Permission to be uncertain
Pete needed to hear that it was okay to feel ambivalent, to struggle with the change, to have concerns. Instead, the tone was relentlessly positive: “This is great for everyone!” When reality doesn’t match the narrative, people go quiet.

Visible investment
Jim needed to demonstrate – through his time and attention – that Pete and his team mattered. Not just the business metrics, but the people. That signal never came.

Earlier confrontation
When the silence started, Jim should have called it out: “You’ve gone a bit quiet. What’s going on?” Sometimes naming the thing is enough to open a door.

None of these are complicated. But they require leaders to treat silence as a warning sign, not a comfort.

Silence in Other Contexts: Beyond Acquisitions

This pattern isn’t limited to M&A. I’ve seen it play out in:

Post-restructure environments
Teams that have been reorganised often go quiet. The loudest voices may have left. The remaining people are watching, waiting to see if the new structure will work. If leaders interpret that waiting as acceptance, they miss the chance to rebuild trust.

After difficult feedback
When you give someone hard feedback – especially if it’s about performance or behaviour – they often go quiet. Not because they’ve accepted it, but because they’re processing, defending internally, or withdrawing. Follow-up matters.

During strategic pivots
When a company changes direction – new market, new product focus, new priorities – some people will vocally resist. But many will just… stop contributing ideas. That silence is a form of protest: “If you’re not listening to us anyway, why bother speaking?”

In diverse or hierarchical cultures
In some organisational cultures, silence is the default when people disagree or feel uncertain. If you’re leading cross-culturally or in environments where speaking up feels risky, you need to actively create permission to voice concern.

How to Interpret Silence: A Framework

Not all silence is bad. Sometimes people are quiet because they’re thinking, or because they genuinely don’t have concerns. And sometimes there may be a cultural dimension – some cultures are more prone to speaking in group/business settings than others. But you can’t assume that. Here’s how I assess what silence means:

1. What’s the Context?

Has something changed recently? A restructure, a new leader, a strategic pivot, a difficult quarter? If so, silence is more likely to signal discomfort than contentment.

Ask yourself: If I were in their position, would I feel safe speaking up right now?

2. What’s the Pattern?

Has this person always been quiet, or is this new? A naturally introverted team member might not speak up in large meetings but could be fully engaged. But if someone who was previously vocal has gone quiet, that’s a red flag.

Ask yourself: Has their behaviour changed? If so, when?

3. What Do Others Say?

If one person is quiet, it might be individual. If a whole team or function goes quiet, it’s systemic. Talk to people adjacent to the quiet team. What are they hearing in informal conversations?

Ask yourself: Is this an individual issue or a cultural/team issue?

4. What’s Not Being Said?

Sometimes silence reveals itself in what’s absent: no questions in meetings, no ideas volunteered, no informal check-ins, no social interaction.

Ask yourself: What used to happen that isn’t happening anymore?

What to Do When You Encounter Silence

Once you’ve recognised that silence is a signal, you need to respond. Here’s what works:

1. Lean In, Not Away

Your instinct might be to give people space. Sometimes that’s right. But often, space just allows distance to grow.

Instead, increase your presence. Show up more. Ask more questions. Create more opportunities for informal conversation.

Example: When I inherited a team that had gone quiet after a failed project, I instituted “walk and talk” 1-1s. Just 15 minutes, outdoors, no formal agenda. The change of setting unlocked conversations that wouldn’t have happened in a meeting room.

2. Name the Silence

Sometimes the most powerful thing you can do is acknowledge what’s happening.

“I’ve noticed you’ve been quieter than usual. Is everything okay?”
“The team feels different lately. What’s going on?”
“We haven’t had much debate in meetings recently. Is that because people agree, or because people have stopped engaging?”

Naming it gives permission to talk about it.

3. Create Psychological Safety

If people are quiet because they don’t feel safe speaking up, you need to actively rebuild that safety.

Tactics:

Ask for input before sharing your view
Reward dissenting opinions publicly
Thank people for raising concerns, even if you disagree
Acknowledge when you’ve made mistakes or changed your mind

Example: At one business, I started every leadership meeting with “what’s the elephant in the room?” It felt awkward at first, but within a few weeks, people started actually naming things. The silence broke.

4. Check Your Assumptions

The acquiring CEO in the story assumed Pete’s silence meant “everything’s fine.” Challenge your own assumptions.

Ask yourself:

Am I interpreting silence in the most generous way because it’s convenient?
What evidence do I have that people are actually okay?
If I’m wrong about this, what would I be missing?

5. Follow Up

One conversation won’t fix it. If someone has been quiet for months, they won’t suddenly open up after one check-in. You need to demonstrate consistency.

Example: I once worked with a leader who had completely withdrawn after a restructure. It took three months of regular, low-stakes conversations before he felt safe enough to share what was really going on. But that investment saved the relationship – and his contribution to the business.

The Broader Leadership Lesson: What’s Not Said Matters More

This isn’t just about acquisitions or change management. It’s about how you lead generally.

The best leaders I’ve worked with assume silence is a problem until proven otherwise. They don’t wait for people to raise their hand. They actively seek out what’s not being said.

Because in most organisations, the really important things – the doubts, the frustrations, the fears, the disagreements – don’t get voiced in meetings. They get whispered in corridors, hinted at in body language, or buried under polite agreement.

If you only listen to what’s being said explicitly, you’re missing most of the story.

Conclusion: Treat Silence as a Signal

The acquisition story I started with ended badly. But it didn’t have to.

If Jim had treated Pete’s silence as a warning sign rather than a comfort, there was probably a window — a few months, maybe less — where he could have rebuilt trust, addressed concerns, and saved the relationship.

Instead, he assumed silence meant success. By the time he realised it meant resistance, it was too late.

I’ve made this mistake myself. We all have. It’s human to prefer the interpretation that requires less work, less confrontation, less emotional investment.

But leadership isn’t about taking the easy interpretation. It’s about taking the true one.

So the next time someone goes quiet – a key team member, a new acquisition, a high performer who used to contribute – don’t assume they’re fine.

Lean in. Ask questions. Create space. Show up.

Because silence, in business, is almost never neutral.

And what’s not being said is often the most important thing of all.

Key Takeaways

Silence is rarely neutral — it usually signals disengagement, loss of trust, or passive resistance
Context matters — silence after significant change is almost always a red flag
Lean in, don’t give space — increase presence and create opportunities for conversation
Name the silence — acknowledging it gives permission to talk about it
Assume silence is a problem until proven otherwise — don’t wait for people to raise concerns