Change management for AI: why the tools are not enough
Installed AI systems are not adopted systems: what distinguishes change management that works, why middle managers decide the game and what to measure.
There is a scene that repeats in the companies we visit: licences bought for everyone, the tool presented at the town hall with the customary enthusiasm, and six months later the usage dashboards telling another story, a minority using the instrument for real, a majority that opened it twice, and meanwhile, on personal phones, the unauthorised tools thriving. The MIT Project NANDA research (July 2025) photographed the paradox at scale: 95% of GenAI pilots with no P&L impact inside companies, and a flourishing shadow AI in over 90% of the same ones. People are not rejecting AI, they are rejecting AI the way we are bringing it to them.
The misunderstanding about change
AI change management fails almost always through the same misconception: it gets treated as communication, when it is redesign. The classic sequence, announcement, catalogue training, adoption campaign with posters and ambassadors, operates on awareness and leaves intact everything that determines behaviour: the process that never includes the instrument, the objectives rewarding the old way of working, the time nobody has freed for learning. McKinsey, in its State of AI research (2025), identifies workflow redesign as the factor with the largest impact on GenAI returns, and the finding also reads in reverse: where the workflow stays as before with a tool resting beside it, the return never arrives, and neither does adoption.
The second leg of the misunderstanding concerns incentives, which speak louder than any campaign. If AI-gained productivity translates, in people's eyes, into headcount at risk or targets raised without counterpart, resistance is not irrational, it is a correct reading of the implicit contract, and no prompting course dissolves it. Organisations where adoption takes root have answered first the question everyone asks in silence, what happens to me if this works, and they answered it with verifiable commitments, not reassurances.
Where the game is decided
The point of the system where change lives or dies is middle management, and it is also the point programmes neglect most, squeezed as they are between top-level and operational training. Middle managers decide, through a hundred micro-choices a day, whether the new way of working is truly permitted: whether learning time is legitimate time or stolen time, whether the mistake made with the new instrument is forgiven like the one made with the old, whether AI-assisted output counts in the meeting. A programme that gives this layer no instruments, no time and no reason of its own to want the change is asking people to cross a bridge their managers never approved.
Around this centre, the practices we see working have little spectacle about them: starting from the workflows where the pain is felt and the benefit is personal, not from the strategic-on-paper ones; using the first real users as designers of the rollout instead of testimonials; measuring adoption with usage and outcome numbers, not satisfaction surveys, and publishing those numbers with the same seriousness as business KPIs. And accepting a physiological timeline: the real adoption curve is measured in quarters, and the programmes declared victorious at month two are almost always measuring curiosity, not change.
The link that closes the circle
The regular reader will recognise the pieces interlocking here: the top's fluency sustaining the programme through difficult quarters, the common language keeping business, IT and risk from losing each other along the way, shadow AI as a symptom to read rather than repress, because it indicates exactly where the demand for instruments exceeds the official supply. Change management is not a workstream next to the others, it is the connective tissue, and in our rating model it lives inside Readiness and Confidence, the two dimensions where low scores best predict the pilots that will never scale.
In the ZeroFive chain this work is called AI Culture, and it typically comes after assessment and strategy for a practical reason: change needs to know what it is changing towards. To build the programme on your real map: calendly.com/fabiolalli/zerofive, or hello@zerofive.ai.
The test to run meanwhile costs an hour and is worth an audit: take the most sponsored AI tool of the past year and look at three numbers, weekly active users against licences, usage at ninety days against usage at launch, and how many official processes include it in writing. The third number, almost always, explains the first two.