The Destination Is Well Described. Nobody Has Written the Path.
The agentic organization has been imagined, in detail, what builds it has not ● The failure is in the structure ● The AI-transformed enterprise can already be imagined. It has not yet been built.
There is no shortage of material telling a company what it will look like once it has successfully transformed itself with AI. McKinsey’s account of the “agentic organization” is among the more careful examples — a genuinely useful sketch of an enterprise where agents hold persistent context, workflows reconfigure themselves around outcomes rather than org charts, and human judgment concentrates at the points that actually require it. Reading it, a company could reasonably conclude it now understands where it needs to go. What it would not come away with is any account of how to get there. This is not a gap specific to one report. It shows up just as clearly in the execution of these transformation efforts themselves: companies with the destination-vocabulary fully absorbed, running initiatives named after it, with no actual description anywhere of the sequence that would get them from where they are to where the vocabulary points.
A picture of the finished state is checkable against itself: internally coherent, citable, safe to publish. A description of the path is a different kind of document. It has to survive contact with a specific company’s actual decisions: which process to touch first (a claims queue, a vendor-onboarding chain, a pricing desk), what evidence would tell you the redesign is working before the metrics catch up, what to do when the first attempt fails in a way the destination-picture gave no warning of.
That kind of material is much harder to produce in general, because it mostly stops being useful the moment it becomes general: specific to one company’s sequence, not portable to the next one. The destination genre is popular partly because it’s the one that scales.
This produces a specific and fairly common failure mode, and it’s worth being precise about what it is not. It is not a capability problem: most large organizations now have access to models more than adequate for the workflows they’re trying to redesign. It is not, mainly, a budget problem either. What’s missing is the actual path: a described, structured account of which operational problem to rebuild around first, in what order, and what would count as evidence the rebuild is working rather than merely running. Not a principle for sequencing — the sequence itself, written down, specific enough to act on and specific enough to be wrong.
Most corporate AI transformation efforts underway right now are running the shaft-and-belt version: installing agentic capability into workflows shaped by an organizational structure the capability was never designed to serve — approval chains, reporting layers, decision rights — and narrating the result in the destination-vocabulary the industry has supplied, without having actually rebuilt anything that vocabulary presupposes. Paul David’s account of the [electric dynamo gives this failure mode its most precise historical form. Factories electrified their power supply and got almost nothing for two generations, because they kept the shaft-and-belt architecture and only swapped the engine that turned it. The productivity gain from electrification arrived thirty to forty years later, once factories were redesigned around individually driven machines rather than a single central power source distributing motion through a mechanical network built for steam. The technology was ready decades before the organization was.
A story tells you what the finished enterprise will look like. A playbook tells you what to build first, why that and not something else, and how you’d know three months in whether you’d chosen correctly or merely activated something. Most of what currently passes for AI transformation strategy is a story with a project timeline stapled to the back. It has the shape of a plan. It answers when, not which, and never touches why this operational problem before that one, which is the only question a real path has to answer.
The corporations that get the electrification payoff early will be the ones that treat this as the actual design problem, rather than a rollout problem to be solved with change management and a longer runway. The AI-transformed enterprise can already be imagined. It has not yet been built one playbook page at a time.