{"id":8237,"date":"2026-06-02T14:40:41","date_gmt":"2026-06-02T14:40:41","guid":{"rendered":"http:\/\/version1.thinktankdev.org.uk\/en-us\/?p=8237"},"modified":"2026-07-21T15:09:46","modified_gmt":"2026-07-21T15:09:46","slug":"resistance-is-gold-and-key-to-people-led-change-management","status":"publish","type":"post","link":"https:\/\/version1.thinktankdev.org.uk\/en-us\/blog\/resistance-is-gold-and-key-to-people-led-change-management\/","title":{"rendered":"Resistance is gold and key to people-led change management\u00a0"},"content":{"rendered":"

This is the second in a series on AI-led change. The first post,\u00a0\u2018<\/i>Navigating AI-led disruption: why people, not platforms, determine success<\/i><\/a>\u2019, made the case that genuine AI transformation depends on people,\u00a0culture\u00a0and leadership.\u00a0<\/i>\u00a0<\/p>\n

This post examines what most organisations miss when they\u00a0encounter\u00a0resistance to AI and why learning to read it differently is one of the most powerful things a change programme can do.<\/i>\u00a0<\/p>\n

When people push back on an AI programme, fall silent in meetings, agree in the\u00a0room\u00a0and do nothing afterwards\u00a0or\u00a0quietly route around the new tool, the instinct is to treat it as a problem to overcome. A better communications plan, more training\u00a0or\u00a0clearer sponsorship from above.\u00a0<\/p>\n

What if it is something more useful than that? What if resistance, read carefully, tells you\u00a0almost everything\u00a0you need to know about what the programme has not yet got right?\u00a0<\/p>\n

In our experience working across AI adoption programmes, resistance is rarely irrational and\u00a0almost never\u00a0random. It tends to carry one of four types of insight \u2014 each one a signal worth understanding before you decide how to respond.<\/p>\n

Four things resistance is usually telling you<\/h2>\n

The first is <b> implementation insight:<\/b> the practitioner is telling you, from direct experience, that the approach will not work. "We tried this before" or "our systems are not set up for this" sounds like obstruction. It is usually an accurate diagnosis. The question that surfaces it is simple: walk me through what you see breaking down.<\/p>\n

The second is <b> contextual insight: <\/b> local knowledge about how things actually work that never made it into the programme plan. The culture, the informal systems, the invisible architecture of decision-making in a particular team. Programmes planned from the centre miss this almost by design. The people closest to the work rarely do.<\/p>\n

The third is <b> ethical insight: <\/b>concerns about fairness, unintended consequences, about who benefits and who does not. "This doesn't feel right" or "what about the impact on…" are not emotional reactions to be managed past. They are frequently the most important signals in the room, and the ones most likely to predict downstream problems if left unaddressed.<\/p>\n

The fourth is <b>identity insight:<\/b> the values and sense of purpose at stake when a change asks people to do their job differently. An experienced developer, analyst, or clinician who says "I didn't spend years learning this to hand it over to a tool" is not being obstructive. They are telling you what the change is costing them before the programme has offered them anything in return. That is information worth sitting with.<\/p>\n

None of\u00a0the above\u00a0indicates\u00a0a workforce that needs managing. They signal a programme that needs to listen differently. And when you do listen, resistance stops being an obstacle and starts becoming the criteria for what good adoption\u00a0actually looks\u00a0like.\u00a0<\/p>\n

Why most programmes are not set up to hear it<\/b>\u00a0<\/h3>\n

The readiness data helps explain why the gap is so persistent.\u00a0\u00a0<\/p>\n