Data readiness
Why 95% of AI pilots return nothing
Ninety five percent of generative AI pilots return nothing. The technology is not the problem. The discipline around it is.
Most AI pilots do not fail because the technology does not work. They fail because the organisation was not ready to use it. The pilot becomes a showpiece. Everyone nods. Nobody scales it. Six months later, the same pilot appears in a different slide deck with a different colour scheme and the same nothing at the end of it. This guide explains why, what the research says, and what boards should do instead.
The number no one wants to talk about
"About 95% of organisations in the study saw no measurable return from their generative AI initiatives."
Source: MIT Project NANDA, The GenAI Divide: State of AI in Business 2025 (preliminary findings, not peer-reviewed), nanda.media.mit.eduNinety five percent. That is not a typo, and it is not an outlier. It is the consistent finding across multiple studies. The technology works. The organisations running the pilots are not ready to turn a working experiment into a working system. The gap between the two is not technical. It is organisational.
I have seen this pattern play out more times than I can count. A team runs a pilot. The pilot shows promise. The team presents the results. The board approves the next phase. And then nothing happens. Not because the results were bad. Because nobody planned for what comes after the experiment.
The gap between a pilot and a product
A pilot is a controlled experiment. A product is a system that runs in the real world, with real data, real users, and real consequences. The distance between the two is enormous, and most organisations do not recognise it until they are already halfway across.
"Ninety percent of companies have launched some flavor of digital transformation, and only a third of the expected revenue benefits, on average, have been realized."
Source: McKinsey, Rewired to OutcompeteTwo thirds of AI transformations do not deliver. Not because the companies lacked ambition. Because they treated a transformation like a technology project instead of an organisational one. The technology was ready. The business was not.
The three things that separate a pilot from something real are data, governance, and people. The pilot can work around data problems because a human is watching it. The real system cannot. The pilot does not need governance because it is small and contained. The real system does. The pilot can run on the enthusiasm of one team. The real system needs everyone else to change how they work.
The data problem nobody checks first
This is the one I see most often. The pilot uses a curated dataset. Someone cleaned it, selected it, and made sure it was right. The real system uses the actual data, which is messy, incomplete, and spread across systems that were not designed to talk to each other.
"63% of enterprises lack AI-ready data or are unsure."
Source: Gartner via Microsoft, Adoption PatternsNearly two thirds of organisations either know their data is not ready or do not know whether it is. The pilot hides this problem because it operates in a bubble. The real system exposes it immediately. The lesson is simple: test the data before you test the technology. Fuzzelogic's five tests for AI-ready data are a starting point. Reachable, trustworthy, explainable, changeable, governed. If your data cannot pass those five, the pilot is theatre.
The governance gap
Governance is not a checkbox. It is the set of rules that decides what the system may do, who is accountable when it goes wrong, and how the organisation responds. Without it, every pilot is a liability waiting to become a headline.
"21% of organisations have no AI governance at all, and governance and risk is the fastest growing barrier to adoption."
Source: Deloitte, State of AI in the EnterpriseOne in five organisations has no governance. That means one in five organisations has no answer to the question "who is responsible when this makes a mistake?" For a board, that is not a gap. It is a risk that sits on your desk whether you acknowledge it or not.
The pilot does not need governance because it is small. The real system does. If you do not build governance into the pilot from the start, you are not building a foundation. You are building a delay.
The people problem
The third failure point is the one that gets the least attention. The pilot runs on a small team that understands the technology, cares about the problem, and has the authority to experiment. The real system runs on people who did not choose it, do not understand it, and have no incentive to change how they work.
I have sat in rooms where the pilot team presented brilliant results and the rest of the business looked at them like they were speaking a different language. They were. The pilot succeeded because the right people were in the room. The real system fails because the right people are not.
"$18 trillion of trapped value blocking AI."
Source: Genpact/HFS, How Four Enterprise Debts Will Make or Break Your AI FutureEighteen trillion dollars of value is locked inside organisations that cannot use it. Not because the value is not there. Because the people, processes, and systems around it were not built to let it out. The pilot does not solve this. The assessment does.
What boards should do instead
Stop approving pilots. Start approving readiness. Before any AI project gets a budget, the board should ask three questions. First, has someone tested the data? Not the technology. The data. Second, has someone named the owner? Not a committee. A person. Third, has someone defined what failure looks like and what the off switch is?
If the answer to any of those is no, the pilot is not ready. It is a science experiment with a corporate budget.
"About 7% of organisations have scaled AI across the enterprise; two thirds of high performers say data is the primary obstacle."
Source: McKinsey, AI Data Readiness: The Key to Scaling ImpactSeven percent. That is the number of organisations that have scaled AI. The other ninety three percent are stuck. The ones that got past it did not start with the technology. They started with the data.
The honest answer
You already have AI in your business. You just do not know where. The question is not whether you can pilot something. The question is whether you can scale it. Most of the time, the honest answer is that the organisation is not ready yet, and the most valuable thing you can do is find out why before you spend another budget cycle on a pilot that goes nowhere.
If the honest answer is that AI should not touch a process, we put it in writing rather than build it anyway. That is what an assessment is for. Not to sell you something. To tell you the truth.
Start with the assessment. Two to four weeks, fixed price, and you own the verdict and the roadmap whether or not we build any of it. When you are ready to talk AI, call Fuzzelogic Solutions and ask for Zak. www.FuzzelogicSolutions.com | info@FuzzelogicSolutions.com | +44 (0)1624 618950
Download the free guide The Boring AI Fix to see the five questions every board should ask and the ten-point scorecard that tells you where you stand.
For more on what good data looks like, read AI-ready data: the five tests. For the full assessment process, read data readiness assessment: how to assess data for AI. The full library is on our index. Our site explains how Fuzzelogic approaches AI for business.
Start with the assessment
Two to four weeks, fixed price, and you own the verdict and the roadmap whether or not we build any of it.
When you are ready to talk AI, call Fuzzelogic Solutions and ask for Zak.
www.FuzzelogicSolutions.com | info@FuzzelogicSolutions.com | +44 (0)1624 618950