What it looks like
There is a folder somewhere with three impressive demos in it. Each one had a moment: the all-hands where it summarised a contract in seconds, the workshop where the room went quiet. Each one then entered an afterlife of security review, workflow questions nobody owned, and a sponsor who moved on. Nothing was cancelled. Nothing shipped. The board has started asking what the AI spend produced, and the honest answer is a folder of demos.
What is actually happening
A pilot answers the question “can the model do the task?” Production answers a different question: “can the organisation absorb the task being done differently?” Most stalled rollouts confused the first question for the second.
The places pilots die are rarely technical. They die at verification (who checks the output, and is that cheaper than doing the work?), at workflow joins (the AI does step three brilliantly but steps two and four still assume a human), and at accountability (when it is wrong, whose name is on it?). None of these appear in a demo, which is precisely why demos succeed and rollouts stall.
Meanwhile your best engineers are using AI heavily as individuals, which proves the capability exists and makes the organisational stall look even more like a mystery. It is not a mystery. It is an operating model that was never redesigned to receive the capability.
The intervention shape
Stop piloting. Pick one workflow that matters, trace where the last pilot actually died, and fix that join: the verification step, the handoff, the accountability. One workflow genuinely absorbing AI end to end teaches the organisation more than ten demos, and it produces the board answer you are currently missing.