A senior executive at a large enterprise recently described a capital allocation review to me. The committee had spent two hours deciding where the next tranche of maintenance capital should go. The discussion drew on last year’s budget, a regional presentation and the persuasive advocacy of a plant head who had been escalating the same request for three quarters.
Somewhere in that same organization sat a predictive model estimating failure risk across the asset base. It was reasonably good. A competent team had built it sometime earlier. Nobody in the room referred to it or mentioned it.
What bothered him was not that the model was wrong. It was not wrong. It wasn’t late, and it wasn’t hard to access. It simply had no relationship with the decision.
I have heard enough versions of that story to believe it describes the central problem in enterprise AI right now — and that we are consistently solving for the wrong thing.
AI adoption is no longer the constraint
Mckinsey’s The State of AI in 2026 makes the point clearly. Almost nine in ten organizations report regular AI use in at least one business function, and around 44% say AI is scaling across the enterprise. Eight in ten report higher individual productivity. Yet only about 37% attribute any positive enterprise-level EBIT impact to AI.
BCG’s survey of large-company CEOs found nearly nine in ten reporting cost or revenue benefits in targeted areas — while more than half cited a missing link between AI and P&L, and only 14% had clearly defined P&L impact across their AI initiatives. PwC’s 2026 CEO survey put it even more starkly: 12% of CEOs said AI had delivered both revenue gains and cost reductions.
Individual productivity is rising faster than enterprise performance. That gap cannot be explained by technology alone, and more tooling should not be the default response.
Part of the cause is how we frame AI in the first place. I ran an informal poll among my own network recently — not research, but directionally interesting — and 57% of respondents said automation and efficiency were the first things that came to mind when they heard the word “AI.” If that is the default mental model, then AI gets pointed at existing work to make it faster or cheaper. It rarely gets pointed at the question of what the enterprise ought to know and decide that it currently cannot.
I have argued before that generative AI is best understood as the use case that creates all other use cases — a foundation that expands what is possible across functions. That remains true. But a foundation only creates possibility. Something still has to direct it at the decisions that determine whether the business performs. That direction is what is usually missing.
Four different gaps behind the same AI problem
Here is the practical consequence. When a consequential decision is poorly supported, most organizations reach for the same answer: we need better AI. But a weakly supported decision can fail for at least four fundamentally different reasons, and only one of them is fixed by building more capability.
- The Capability Gap – The enterprise genuinely cannot produce the intelligence the decision requires. An executive need to know which assets are most likely to fail in the next 12 months, and the organization has no reliable condition data, no failure history, no model, no one who could build one. This is a real gap, and it needs real investment — data capture, models, skills, sometimes a new platform.
- The Design Gap – The capability exists, but it was not designed around the question being decided. The organization can predict asset failure. The executive’s decision is not simply which assets may fail. It is where to allocate a fixed capital budget — which requires the consequence of failure, safety exposure, repair-versus-replace economics and scenarios at different budget levels. Failure probability is an input to that decision. On its own, it is not an answer, and handing the executive an input and calling it intelligence is how analytics teams lose their credibility.
- The Delivery Gap – The right intelligence exists and is well designed, but it reaches the wrong person, at the wrong moment, or in the wrong form. A capex-risk analysis that arrives after the budget is closed is a record, not decision support. So is a complex dashboard when the executive actually needs a one-page recommendation before the investment meeting.
- The Connection Gap – This in my experience it is one of the most common, the least visible and potentially the most consequential. The intelligence exists, it is well designed, it arrives in time — and consulting it remains optional. The model is available. The investment committee still runs on historical budgets and advocacy. Nothing in the formal governance of that decision requires anyone to look.
Connection gaps are difficult precisely because nothing appears to be broken. Every component works. The data is sound, the model performs, the report is circulated. The failure is structural rather than technical: no one ever changed how the decision is made. And because there is no visible defect, the usual response is to improve the components — a better model, a richer dashboard, a wider rollout — which leaves the gap exactly where it was while consuming another budget cycle.
Closing a connection gap is usually an operating-model issue rather than a technology one. The intelligence must become part of the formal decision process — what goes into the committee pack, what evidence must be considered, and where human accountability for the final decision sits.
I use these four gaps as part of a broader framework I call Enterprise Intelligence Architecture (EIA). EIA starts with the decisions that materially determine enterprise performance and works backward to the intelligence those decisions require—then to the data, analytics, AI and governance needed to produce it. The objective is not to create another AI architecture. It is to connect what the enterprise can know to how the enterprise actually decides.
EIA is the enterprise expression of a broader Institutional Intelligence Architecture (IIA), which treats AI as cognitive infrastructure for improving how institutions perceive, understand and decide.
Why the diagnosis matters
In many mature enterprises, the highest-return gaps are not capability gaps. The data largely exists. The models often exist. The analytics team is competent. What is missing is design, delivery and connection — Many of those gaps can be addressed without another major platform investment. The harder work is often redesigning the intelligence, its delivery or its place in the decision process.
That can be good news. An organization may be able to improve how it decides using capabilities it has already paid for. It also changes the AI roadmap conversation — from what technology can be deployed to which decisions are consequential, recurring, information-constrained and improvable with what already exists.
A practical starting point
EIA does not need to begin as a large transformation programme. A useful starting point is one consequential, recurring decision where the organization may already know more than it currently uses. The question is whether the decision is constrained by missing capability, poorly designed intelligence, ineffective delivery, or a lack of connection to the formal decision process. Addressing that specific gap first allows the enterprise to improve decision quality using much of the capability it already has, and then extend the same approach progressively to other important decisions.
The question worth asking
Enterprise AI success should not be judged primarily by the number of pilots, copilots or models deployed. What matters is whether the organisation can repeatedly turn what it knows into better judgment at the decisions that matter.
That starts with a diagnosis, not a purchase. The question is not, “Where should we deploy AI?” It is, “What should this enterprise be able to know and decide better than it does today — and which of the four gaps is standing in the way?”
Answer that for one consequential decision, and the organisation may discover that the missing ingredient is not another AI tool. It is the connection between the intelligence it already has and the decisions that determine performance.