AI Thinking

Instead of “AI rollout” think “AI Enablement”

Why AI rollouts are seeing low usage and what to do about it

Katie Lips, CEO and Founder of Rebel Futures/26 August 2026
Instead of “AI rollout” think “AI Enablement”

In plenty of organisations, AI adoption is high, but usage is low. Approximately 70% of Fortune 500 companies hold Microsoft Copilot licenses, yet weekly active use is 20-30%. Daily use, even inside organisations that consider themselves committed to the rollout, stays under forty percent.

If AI is so powerful, why isn’t the whole team using it every day? If someone has a license, and they’re not using it every day, they’re clearly not seeing the benefit. If colleagues are not seeing or realising the benefit, teams are not AI enabled, and workflows, and businesses are most certainly not transformed.

A license for 10,000 people in a medium sized firm costs over £3m a year. The money’s being spent, but value is most definitely not realised. So what’s stopping teams across organisations from using AI (at all), and from exploiting it to its maximum capability?

You will have read about tech companies incentivising staff to burn through tokens with hacks like token usage leaderboards boosting bragging rights. But in regular businesses, where people want to do their current jobs well, how can we encourage and enable AI usage effectively?

Research on why adoption stalls for most businesses is pretty consistent: undefined workflows, data governance restrictions, output quality requiring more manual rework than without AI assistance, and a lack of training. It’s not because there was no token burn rate leaderboard. And none of these issues are specific to Copilot - they’re relevant to any AI rollout, indeed to any technology rollout anywhere.

What I have seen in quick to act, innovative organisations keen to get AI working for them, is that there is sometimes a ‘you go figure it out’ mentality. If that’s the case, there will always be some team members who do, and plenty who don’t. And it’s not about technical skills or a lack of an ‘instruction manual’, it’s more about personality. Some say it’s about imagination “I’m not imaginative enough to consider what AI can do for me and I dislike starting with a blank page”, others say it’s about time “I can’t take time away from my day job to experiment and configure.”

It’s clear AI can deliver productivity gains in any industry, in any line of work, in any process. But, only if it’s configured well. Only if the tools are well understood, and more importantly, well adapted, before they can be truly adopted, and value realised.

There’s lots of unglamorous work to be done: configuring the tool itself, building reusable prompts and skills, running training and office hours and an evangelist network. And to do this well, as a leader, you need to really understand what helps people, and what doesn’t; what their motivations are, and their blockers. This in turn, is all about relationship building, and listening.

Then there’s the use case development, and for me this is not about identifying hundreds of use cases and seeing what sticks. Instead, it’s about understanding pain points, problems and jobs to be done. I bring a sharp product thinking lens to this piece; because without identifying the problem you’re solving, forcing AI on top of an already well performing process can cause more problems, than it fixes.

Then there’s test and learn within the ‘rollout’. And by the way, the word ‘rollout’ is probably the worst way to describe AI enablement. ‘Rollout’ assumes you know all the answers at the start and you are managing a simple change - from state A to state B. It never goes like that, nor should it.

Models develop, internal capabilities develop, people acquire new skills, and develop new ideas. AI processes you identify at the start, will evolve and be honed by the people using them. It is, and should be, iterative.

AI pilots and rollouts are failing because they aren’t enabled properly. Not enough time, care, attention, listening, problem identification, experimentation, and change management is put in place around them.

Whatever the tool: Copilot, Chat GPT, Claude or any other AI tool, the tool is just the start.

At Rebel Futures, we can help by understanding your organisational needs and designing enablement programmes that help you get true value from AI.

Katie Lips is CEO and Founder of Rebel Futures. She helps organisations grasp the opportunities at technology inflection points, from the early web and pre-iPhone mobile to cloud-based SaaS and now AI. She has held senior roles at EY and Aimia, and was Head of Digital Policy at Which?. Katie holds a Harvard Kennedy School qualification in Leading in Artificial Intelligence and is a Founder Institute graduate.

Related: explore our work on AI Adoption.

base44
Edit with Base44