When a technology programme meets resistance, the standard response is to escalate the change effort: more communications, more training sessions, more stakeholder workshops. The assumption underneath all of it is that resistance is the obstacle, something to be persuaded, equipped or managed past.
That assumption is usually wrong, and acting on it tends to make the programme worse. Resistance to a technology implementation is not noise in the signal. It is the signal.
What Resistance Is Actually Telling You
BCG’s 2020 survey of 825 senior executives found that 70 per cent of digital transformations fall short of their objectives. Bain’s 2024 Transformation and Change Survey of more than 400 executives put the figure higher still, at 88 per cent failing to achieve their original ambition. The two surveys measure different things, but both point the same way. Those programmes were rarely undone by stubborn employees. Their implementation drifted from operational reality, and the people doing the work could see it before the programme team could.
When a clinical team pushes back on a new patient records system, they are rarely resisting technology itself. They are reporting that the workflow design does not match how the ward runs at three in the morning, or that the training schedule assumes competencies the ward does not yet have. A finance team resisting a new reporting platform is often reporting that it strips out a nuance the team relies on daily, one the requirements process never surfaced.
The people closest to delivery are often the sharpest diagnosticians of implementation risk a programme has, and under schedule pressure, programme teams tend to receive that diagnosis as obstruction rather than intelligence.
The Stakeholder Management Euphemism
The phrase stakeholder management carries a weight of assumptions worth questioning. In practice, it frequently means: how do we get these people to comply?
The vocabulary gives it away: stakeholders segmented by resistance level, engagement plans that move people along an adoption curve, communications calibrated to reduce objections. The apparatus treats resistance as something to overcome rather than something to process.
Cornerstone OnDemand’s 2024 workforce readiness research found that 63 per cent of UK executives regard their own workforce as unprepared for change, and that employees without proper access to training were five times more likely to report difficulty adapting. That gap is a programme design failure. The workforce did not create it.
Whatfix’s survey of more than 1,100 software users found that 51 per cent had no role-based onboarding or support when a new system went live, and 78 per cent felt they lacked the expertise to use their daily tools properly. The investment did not happen. The resistance did.
What Good CIOs Do Differently
The best technology leaders share a habit: they treat early resistance as a discovery mechanism rather than a threat. When a pilot site pushes back, the first useful question is what the pilot site is seeing that the programme team is not, rather than how to handle the resistance.
That reframe slows the rollout and demands real engagement, but it catches design flaws at pilot cost instead of full-deployment cost. Decades of change research have produced one widely repeated adoption-failure statistic after another, none traceable to a verifiable source. The underlying point holds regardless: resistance is useful information, whatever number gets quoted beside it.
Change Fatigue and the Portfolio Problem
Reading resistance accurately gets harder inside an organisation running too many programmes at once. Prosci has benchmarked change saturation since 2007, and its latest research found 73 per cent of organisations near, at or past that point.
That is a portfolio problem wearing a change management label. Resistance to one programme, under those conditions, is often resistance to being asked to run faster on a track that is already full.
Reading the Room Before It Becomes a War Room
Before a programme leaves design, ask the people most affected a blunt question: what about this will not work? The phrasing matters. “What concerns do you have?” invites the polite version of resistance. “What will not work?” leaves no room for one.
Asked honestly, that question surfaces operational objections while they are still cheap to fix. Most of the time, the people who will resist a programme know it has problems before the programme team does. The only real question is whether the programme is structured to hear them, or finds out after go-live, when the resistance has nowhere left to go but into next year’s failure numbers.