AI Didn't Create the Gap. It Removed the Slack.

There is a failure pattern that has become familiar enough to name. An organisation runs an AI initiative. Readiness is assessed and passed: the data is adequate, a sponsor is in place, the committee is constituted, the vendor is selected. Deployment begins. The early demos look good. Then, somewhere between twelve and eighteen months in, the system is quietly paused for review, and some months after that it is withdrawn. There is rarely a public moment of failure. The initiative simply stops mattering.

The usual explanations are adoption, change management, data quality, or the vendor. Sometimes one of those is the real cause. More often, none of them is, and the initiative was lost long before deployment, not in the model, but in the structure around it.

This is worth stating plainly, because it is not really a claim about AI. Organisations have always struggled to convert what they know into what they do. They accumulate knowledge, form intentions, exercise judgement, and receive feedback, and then fail to turn any of it into coherent, coordinated action. The knowledge is real. The intent is real. The capability is often real. What breaks is the translation.

We tend to misdiagnose that break. We call it a capability problem and hire for skills. We call it a leadership problem and change the people at the top. We call it a process problem and redraw the workflow. We call it a culture problem, which is usually where diagnosis goes to die. Sometimes these are right. But often the deeper issue is that the organisation's way of knowing, deciding, authorising, acting, verifying, and adapting has fallen out of coherence with itself. The parts no longer line up. Information arrives somewhere that has no authority to act on it. Authority sits with someone who cannot see the information. Accountability is assigned to a role that has lost the levers to deliver it. Each part works. The system does not.

It would be dishonest to present any of this as new. Twenty-five years ago Pfeffer and Sutton called it the knowing-doing gap: the well-documented distance between what organisations know and what they actually do about it. Stafford Beer, working in organisational dynamics, modelled the firm as a system that has to sense its environment, decide, act, and adapt as a coherent whole, and showed what happens when one of those functions is starved or severed. Karl Weick spent a career on how organisations make sense of their world, and how that sensemaking quietly breaks. The gap has been named, modelled, and studied for decades.

What has been hard is not naming the gap. It is seeing it inside a specific organisation: locating it, measuring it, and pointing to the exact place where knowing stops becoming doing. The problem has been legible in theory and invisible in practice. You could believe in it completely and still not be able to show a sponsor where, in their organisation, it was costing them.

There is also a reason the gap could stay invisible for so long without the organisation falling over: slack. Human-speed decision-making is full of slack, and the slack does useful work. The senior person who "just knows" and quietly overrides the formal process. The handoff that no one can technically enforce but that happens anyway because two people have worked together for years. The workaround that keeps the real process running while the documented one stays on the wall. The week a decision sits in someone's inbox before it is actioned, which turns out to be exactly enough time for a problem to surface and get caught.

These are not signs of a healthy structure. They are compensations for an unhealthy one. But they are effective compensations, and they share a property: they all run at human speed. As long as the whole system moved at the pace of meetings, inboxes, and informal conversations, the slack absorbed the incoherence. The gap between what the organisation knew and what it could do was real, but it was padded on every side, and the padding held.

This is what AI changes, and it is the part the standard narrative misses. AI does not simply add another tool to the stack. It accelerates one part of the decision system, the generation of recommendations and answers, while leaving the surrounding human architecture untouched. Recommendations now move faster than authority can ratify them. Information moves faster than accountability can keep up with. Models produce answers faster than the organisation can test whether those answers are usable, legitimate, or safe to act on.

The slack does not survive this. The padding that depended on human speed is squeezed out. The senior override that used to be an occasional, invisible smoothing becomes a constant, conspicuous bottleneck. The handoff that worked because two people trusted each other cannot scale to the volume the AI generates. The week of useful delay becomes a queue that backs up faster than anyone can clear it. The compensations stop compensating, and the structural problem they were hiding becomes load-bearing and visible for the first time.

Take a single decision in a professional services firm: pricing approval. Before AI, a handful of lower-margin fee approvals cross a managing partner's desk each week. The partner glances at each, asks a question or two, and waves most through. That glance is doing quiet work. It catches the engagement being discounted to drag a number over the line at financial year-end, the client who is already unprofitable to serve, the rate concession that will set an expensive precedent across the portfolio. The day or so the approval sits in the queue is not waste. It is where the judgement happens.

Now an AI tool prices every quote in real time, and the prices are good, sharper than the team's instinct. But every non-standard price still routes to the same partner. There are no longer five approvals a week; there are fifty. The partner has two options, and both break something. Approve them without reading, and the sign-off becomes nominal: the judgement that used to catch the bad deals is gone, and nobody notices until the engagement finishes underwater. Or actually read them, and the queue backs up: quotes go stale, the team starts defaulting to standard rates to dodge the wait, or routes around the partner to whoever will say yes fastest. The careful pricing the AI produced never reaches the client at the speed it was built to move at.

Nothing in the model failed. What failed is that the approval step was built for human-speed deal flow, and the judgement inside it depended on the volume staying low enough for one person to actually think. The structure underneath: a single partner as the one place a price gets ratified, was never designed to run at the speed the AI now runs at. The slack in that step was load-bearing. The AI took it out.

This is the shape of almost every stalled initiative. It breaks around the AI, so the AI takes the blame the platform is declared "not working," at the worst possible moment, after the spend and in front of the sponsor. But the platform is working. What it removed was the slack that had kept an existing structural problem out of sight.

This reframes the risk. It is not principally that the model underperforms; the models are mostly good enough. The risk is that the organisation cannot absorb what a good model produces. It cannot decide at the speed the model recommends. It cannot route the outputs to people with the authority to act on them. It cannot keep accountability attached to anyone who still has the means to change the outcome. That is not a problem you fix by improving the model, retraining staff, or replacing the vendor. Those are all interventions at the wrong layer. The problem is in the decision architecture, and it will quietly defeat the next AI initiative, and the one after that, until the architecture changes.

This is a claim worth bounding, because the opposite error is just as easy to make. Not every stalled initiative is structural. Some models genuinely underperform. Some vendors oversold what they shipped. Some organisations simply lack the capability to run what they bought. The argument is not that structure explains everything. It is that structure is the explanation most often skipped because it is the one no dashboard reports and no vendor is incentivised to raise. Rule the obvious causes in or out first. Then look hard at the structure still standing when they are gone.

Underneath the slack argument is a separation that is easy to miss. For most of organisational history, knowing and deciding sat close together. The person with the relevant knowledge usually held the authority to act on it, or sat near someone who did, and both moved at roughly the same speed. That coupling is coming apart. The knowing is increasingly done by a model. So is the recommending. The authorising still sits with a human, often several steps removed. The accountability sits with someone else again. Four things that used to travel together: knowing, recommending, authorising, and answering for the outcome are being pulled to different places, moving at different speeds, held by different parties.

This is why an org chart cannot show you the problem. It assumes those four are joined, or close enough not to matter. Once they separate, the only way to see the gap is to map authority and accountability as two distinct layers and look at where they fail to meet.

That is no longer something you can only believe in; it can be drawn. Map the organisation as a graph; the roles, and the two kinds of connection the org chart collapses into one: who holds authority over a decision, and who is accountable for its outcome. Drawn as separate layers, the places where they have come apart stop being a matter of opinion. An authority with no accountability beneath it; an accountability with no authority attached; a recommendation path that terminates at someone who cannot act; a feedback loop that never reaches anyone who can change a thing these show up as structure, not anecdote. They can be scanned for, repeatably, confirmed against operating evidence, and put in front of a sponsor in plain terms.

That is the difference between knowing the gap exists, which we have known for twenty-five years, and being able to show a particular organisation where its gap is, what it is costing, and what to change before the next initiative runs into it.

There is a another trap on the other side of visibility. Organisations tend to assume that seeing a problem clearly is most of the work of fixing it. It rarely is. Clearer sight usually does the opposite first: it exposes how much was being held together informally, and how much deliberate work it will take to hold together on purpose. This is an old pattern, not a new one. Each time a society has sharply increased what it can know through measurement, through records, through science it has been forced to build new machinery to act on the new knowledge, and the machinery has always lagged the knowing. The discovery is the easy part. The institutions that make a discovery usable arrive later, slowly, and at cost.

That cost is the part the AI conversation skips. Coherence is not free, and the reason organisations live with incoherence is that the alternative is expensive. Every increase in what an institution can perceive and recommend demands a matching increase in what it can decide, authorise, and act on. When the sensing side races ahead and the responding side stays where it was, the surplus is not intelligence, it is noise the organisation cannot use. AI is a very large, very sudden increase on the sensing side. The matching investment on the responding side has not been made in most organisations, and in most it has not even been costed.

For most of the history of management, the gap between what an organisation knew and what it could do was a tolerable inefficiency, padded by slack and survivable. AI removes the padding. The organisations that come through this period well will not be the ones with the best models, those are increasingly available to everyone. They will be the ones whose structure can absorb what the models produce: that can decide as fast as they can recommend, route as fast as they can generate, and keep accountability attached to someone who can still act.

The constraint has moved. The hard part used to be generating intelligence: knowing enough, fast enough, to act well. The models now do that, and they do it for everyone. The hard part now is metabolising it: turning what the organisation can suddenly know into something it can actually decide and do. Institutional intelligence has raced ahead; institutional authority and institutional action have not kept up. The cost of the distance between them used to be hidden. It isn't anymore. The work now is to make that distance visible, and then to pay for closing it, before it is made visible for you.

I help organisations where important decisions are being made but execution isn't moving. If this is you then get in touch.