You bought the tools. The work didn't get better.

Someone bought the licences. Someone said transformation a few times. Now, you're tasked with getting several hundred people to work differently with little more than a training budget and a usage dashboard.

The dashboard says eighty percent active, the leaderboard ranks people by how many messages they sent to your LLM.

Underneath it, things look less promising:

• People experimenting with no method, often in tools nobody approved
• Work coming back polished and hollow, and the person who received it quietly redoing it
• Some of your best people refusing, for reasons they're careful not to say out loud
• A question from finance about ROI that you cannot currently answer

Most organisations are exactly here. Almost none of them are saying so.

If AI has changed your work a great deal, admitting it invites a question about what you're for. If it hasn't changed at all, admitting that invites a question about whether you're keeping up. Both answers cost something. The safest available answer, for almost everyone, is that it's going fine.

My research calls this the silence cascade. The deeper someone's engagement with AI, the higher their identity stakes, and the less likely they are to disclose it. It's why usage numbers can look healthy while the organisation learns nothing. The learning is happening. It just happens privately, one person at a time, and never becomes anybody else's.

A senior leader in one of my research interviews, someone who describes himself as being on the right side of this technology:

No course fixes that. The thing being avoided isn't a skill.

Three things get sold as the answer. None of them are.

Drive adoption. Measures whether people opened the tool, not whether the work got better. You already have that number. It's why you're reading this.

Maximise seat usage. Makes usage the goal, so you get usage. You're left with a higher bill and more output to check, produced by people who were told volume was the point.

Prompt engineering. Teaches people to hoard prompts, search for the perfect formulation for each problem, rather than when to hand work to AI, and how to tell whether what came back is any good.

That gap has a cost, and it lands on whoever receives the work. Stanford and BetterUp Labs named it workslop: work that looks finished and isn't, passed to a colleague who then spends close to two hours repairing it. Around two in five workers reported receiving some within a single month. The productivity doesn't disappear. It moves downstream, onto someone with no budget line for it, and it takes trust with it.

There's a longer reason underneath, and it predates AI by about twenty years.

Judgement was designed out of most organisations on purpose. Process was standardised. Oversight was added. Innovative behaviour was replaced with innovation frameworks. It was a rational trade at the time: distributed judgement is expensive to coordinate, and standardisation is cheap.

AI is what makes the bill arrive. You can't ask people to exercise discernment over machine output if the last two decades were spent designing the discernment out.

Capability — in the people. Not prompt technique. The choice before the prompt. There are three relationships you can have with these systems: as a tool, as a teacher, as a sparring partner. Almost everyone uses one of them for everything without noticing they chose. Learning to pick deliberately, step by step, is the capability. It survives the next model release, which prompt formulas don't.

Conditions — in the organisation. Making it safe to say what's actually happening. Deciding where a person stays in the loop, and being able to say why. Redesigning the handful of workflows that matter, with the people who do that work rather than for them.

Some of this looks like slowing down, and it is. Skipping the critical thinking is not faster. It moves the cost to whoever receives the work.

Adoption counts, licence usage and engagement scores describe activity. They don't show whether anybody changed how they work in a way that connects to an outcome. That's why the ROI question from finance is so hard to answer.

My MSc research produced a measurement instrument for AI adoption, designed to find what usage data structurally cannot. Where adoption is real. Where it's being performed. Where it's stalled, and why. And what people won't say in a meeting.

You get a baseline you can put in front of a board, and a second reading later that shows movement.

When this is working, what you hear back doesn't sound like a productivity metric. It sounds like something returned.

If the sentence is a quantity, it's the wrong measure. If it's something somebody got back, it's the right one.

You need something small enough that whoever holds the budget can say yes without a business case, and concrete enough that they can see what they are getting. That is what phase one is for.

It is also built to be forwarded: a baseline and a readout in your board's language, priced to sit inside a departmental budget rather than trigger a procurement process.

• A measured baseline of where AI adoption actually stands
• A readout for your board, with the gap costed
• A weekly working session with your team, and support in between
• One or two workflows redesigned with the people who run them

At the end you have evidence, a plan your sponsor has seen, and enough internal capability to keep going.

After that it continues in 90-day sprints, or it stops. No minimum beyond the first ninety days, and no renewal you have to be talked out of.

I work with only two organisations at a time. This way I can focus on adding real value and embedding the learnings in your team.

For twenty years I was the supplier. Brought in to run the training, deliver the system, hand over whatever had been signed off. It is the best seat in the house for watching an organisation pay for something and then fail to absorb it. Six onboarding calls. An invite list that keeps growing. People showing each other that they care by asking stupid questions. And then nobody feels safe to engage with the actual subject matter.

I have also been in the rooms where the penny drops and a team unlocks a way of working it keeps. So I know what makes adoption fail, and I know what makes it stick.

Behind that: an MSc in organisational psychology, an AI-adoption measurement instrument built from original research, and a continuing set of interviews with people doing this work inside real organisations. Some of the quotes on this page come from those.