THE AI Adoption Office
AI adoption · change · execution

Most organisations have already bought AI. Far fewer have changed how the work gets done.

That gap is where most AI programmes quietly sit, and it is rarely anyone's fault. The technology arrived faster than the work around it could be redesigned. Closing that distance is the job.

Book an intro call 30 minutes. No pitch deck.
Twenty years leading transformation, ERP and GBS programmes inside adidas, Philips, Heineken, Unilever, Nike, LyondellBasell and Accenture. I have sat on your side of the table.

What usually happens

Deployment is not adoption.

The tools work. People use them a little, often for drafting and summarising. And the process around those tools is still the process that was designed for a world without them, with one more step added on top.

That is not resistance. In most organisations I have worked in, people want to use these tools well. What they are missing is clarity about why AI is being introduced, honesty about how their role might change, and the time and support to build real confidence. Leaders are usually missing something too: a reliable picture of where their organisation actually stands, rather than what the usage report suggests.

So the value stays theoretical. The spend is already committed. What has not been captured yet is the return.

The method

The HUMAN Framework

A structured way to turn deployed AI into adopted AI. It treats people as the ones doing the changing, not the ones being changed, and it works the same way whichever model or vendor sits underneath.

H

Honest inventory

Everyone has a licence. The useful question is who can do something meaningful with it, and where confidence is genuinely high.

U

Understand the role shift

If AI takes on part of a job, what is the job now? Saying this out loud early is one of the strongest things a leadership team can do.

M

Map the boundaries

Where AI decides, where it advises, and where human judgement stays. Who owns the outcome, and how someone raises a concern.

A

Adopt with intention

Redesign the workflow around the capability rather than fitting the capability into the old workflow. Usage is not the outcome. Name the outcome first.

N

Nurture human capability

Build capability that stays. If the advisors left tomorrow, what would keep working on its own?

+

Normalize the conversation

The stage that runs through all the others. People need to be able to say "I am not sure I trust this yet" without it counting against them.

Where to start

The AI Adoption Readiness Scan

Entry engagement

A clear read on the conditions your AI is landing into

A structured diagnostic across seven readiness dimensions, answered by leaders and teams alike. Everyone who takes part gets a personal reflection back. Leaders get an aggregated picture of where readiness is strong, where it is thin, and where the view from the top and the view from the floor have drifted apart.

  • Readiness by dimension and by role
  • The gaps worth acting on first
  • A debrief that turns findings into decisions

What follows

If the Scan surfaces something worth acting on, there are two ways I keep working with you.

  • A twelve week programme covering use cases, leadership literacy, role and workflow redesign, and governance
  • Retained advisory, including executive coaching and team upskilling

Scope depends on size and on where you are starting from, so I would rather work that out on a call than guess it here.


Start with a conversation

Thirty minutes, no obligation. Tell me what you have deployed and where it is getting stuck, and I will tell you honestly whether I can help.