Silence is a signal for EQ leaders

The transformation risk that doesn’t appear on your risk log

A transformation workshop can look successful on paper. The right people attended, the slides were covered, the actions were logged, and nobody pushed back.

Then the week after it turns out it wasn’t as successful as it felt. Decisions that should take a day take two weeks. The same questions resurface in a different form. People agreed in the room, but nothing changed outside it, and many actions remain incomplete.

This is often where resistance starts to show. If you’re close to the operational teams, you usually feel it early. You end up stuck between a project team that thinks things are moving and the people doing the day job who are starting to slow down.

This article is about that subtler form of resistance: not the person who openly challenges the programme, but the people who stop contributing, stop testing properly, and start finding ways to cope outside the process.

Silence isn’t agreement

When someone challenges a decision directly, it’s uncomfortable but manageable. You can respond by understanding, explaining the rationale, addressing the concern, and moving forward. The harder version is when people stop saying what they actually think.

They don’t want to be the difficult one. They raised something similar six months ago and nothing changed, so why bother. They don’t fully understand the new process yet but they’re not going to admit that in front of their team. Or they’ve clocked that the decision has already been made at a level above them, so they nod and say nothing.

A project team can mistake silence for alignment, a sponsor can mistake attendance for engagement, and a training lead can mistake completion for confidence. Everything looks fine on the dashboard. But underneath, people are holding back, and that shows up later at go-live, when support tickets spike and teams return to the spreadsheet they never really stopped using.

The person who built the old system

Here’s a scenario most managers will recognise. There’s someone on the team who has run the current system for years. They know every quirk, every workaround, every use case the system vendor never anticipated. When the new ERP or Finance system comes in, they get put through the same training as everyone else.

On the surface they seem fine. They attend the sessions, and don’t object. But they’re slow to test and their deliverables lose momentum. In meetings they ask detailed questions about whether the new system can handle specific scenarios, and the answers aren’t always satisfying.

This usually isn’t about someone disliking change. They built something that worked and protected the business through difficult periods. If the new system is replacing it, they need to feel confident it’s genuinely better, not just newer. Until then, they’re unlikely to champion it, and because they’re often one of the most respected people in the team, that matters far more than their individual adoption.

This is one of those moments where a manager can either make things worse or handle it well. One hears the detailed questions as obstruction and pushes back. Another recognises what sits behind them and brings that person into validating the new system, so their expertise helps the programme instead of pulling against it.

The load no one is measuring

The other thing that rarely makes it onto a risk log is cumulative fatigue. ERP and Finance transformation doesn’t arrive in isolation. It lands on top of month-end reporting, a restructure that isn’t quite finished, three other initiatives someone is nominally leading, and the general operational pressure that never really goes away.

People can support the ambition and still not have the capacity to absorb the pace. When that happens, the signs are easy to misread. Actions aren’t completed because someone is labelled resistant. In reality, they have fourteen other things with equal priority, and no one has helped them triage. Workshops become less participative because people are running on empty.

Recognising that is part of good EQ leadership. It doesn’t mean slowing the programme every time someone is busy. It means being realistic about what you’re asking of people who are already stretched, and making conscious choices about pace instead of assuming momentum will carry everything through.

What it looks like when a manager reads the room

The difference between a manager who has this and one who doesn’t usually comes to life in small moments rather than big ones.

The energy in a workshop drops halfway through. The manager who misses it keeps pushing through the agenda because there’s still a lot to cover. The manager who notices it pauses and says, “This is getting quite dense; let’s take five,” then uses the break to check in with the two people who went quiet twenty minutes earlier. That quick conversation brings out something the project team hadn’t picked up. The second half of the session lands very differently.

An action keeps slipping from the same person. The instinct is to escalate or tighten governance. An EQ response is to ask first: do they understand the task, believe the direction is right, and have the capacity right now? The answer changes what you do next. It might be a resourcing issue. They may need more clarity. Or the action may be stuck behind something upstream that nobody has flagged.

A stakeholder above you asks whether the programme is on track. Everything on the plan is green. But you’ve noticed the energy in the team has shifted, and a few experienced people have stopped contributing in sessions. The better response is to say that out loud rather than flatten it into a status update: “The plan is green, but confidence feels lower than it did two months ago, and I think we need to understand why before it turns into something bigger.”

That last one is difficult. It requires a manager to be honest upward about something that isn’t on the dashboard, when the easier thing is to report green and hope it resolves itself. But if nobody says it early, the issue usually surfaces later in a much more expensive form.

When underground resistance becomes visible, it’s usually too late to be cheap to fix

By the time resistance is visible on a risk log, it has generally been building for months. Adoption dips, teams revert to old processes, and the business case starts to feel optimistic. Sponsors lose confidence because the organisation never fully moved with the technology.

The investment to address it then is far larger than the investment to manage it earlier. A conversation in week four is a conversation. The same issue in week twenty, when it has hardened into disengagement and workaround, is a recovery effort.

That’s why EQ leadership needs to run through the whole programme, not appear later as a soft add-on when things start going wrong. It changes what managers notice, what they ask about, and whether people feel able to say what they really think.

One useful question to ask regularly is simple: what are people not saying? You can usually find the answer if you make enough room for it to come out.

Making it practical

In practice, this comes down to what managers pay attention to and how they respond to what they find.

Ask smaller, more honest questions. Instead of “is everyone happy with the plan”, try “where is confidence lowest right now”. Instead of “any concerns”, try “what would make the next phase easier to absorb”. Those questions give people a route into honesty without requiring them to position themselves as difficult.

Pay attention to where the silence is coming from. If one function is less engaged than others, the issue is probably local and worth understanding. Any time your most experienced people are holding back, that’s an ownership or confidence signal worth taking seriously. If everything seems fine at the leadership level but operational teams are hesitant, the change may make strategic sense but feel chaotic in day-to-day work.

And when something is received differently to how you expected, treat that as information before you treat it as a problem. A frustrated comment in a workshop often contains a genuine concern wrapped in irritation. A workaround that appears three weeks after go-live usually points to a process gap or a training issue that nobody felt comfortable raising directly.

None of this replaces delivery rigour. The plan still matters. But plans and governance won’t tell you what people are really thinking or how they’re actually responding. That’s where this kind of leadership matters most. It helps keep a programme moving in conditions that are usually messier and more human than the plan suggests.

Contact us today to discuss emotionally intelligent leadership, or explore more guidance in our EQ Hub.