Resistance to change in organisations

What if the most useful information about your change initiative is coming from the people who aren't getting on board?

It's not a comfortable thought. Leaders invest significant energy in designing change well - the business case, the communication plan, the rollout sequence. When parts of the organisation don't move, the instinct is to treat that as a problem. Overcome the resistance. Communicate more clearly. Find the champions and use them to bring the reluctant along.

But there's something worth noticing in the pattern of what "resistance" looks like in most organisations. It's rarely open opposition - that would be easier to work with. It's quieter than that. Meetings happen but nothing changes afterwards. New processes get followed on paper but the old ways persist underneath. People nod in the room and then carry on exactly as before. Gartner research found that 36% of business leaders said their teams are more likely to hesitate and delay action to see if changes will stick before adopting them - a rational response that rarely shows up in any project plan.

That pattern - the gap between stated adoption and lived reality - is worth taking seriously. Not as something to push through, but as something to listen to.

What resistance looks like when you're not looking for it

The word "resistance" conjures images of confrontation - people pushing back in meetings, raising objections, refusing to engage. That kind of resistance is relatively rare and, when it happens, relatively useful. Someone who tells you directly that they think this is wrong is giving you something to work with.

The more common forms are quieter and harder to read. Teams that adopt new language but not new behaviour. Middle managers who implement the letter of the change but not the spirit. People who engage enthusiastically in workshops and then return to their desks unchanged. Projects that technically complete but somehow don't produce the outcomes everyone expected.

These patterns tend to get labelled as "resistance" and treated as something to manage. But there's a different way of reading them. What if resistance isn't a problem to overcome? What if it's information about the conditions inside your organisation - and the most useful feedback you're going to get?

What the resistance is responding to

When people resist change, they're rarely resisting the change itself. They're responding to something about the environment the change is entering. The same initiative can land smoothly in one organisation and meet a wall in another - not because of the initiative, but because of the conditions it's arriving into.

Five patterns keep appearing across the organisations we work with. Each one produces behaviour that looks like resistance but is telling you something specific.

When trust is low, people wait. They've seen changes announced before. They've watched previous initiatives arrive with energy and then quietly fade. They've learned that the safest response is to wait and see whether this one is real before investing effort. This isn't cynicism - it's pattern recognition. Gartner's 2025 research found that 79% of employees have low trust in change. That number doesn't describe a workforce that's resistant. It describes a workforce that's been taught, through experience, to be cautious.

When capacity is stretched, people protect what they have. Change requires energy - cognitive, emotional, practical. When people are already running at full stretch, adopting something new means dropping something else. If the organisation hasn't created space for the change, people will unconsciously protect their existing workload, relationships, and routines. The behaviour looks like reluctance. The cause is a system already running at capacity with nowhere to absorb something new.

When clarity is missing, people fill the gap with anxiety. Uncertainty about what the change means in practice - for roles, for teams, for day-to-day work - creates a vacuum that people fill with their own assumptions, usually worse than reality. The resulting hesitation isn't resistance to the change. It's resistance to the uncertainty. The less specific the picture of what "after" looks like, the more energy goes into imagining worst cases.

When involvement is absent, people don't feel ownership. Change designed in a room somewhere and communicated outward creates a specific dynamic: the people expected to make it work had no hand in shaping it. The resistance here isn't about the content of the change. It's about the experience of having something done to you rather than with you. It's a completely rational response to being asked to commit to something you had no part in creating.

When safety is uncertain, people stay still. If the organisation's track record suggests that admitting difficulty, asking for help, or raising concerns leads to negative consequences, people will do the safest thing available: comply on the surface and protect themselves underneath. This is the most invisible form of resistance and the hardest to shift, because it's being reinforced by signals the organisation may not even realise it's sending.

The conditions, not the communication

This is where the conventional advice about resistance starts to break down. "Communicate more clearly" assumes the problem is that people don't understand the change. "Get better buy-in" assumes people need persuading. "Find the champions" assumes the solution is social pressure.

None of that addresses what the resistance is actually responding to. You can communicate a change brilliantly into an environment where trust is low, and the communication will make no difference. You can find enthusiastic champions in a system running at full capacity, and the enthusiasm won't create the space the change needs to land.

The pattern across organisations that navigate change well isn't better communication or more sophisticated change management methodology. It's attention to the conditions the change is entering. Leaders who get curious about what the resistance is telling them - rather than treating it as something to push through - tend to find that the answers reshape how they approach the change itself.

Sometimes the resistance reveals a trust deficit that needs addressing before this particular change can land. Sometimes it surfaces a capacity problem that no amount of project planning can solve. Sometimes it shows that the organisation's experience of previous change has created patterns that will repeat until someone breaks the cycle.

Listening to resistance in practice

What does it look like when leaders treat resistance as feedback rather than an obstacle?

It starts with a different question. Instead of "how do we get people on board?", the question becomes "what is this response telling us about the environment?" That shift changes what you pay attention to. You start noticing which parts of the organisation are responding and which aren't - and what that pattern reveals about local conditions. You start asking whether the organisation is ready for this change, not just whether the change is ready for the organisation.

It often means slowing down in order to move faster. A leader we worked with in a housing association merger noticed that frontline teams were complying with new processes but the quality of work was quietly declining. Rather than pushing harder, she paused to understand what was happening. The teams weren't resisting the new processes - they were grieving the loss of established relationships and ways of working that the merger had disrupted. Once that was acknowledged and worked with, not just communicated past, adoption shifted from compliance to genuine engagement.

This isn't about being soft on change or accepting that nothing should ever be uncomfortable. Change is inherently disruptive, and some discomfort is part of the process. The distinction is between discomfort that comes from genuine adaptation - learning new things, adjusting to new relationships, developing new capabilities - and discomfort that comes from the change ignoring the conditions it's entering. The first kind is productive. The second kind produces resistance that no amount of communication will resolve.

What your organisation might be telling you

Change fatigue is one of the most discussed challenges in organisational life right now, and for good reason. But fatigue and resistance aren't the same thing. Fatigue says "I'm exhausted." Resistance says "something about this isn't right." Both deserve attention, but they need different responses.

If you're experiencing resistance to a change initiative right now, it might be worth sitting with a few questions before reaching for the standard toolkit:

What have people in this organisation learned about change from their previous experiences here? What would a rational person do, given that history?

Where is the capacity for this change supposed to come from? What are people being asked to stop doing, or do less of, to make space for it?

How much of the design of this change involved the people who'll need to make it work?

What happens in this organisation when someone admits they're struggling with a change? Is it safe to say "this is hard"?

These aren't comfortable questions. They often surface things the organisation would rather not look at. But they're the questions that resistance is already asking - just in a language that's easy to misread.

The organisations that build real change capability aren't the ones that get better at overcoming resistance. They're the ones that get better at listening to it.