Designing the future is easy. Living it is hard.
Every organisation I have ever worked with knows roughly what it needs to change. The slide deck is clear. The strategy is documented. The rationale is sound.
The problem shows up six months later, when the strategy has not moved and nobody can quite explain why.
The 90/0 Problem
Here is a pattern I see repeatedly. An organisation embarks on a significant change, a technology upgrade, a restructure, an AI programme. They spend around 90 percent of their budget on the Plan. The technology. The process design. The project management.
They spend close to nothing on the Psychology. On helping people understand what is changing and why. On building the trust that makes people willing to try something new. On working through the resistance that is entirely predictable if you know what to look for.
The divide this creates is widening. The organisations that have moved on treat AI as a colleague, not a tool to deploy. Their people are shifting from doing the work to directing it. Change happens in short, continuous cycles rather than year-long programmes with a go-live date and a launch party.
Most organisations are still doing the old thing. They treat AI like a software rollout. They handle adoption as an afterthought and mark success when the system goes live, not when people actually use it differently. The 90/0 budget split is the mechanism that explains the gap between these two groups. It is structural, not a failure of intent.
The Plan is easier to budget for, easier to measure, easier to present to a board. The Psychology is harder to quantify and easier to defer. Until the programme stalls and the investment is at risk.
Why This Matters Now
AI has made the gap impossible to ignore. Not because AI is uniquely complex but because it moves faster than previous change cycles, and the stakes for getting adoption wrong are higher. When your competitive advantage depends on your people actually using new tools and new ways of working, the adoption question is not a soft issue. It is the main issue.
I have watched AI transformation programmes stall not because the model was wrong, not because the integration was technically difficult, but because nobody in the organisation genuinely believed the change was for them. They saw it as a cost reduction exercise with a new name. They were not entirely wrong.
The organisations getting this right are not necessarily the ones with the most sophisticated AI strategy. They are the ones that treated adoption as a first-class problem from the start, not an afterthought once the technology was in place.
The rate of change itself is accelerating. The organisations that keep up will not be those that run a transformation every few years. They will be the ones that have built the human capacity to absorb change continuously. Micro-transformations rather than mega-programmes. That requires a completely different approach to adoption.
Intention to Adoption
There is a gap between Intention and Adoption that most change programmes fall into and never escape. Intention is the easy part. Leadership is aligned. The case for change is clear. Everyone agrees, in meetings, that this is the right direction.
Adoption is what happens when the meeting ends and people return to their desks. Do they actually change what they do? Do they use the new system, follow the new process, show up differently in the ways the strategy requires? That is the real measure of whether change has happened.
Most organisations stop at Intention and call it transformation. They measure launch success rather than adoption depth. They count training sessions rather than behaviour change. They move on to the next initiative before the previous one has fully landed.
Adoption is the actual work. It requires sustained attention, clear communication, visible leadership commitment, and a genuine willingness to listen to the people who are being asked to change. Not to slow things down. To give the change a real chance of sticking.
I have a name for the role that this work requires. I call it the Chief Adoption Officer. Not a job title so much as a philosophy. A commitment to making the human side of change as rigorous and well-resourced as the technical side.
This shift, from people who do the work to people who direct AI to do it, is not a technical change. It is a behavioural one. That is precisely where adoption thinking applies.
Change is inevitable.
Adoption is optional.
I help you choose it.