You are Solving the Wrong Problem

You’ve approved the budget. You’ve hired the consultants. You’ve commissioned the change management strategy — the stakeholder analysis, the communication plan, the training schedule, the engagement workshops.

And somewhere in the back of your mind, you’re not confident it’s going to work.

That instinct is worth examining.

Most large change programs treat resistance as the primary obstacle. People aren’t adopting the new system. People aren’t following the new process. People aren’t enthusiastic. The answer, apparently, is more communication. More engagement. More persuasion. More budget for the people who specialise in persuasion.

But watch what’s actually happening in organisations where change lands without the drama.

Nobody sold anybody on anything.

Think about the last time you changed your own behaviour — genuinely, not temporarily. Not because someone ran a workshop. Not because a consultant presented a compelling case. Because you saw something clearly. A doctor showed you a scan. A conversation landed differently than you expected. A number stopped being abstract and became real.

The behaviour changed because the awareness changed. Not the other way around.

Now think about the large-scale ERP or systems change you’re sponsoring. Your change management program is built on the assumption that people are resistant. That they need to be brought along. That motivation is the gap.

What if the gap is something else entirely?

Here’s what I’ve seen repeatedly. The people who aren’t adopting the new system aren’t resistant to change. They don’t yet see the problem the change is solving. Not clearly. Not personally. Not in terms of their own work.

They’ve been told the organisation needs this. They’ve sat through the town hall. They’ve read the CEO message in the newsletter. They understand it abstractly.

But they haven’t had the moment where it became obvious to them — in their own terms — why the old way is the problem.

That moment is the seed. Everything else is water before the seed exists.

A council finance team I worked with had been told for eighteen months that the new financial system would improve reporting and reduce manual reconciliation. Eighteen months of communication. Eighteen months of training sessions. Eighteen months of polite compliance and private scepticism.

Then someone sat with them for half a day. Not to explain the system. To map the current process — step by step, person by person, task by task. They counted the hours. They identified the errors. They traced what happened when a journal entry went wrong at month-end.

By lunchtime, the team was asking when the new system was going live.

Nothing had changed except what they could see.

This is the distinction that most change programs miss. They are built to answer the question “how do we get people to accept this?” — when the more useful question is “what would people need to see, clearly, for this to make obvious sense to them?”

The first question makes change a persuasion problem. The second makes it a visibility problem.

Persuasion is expensive, slow, and produces compliance. Visibility is faster and produces ownership.

The leader’s role in this is not to be an evangelist for the new world. That approach breeds cynicism — especially in people who’ve lived through three previous transformation programs that each arrived with its own set of enthusiastic consultants and didn’t deliver what was promised.

The leader’s role is to create enough of the right conditions that people arrive at the realisation themselves.

That means being genuinely honest about what the current state costs. Not in an abstract ROI calculation buried in a business case. In real terms. In terms of this team’s actual Tuesday morning.

It means creating enough proximity between people and the actual problem that the problem becomes undeniable rather than theoretical.

It means asking different questions in project meetings. Not “are stakeholders engaged?” but “do people actually understand what’s broken about the current state, in their own words?”

Once people see the problem clearly, the resistance question largely answers itself. Not entirely — there will always be individuals whose resistance is about something other than understanding. But the mass of quiet non-adoption that haunts most large programs? That’s not resistance. That’s people who were never shown the problem in terms that made it real.

The change management budget you’re approving is mostly trying to solve a persuasion problem. The actual problem is a clarity problem.

Those require different interventions. And one of them is significantly cheaper.