Most AI projects do not deliver the value their business case promised. Two serious studies name the causes, and neither one blames the model. RAND finds that the root causes are organisational. The National Audit Office finds that legacy systems and data sharing limit what UK government can do. A third study measures the specific defect that both describe, and that defect survives after you fix the others.
Connect with us about your data foundation · · Replies within 24 hours
They fail for organisational reasons far more often than technical ones. RAND studied this directly and published The Root Causes of Failure for Artificial Intelligence Projects, and it names five root causes.
One figure from that work matters more than the list. Within RAND's sample, 84% of industry interviewees named leadership-driven issues as the primary cause of failure. The failure therefore sits above the engineering rather than inside it.
The National Audit Office examined the use of artificial intelligence in government. It found 70% of respondents piloting or planning AI use cases, with adoption not yet widespread.
It named two obstacles: legacy systems, and data access and sharing. It also warned that value for money is at risk when no department owns the AI strategy.
Those obstacles match the RAND list. Cause two is missing data and cause four is inadequate infrastructure. The NAO describes both in a UK public-sector setting, and it adds a third condition. The data exists, and it cannot move between systems.
The failure appears at the end of the project. A team spends months on procurement, data access and integration, and the model arrives last. It then produces a wrong answer and takes the blame for everything upstream.
The Office for National Statistics shows the gap in outcomes. Its 2023 to 2026 series puts UK SME adoption at 54% in 2026, up from 35% the year before, with only 12% of those users reporting higher revenue. Adoption is therefore not the constraint.
Remove the causes that effort can fix. Suppose your leaders engage with the work, you choose the problem well, the data exists, and the technology can do the task. One defect still remains, and researchers have measured it.
Your database stores the structure of your data, and it does not store the meaning, so a model must invent the business rules that nobody recorded.
A 2026 benchmark tested that directly. Three frontier models answered 99 business questions on a public dataset, twice each, and the second run added a short document describing the measures and the conventions.
| Model | Schema only | Schema and meaning | Change |
|---|---|---|---|
| Claude Opus 4.7 | 50.5% | 67.7% | +17.2 points |
| Claude Sonnet 4.6 | 46.5% | 68.7% | +22.2 points |
| GPT-5.4 | 45.5% | 68.7% | +23.2 points |
With the document present, the three models became statistically indistinguishable from each other. Without it, they also became indistinguishable.
We give the full evidence in why AI gets your own business data wrong.
A recent paper argues that it is not, and its title says so. Why AI Readiness Is an Organizational Learning Problem, Not a Technology Purchase.
That framing matches the RAND finding about leadership, and it explains why buying a platform rarely fixes the problem on its own. A platform can hold a discipline, and it cannot supply the decision to adopt one.
The useful question therefore changes. Not which tool to buy, but which of these failures your architecture makes impossible.
| Root cause | Removable by architecture? | Reason |
|---|---|---|
| The wrong problem | No | A human decision. Only better scoping fixes it. |
| Missing data | Partly | Architecture cannot create data, and it can stop a silo trapping it. |
| Technology before the user | No | A cultural failure. |
| Inadequate infrastructure | Yes | This is the definition of an architectural problem. |
| Too hard for AI | No | A limit of the technology. |
| Meaning not recorded | Yes | A declared vocabulary makes the omission impossible. |
Two of six is an honest answer, and it still separates a project that can succeed from one that cannot.
We build your system on engage.re, and four of its properties bear directly on the failures above.
Sense Future built engage.re, and it has run in production since December 2025.
Ask four questions of your last project, and each answer points at a different cause.
The cost lands in three places, and only the first appears in a post-mortem.
The direct spend covers procurement, licences, integration work and staff time. You know that figure, and of the three it stays the smallest.
The opportunity cost is larger. A team spent twelve months on a pilot that produced nothing, and those months did not go into the service. No invoice records that cost.
The confidence cost lasts longest. A failed pilot teaches an organisation that AI does not work for its problem, and the next proposal then meets a board that has already decided. Where the data could not move between systems, the organisation has learned the wrong lesson from a real event.
A council runs an AI pilot in adult social care, and the pilot needs data from housing, revenues and the care record. Each source sits behind a different supplier, a different permission model and a different definition of a person. Twelve months later the pilot reports that the data was not available, and nobody records that as an architecture failure.
A care home group runs the same pilot across a records system, a rota tool and a family portal. Three systems instead of thirty, and the same three obstacles. The manager concludes that AI does not work for care, and the obstacle was the estate.
The care home software and school software pages set out the sector detail. Our guides to CQC digital records and charity data management describe the same problem inside a single sector.
For organisational reasons more often than technical ones. RAND names five root causes: the wrong problem, missing data, technology chosen before the user, inadequate infrastructure, and a task too hard for AI. Within its sample, 84% of industry interviewees named leadership-driven issues as the primary cause, so the failure sits above the engineering rather than inside it.
The National Audit Office names two obstacles: legacy systems, and data access and sharing. It found 70% of respondents piloting or planning AI use cases, with adoption not yet widespread. It also warned that value for money is at risk where no department owns the AI strategy.
The data. A 2026 benchmark ran three frontier models over the same questions, with and without a description of what the data means. Accuracy rose 17 to 23 points with the description, and the three models then became statistically indistinguishable from each other. The description accounted for nearly all the variance.
It prevents two of the six causes. It removes inadequate infrastructure, and it makes undeclared meaning impossible. It cannot fix the wrong problem, a culture that chases tools, or a task beyond the technology. That answer is partial, and it still separates a project that can succeed from one that cannot.
Record what your data means, and name an owner. A team that has recorded its conventions can choose a model on cost and speed, and a team that has not cannot recover the gap with a larger model.
We build your system on engage.re. Your meaning is declared before your data exists, no silo can trap your data, one identity model and one gate cover your whole estate, and your system does not become the legacy the NAO describes.
Connect with us about your data foundation · · Replies within 24 hours