The change plan ticked every box, communications went out on schedule, the FAQ document was thorough, the town hall ran well.
Three months later, adoption has stalled and the same objections surface in every team meeting. The usual diagnosis is resistance. The usual fix is more communication. Both are usually wrong.
It is not a comprehension program
The standard response treats resistance as a misunderstanding. Explain it again, with better slides and a stronger case for why it matters. But most people affected by a change understand exactly what is happening.
What they are responding to is the order in which it happened – decided, announced, explained. At no point in that sequence was anyone asked. People are not resisting change. They are resisting being changed.
Where the gap really opens
Most organisations put enormous effort into strategy. A merger, a new customer segment, a technology shift, a push into AI. The harder part comes next: turning that strategy into the work people do on Monday morning.
Somewhere between the strategy document and the day-to-day sits a discipline that is often rushed or skipped altogether. Organisational design – at its core, it asks practical questions:
- What is the work that actually needs to happen?
- Who owns which parts of it?
- What capabilities are needed, and where should they sit?
- What has to stop to make room for what is new?
Here is the problem – these questions are usually answered in a room that does not include the people who do the work.
So the design arrives finished, and it often does not fit.
Not because the strategy is wrong, but because the people closest to the work are the ones who know where it will rub, and nobody asked them. What gets labelled as resistance is very often people pointing, quite accurately, at a flaw in the design.
Two speeds, one set of people
There is another reason change stalls, and it rarely makes it into the project plan – organisations now run at two speeds at once. One speed is about running the business: reliability, efficiency, scale, getting today’s work done well. The other is about changing the business: testing new ideas, building new capability, learning fast and adjusting as you go.
Both have to happen. Usually at the same time. Often by the same people.
And they are very different kinds of work. When a change is announced, it is typically layered on top of a full day job. No one has redesigned the role, taken anything away, or worked out how the team will keep the day-to-day running while learning a new way of operating.
From the outside, slow uptake looks like reluctance. From the inside, it feels like being asked to do two jobs with the time for one.
That is not resistance. That is arithmetic.
What changes when you ask?
We worked with a team that had rolled out a new operating model with a strong communications plan and low uptake regardless. Before the next phase, we ran a short round of listening sessions. The objections we heard were not about the model itself. They were about how it would actually land in the team’s day-to-day work, things the people who designed it could not have seen from where they sat. That input only surfaced because people were asked about their work, not about the change. Once it shaped phase two, adoption moved without a single extra memo.
Orchestration is designed, not announced
There is a lot of talk right now about orchestration. Aligning people, roles and capability across different kinds of work, while keeping the whole organisation functioning.
It is a useful idea. But orchestration is not something you announce – it is something you design, with the people who will be playing their part.
That is what turns a strategy into a coordinated set of activities people can actually deliver. And it is where most of what gets called resistance quietly disappears.
Before your next announcement goes out
Ask three questions:
- Who from the affected group has helped shape how this will work, not just been told it is happening?
- What are we asking people to stop, so they have room to start?
- Which parts of the design have been tested against the real work, by the people who do it?
If your last change initiative met resistance you could not fully explain, the more useful question is not what people misunderstood.
It is what they were never asked.
