The Change Will Happen. The Road Is a Choice.

Resistance is guaranteed. The question is what the organisation looks like on the other side.

Throughout my career, I have been inside many kinds of transitions. Companies merging. Businesses moving from B2C to B2B. Information systems being implemented. Processes being redesigned. Management teams being replaced. Some changes were small. Some were dramatic enough to redraw the entire organisation.

They were all different - different scale, different pressure, different leadership. But two things were always true:

There were always people who resisted.

And the change always happened in the end.

So the real question was never whether the change would go through. It was about the journey itself.

Two Companies, Two Roads, Same Destination

I have seen many changes up close, but two extremes showed me how wide and different the journey can be. Both succeeded. Both hit their go-live. Both delivered the outcome management wanted.

But what happened in between was not the same.

The first company treated the change as a human event, not only an operational one. Senior management brought everyone into one room for a full-day workshop - warehouse workers, production floor, QA, QC, middle managers, all together. They walked through what was changing, why it was necessary, and how it would affect each group. They answered questions. They listened. They stayed in the room.

People walked out of that workshop understanding the change. Not all of them were enthusiastic - some had concerns, some were cautious. But many were on board, and some were genuinely excited. By the time the rollout began, the organisation was pointing in the same direction.

The second company did the opposite. Senior management made the decision, handed it to local managers, and expected it to propagate. There was no workshop. No context. No conversation. Local managers - themselves only partially informed - had to implement something they couldn't fully explain. Employees found out in pieces. They were confused. They were frustrated. They felt the change was happening to them, not with them.

Both companies achieved their goal. The system went live. The process was adopted. On paper, both were a success.

But the experience was not the same. And the organisation that emerged was not the same.

Why the Road Matters More Than You Think

The first company ended up with a workforce that had been through a change together. That experience became an asset - a shared memory of “we can do this.” The next change was easier.

The second company ended up with a workforce that had survived a change. That experience became a liability - a shared memory of “we are not told things here.” The next change was harder. And the one after that, harder still.

This is the quiet cost most change plans never account for. You can meet every milestone on the Gantt chart and still damage the thing that makes the next change possible — the trust between management and the people doing the work.

What Resistance Is Actually Telling You

When people push back, the easy answer is to label them: resistant, negative, difficult, not on board. Once that label goes on, the conversation changes. From listening to convincing. From curiosity to pressure.

But resistance is rarely irrational. In my experience, it is almost always about something underneath the change itself:

• Loss of competence - they were good at the old way. The new way makes them a beginner again.

• Loss of control - decisions that used to be theirs are now someone else's.

• Loss of identity - “I'm the person people come to for this” becomes “what am I now?”

• Loss of relationships - restructures break teams that took years to form.

• Loss of clarity - the old way was predictable. The new way is not.

• Broken trust - they've been here before. The last change was announced the same way - and it didn't go well.

None of these are irrational. All of them deserve a real answer - not another slide in the rollout deck.

What the First Company Did Differently

They didn't do anything magical. What they did was treat the change with the weight it deserved.

The workshop didn't open with “here's what we're doing.” It opened with “here's why we have to.” That distinction matters more than it looks. People do not commit to a solution they don't believe is solving a real problem - no matter how well the solution is explained.

Everyone was in the same room. Warehouse, production, QA, management, all hearing the same version at the same time. No one had to piece the story together from what a colleague thought they heard. No one was left wondering what the other side had been told.

And they named the loss before they sold the gain. They said out loud what the change was asking people to let go of - competence, routine, relationships, a quiet sense of being good at the job - before they moved on to the benefits. You don't have to fix those losses. You have to see them, and you have to say you see them.

Most importantly, they stayed in the room. Not a one-way announcement but a real conversation. Real questions, real concerns, real answers - and the discipline to sit with the uncomfortable ones. The loudest objector, in my experience, is almost always saying what everyone else is thinking quietly.

And then they gave it time. Acceptance is a process, not an event. Silence in the first meeting is not agreement - it is processing.

The Part You Actually Control

Every real change meets resistance. Every real change goes through anyway. Those two facts are fixed.

What is not fixed is the road - and every road leaves a mark. One mark makes the next change easier. The other makes it harder. There is no neutral option.

That is the real decision on the table. Not whether to run the change. How your people will remember it when it's done.

One final tip: the best resistance conversation is usually not a meeting. It's a five-minute coffee with the person who didn't say anything in the room.