Why Change Resistance Is Rational
Most leaders talk about resistance to change as if it were a flaw in the people being asked to change. It isn't. In most cases, resistance is a rational response to what those people have already lived through.
Think about what you are asking for. You want people to give up a way of working they have mastered, one that makes them competent, trusted and efficient, in exchange for a promise. The new way may well be better for the organisation, eventually. For them, in the short term, it means being slower, less sure and more exposed. Weighing that trade and hesitating is not a mindset problem. It is judgement.
That judgement is usually built on history. Most people in large organisations have lived through several transformations: initiatives launched with energy and quietly dropped, tools learned and then replaced before they paid off. Waiting to see whether this one lasts is a reasonable strategy.
Resistance is also information. When a team pushes back, they are often telling you something your plan missed: a dependency nobody mapped, a workload nobody reduced, a process step that only works on a slide.
I've seen this play out with something as small as a timesheet. An organisation rolled out a new interface for logging time and made it mandatory. Everyone complied. Over the following weeks, people started reporting that the new process took longer than the old one and was costing them more time, not less.
That sounds trivial until you do the maths. Picture an enterprise of around 12,000 employees. Ten to fifteen extra minutes a week per person adds up to between 90,000 and 140,000 hours a year. At blended salary costs, that is roughly $1.5 to 2.3 million, the equivalent of 50 to 75 full-time employees doing nothing but filling in timesheets.
Management could have called that resistance and pushed harder. Instead, they let people choose between the old way and the new one, and tracked both time and preference. The old process came out ahead, so they took it, redesigned it and improved on it. Notice what the resistance looked like: not refusal, but feedback. The people pushing back were right, and the organisation ended up with a better process because someone listened.
AI makes this sharper. When people hesitate to adopt an AI tool, the reason is rarely ignorance. They are asking whether it makes their expertise less valuable, whether the output can be trusted, and who gets blamed when it is wrong. Those are fair questions, and another training session doesn't answer them.
The shift for leaders is simple to say and hard to do: stop asking how to overcome resistance and start asking what it is telling you. Treat the people resisting as the first real users of your change, not its obstacles. Fix what they point to, and show through what you do, not what you announce, that the change is worth their effort.
People rarely resist change itself. They resist giving up what works for a promise they have learned not to trust.
I publish a new article on transformation, delivery and leadership every week here. For AI, subscribe to Decoded, my monthly newsletter where I decipher the news and what it means for leaders.
