Where Value Dies
A five-minute diagnostic you can run on any AI initiative tonight. The result will explain why the pilot that "worked" has not produced a dollar of measurable value.
The first two editions of this publication were about the foundation: most enterprises sit at Level 3 of data maturity and believe they are at Level 5, and most enterprises are accounting for AI as software when the asset they are actually building is capital. Each of those is a frame. Neither is, on its own, an instrument.
This edition is about an instrument.
There is a pattern I keep encountering inside AI programs that look healthy from the outside. The pilots are running. The models are accurate. The vendors are delivering against statements of work. The dashboards show green. And yet, when the CFO asks how much of the original business case has actually shown up in the P&L, the answer is some version of not yet, but soon, and here is what we are learning.
It has been not yet, but soon for eighteen months in some of these programs.
The technical posture of the program is fine. The economics of the program is not. And the gap between the two is rarely a model problem or a vendor problem or a data problem in the way those problems are usually framed. It is a chain problem.
Every AI initiative that is supposed to produce business value moves through five links. The model surfaces something — insight. A human or another system understands what it means — interpretation. Someone is accountable for acting on it — ownership. The action is taken — action. The result is measured against the original promise — verification.
When any one of the five breaks, the value disappears. The model can be excellent. The data can be clean. The interface can be elegant. None of that matters if the chain breaks.
In most enterprise AI programs that look successful but are not yet financially real, the chain has broken in a specific place. And once you know where to look, you can usually find the break in about five minutes per initiative.
The five links, briefly
Link 1 — Insight. The model identifies a pattern, anomaly, prediction, recommendation, or generated output. This is the link most AI teams obsess over and the one that is rarely the actual problem. Modern models are good at producing insight. That is not the bottleneck.
Link 2 — Interpretation. Someone — a human, a workflow, another system — understands what the insight means in the context of the business. A churn-risk score is not interpretation; it is data. The interpretation is what that score means for this specific customer in this specific quarter under this specific commercial relationship. Interpretation breaks when the insight arrives without the context required to act on it.
Link 3 — Ownership. Someone is accountable for doing something about the insight. Not “the team” is accountable. A specific role with a specific name. Ownership is the link where most AI initiatives die, and the reason is structural rather than personal: AI surfaces work that does not fit cleanly into any existing function, and unless someone has been deliberately chartered to absorb that work, it falls through the gap between roles.
Link 4 — Action. The accountable owner takes the action the insight suggested. This sounds trivial; it often is not. The action may require a system the owner does not control, an approval the owner does not have, or a workflow change the organization has not yet authorized.
Link 5 — Verification. Someone measures whether the action produced the value that was originally promised, and feeds that measurement back to the program. Without verification, the chain runs forever without learning. Pilots become permanent. The business case never closes.
A working chain delivers value. A broken chain delivers activity. Most enterprise AI programs are running on broken chains and reporting activity as if it were value.
Where the chain actually breaks
After running this diagnostic on enough programs to see the pattern, the breakage is rarely distributed evenly across the five links. It clusters at Link 3 — ownership — and the clustering is structural enough that it is worth naming.
Consider the typical setup. An AI program identifies that 12% of the customer base shows elevated churn risk over the next ninety days. The model is accurate; the data is clean; the dashboards render correctly. Insight is intact. Interpretation is intact — the score is contextualized by segment, by tenure, by recent service events. The first two links are working.
Now the question: who is responsible for doing something about it?
If the answer is “customer success,” that is not an answer. Customer success has fifteen other priorities and no specific commitment to engage twelve percent of the base in the next ninety days. If the answer is “the retention team,” that may be an answer — if a retention team exists, has capacity, and has been told this is now part of their workload. Often none of those is true.
What happens, in practice, is that the insight gets reported to a steering committee, the steering committee acknowledges the insight, and the insight becomes information rather than action. The chain has not broken at the model. It has broken at the question of who owns the work the model surfaced.
This is the pattern I have started calling Pilot Purgatory — the failure mode where AI initiatives appear to succeed (the pilot performs, the demo lands, the steering committee approves) but never cross into the P&L. Pilot Purgatory is almost always a Link 3 problem. The insight is real. The interpretation is real. No one owns the action.
The reason Link 3 is the most common breakage point deserves examination. AI surfaces work that did not previously exist in the organization. It identifies risks that were not previously visible, opportunities that were not previously tractable, and exceptions that were not previously caught. That new work has to go somewhere. In a well-designed AI operating model, the new work is deliberately routed to a specific role with the authority, capacity, and incentive to absorb it. In most organizations, the routing has not been designed. The new work falls into the gaps between functions, where it dies quietly.
Link 4 — action — fails less often, but when it does, the failure is usually about system or authority constraints. The owner has been named, accepts the work, and then discovers they cannot actually execute because the relevant system does not allow it, the relevant approval requires three other signatures, or the workflow change has not been authorized at the level required to make it stick. Link 4 problems are real but solvable; Link 3 problems require organizational design.
Link 5 — verification — fails most often by omission. Nobody ever circles back to measure whether the action produced the value. The pilot is declared successful because it produced insights; whether those insights produced dollars is left unmeasured. A program without verification cannot learn, which means it cannot improve, which means it cannot mature into a capital asset. It stays an activity layer indefinitely.
How to run the diagnostic
The 5-Link Chain is not a framework that requires training to apply. It is an instrument you can run on any AI initiative in five minutes. The procedure:
Pick one specific initiative — not a portfolio, one initiative. Ideally the one whose business case is most prominently cited in board materials.
Trace it through the five links. At each link, ask two questions. First: is this link intact? Second: if it is intact, who specifically is responsible for it, and how do I know?
The answers will pattern very quickly. Links 1 and 2 will almost always come back intact, because that is where the technical work has been done. Link 3 will almost always be where the answer becomes vague — “the team is on it,” “we are still working out roles,” “the steering committee has it.” Link 4 may be intact if Link 3 is intact, but will reveal authority constraints if you press. Link 5 is usually missing entirely.
The diagnostic does not require sophistication. It requires honesty. Most leaders, asked to trace one initiative through five links, will identify the breakage within a few minutes. The reason the diagnostic is rarely run is not that it is hard. It is that running it surfaces gaps that the program’s reporting cadence is currently smoothing over.
What the diagnostic produces
When the chain is intact, you have an AI initiative that is producing measurable value and accumulating into the capital base from the last edition. The diagnostic confirms what is working and identifies which other initiatives to model on it.
When the chain is broken — and most chains are broken at Link 3 — the diagnostic produces something more valuable than a fix. It produces a precise statement of what is wrong, in language the organization can act on. “This initiative dies at ownership” is a more actionable diagnosis than “the AI program is underperforming.” The first names a specific gap that a specific role can be assigned to. The second names a feeling that produces no action.
This is the difference between an instrument and a frame. A frame helps you think. An instrument helps you see. The 5-Link Chain is an instrument, and like all instruments, it earns its keep by surfacing what was previously invisible.
A program that runs the diagnostic on its top five initiatives, honestly, will usually find that three of the five are stuck at Link 3, one is stuck at Link 5 (running without verification), and one is actually working. The working one is the one to study. The three stuck at Link 3 need owners. The one stuck at Link 5 needs a verification cadence. None of those interventions require new technology. All of them require operating discipline.
That, again, is the pattern. The AI programs that are creating value are not the ones with better models. They are the ones with intact chains.
The standard a leader should hold
Every AI initiative on the company’s active portfolio should have a named answer to all five link questions: who produces the insight, who interprets it, who owns the action, who executes, and who verifies. If any of the five has a vague answer or a missing one, the chain is broken and the initiative is producing activity rather than value.
The discipline is not annual. It is initiative-level. A portfolio of twelve AI initiatives requires twelve sets of five answers — sixty answers in total. Most programs cannot produce them. The ones that can are the ones whose AI is reaching the P&L.
The executive decision
Before the next AI program review, run the 5-Link Chain on the three initiatives most prominently featured in board materials. For each, name the role accountable at each of the five links. If three or more of the fifteen answers are vague, the program is reporting activity as value. The corrective is not more pilots. It is closing the chain on the initiatives already underway.
Board line
Insight, interpretation, ownership, action, verification. Most AI initiatives die at link three. Run the chain on your live pilots tonight.
Closing question
For your most important AI initiative — the one you would cite to the board next quarter — at which link does the chain actually break? And does anyone in the room know that yet?
Onward,
Raja
Raja Pabba is the founder of CloudMetrics and writes The CAIO Review on enterprise AI operating discipline. Subscribe at caioreview.com.