Five Studies Explained Why AI Fails. None of Them Asked This.

Five Studies Explained Why AI Fails. None of Them Asked This. 

Several recent studies have explained why AI fails. All of them blamed the wrong thing, and the cost of that misdiagnosis isn't staying confined to data quality. It's already showing up in what companies pay to borrow.

Citi found that companies seen as spending heavily on AI without being able to prove it's paying off now pay roughly a third of a percentage point more in interest than companies seen as building AI that actually delivers. That's not a survey result or an analyst's opinion. It's a real cost, set by banks, based on whether a company's AI spending is working. The failure isn't just something researchers are writing about anymore. It's showing up in what it costs a company to run.

In the last eighteen months, five major studies have each taken their own swing at why AI isn't delivering. Put them side by side and something strange shows up: they all measured the same collapse, they all pointed at data, and not one of them checked the thing that actually explains it.

The scoreboard

MIT NANDA (2025)

• What it found: 95% of generative AI pilots produce zero measurable P&L impact

• What it blamed: Missing validation and governance infrastructure to make AI output production-ready

Gartner (2024–2025)

• What it found: 30%+ of GenAI projects abandoned after proof of concept

• What it blamed: Poor data quality, inadequate risk controls, escalating costs, unclear business value

RAND Corporation

• What it found: 80%+ of AI projects fail — twice the rate of non-AI IT projects

• What it blamed: Fragmented data across disconnected systems, inconsistent metric definitions between departments, gaps in historical data, weak governance

McKinsey (2025)

• What it found: 88% of organizations use AI somewhere; only 39% report enterprise financial impact

• What it blamed: Framed as a measurement gap between individual productivity wins and organizational outcomes

S&P Global (2025)

• What it found: 42% of companies abandoned most of their AI initiatives, up from 17% the year before

• What it blamed: Cost overruns, data privacy and security concerns, inability to move pilots into production

‍

Five different research shops, five different survey methods, five different vocabularies for the same failure. And every single one of them, when you look closely, is measuring data quality inside a system — is it complete, is it governed, is it current, is it clean — rather than agreement between systems.

That's the test nobody ran: whether the "customer" your CRM is scoring is the same "customer" your billing system is invoicing and the same "customer" your product usage data is tracking. None of these studies checked that, because none of their survey instruments were built to. You can't ask a data leader "is your data governed" and get an answer that reveals whether three of their systems are quietly disagreeing about what an entity even is. That failure mode doesn't show up on a quality audit. It shows up as an AI system that's confidently, invisibly wrong.

Why the studies keep missing it

A quality audit checks a dataset against itself. Are the fields populated, are the formats valid, are the values current. A system can score perfectly on every one of those dimensions and still be feeding an AI model a version of "Acme Corp" that has nothing to do with the "Acme Corporation, Inc." three systems over. Both records can be complete, accurate, and well-maintained. The disagreement between them is invisible to any tool that looks at one system at a time — which is exactly how Gartner, RAND, and the rest are set up to look.

That's not a criticism of the research. The instrument matches the century-old assumption that data problems live inside databases. It's why "clean your data" has been the reflexive advice for two decades and it's why that advice keeps producing companies with technically clean, individually governed, mutually contradictory systems — and AI initiatives that fail anyway, for reasons the audit that passed them can't explain.

The data normalization test nobody ran

If you want to know whether this is your problem, don't run another data quality audit. Pull the same entity — a customer, a product, an account — from three systems that all claim to have accurate, complete, current data on it. Now check whether all three would identify it as the same thing. Not whether the fields are populated. Whether the fields agree.

Most companies have never run that test, because nothing in the standard data governance playbook asks for it. It's not on the RAND checklist. It's not on the Gartner risk framework. The discipline that actually covers it has a name — data normalization, the practice of reconciling how different systems represent the same entity so "Acme Corp" and "Acme Corporation, Inc." resolve to one record instead of two — and it's a different discipline from data quality, even though most governance programs treat them as the same line item. It's the specific gap in the exact type of infrastructure everyone in this scoreboard is diagnosing around, without naming.

The credit market isn't waiting for anyone to name it. It's already pricing the gap between companies that can prove their AI works and companies that can't — and the studies explaining the difference keep measuring the wrong layer to find out why.

Curious what data normalization can do? Book a demo and see Narrative run inside your own environment.