Skip to main content
Back to Resources
Industry Insights

What the MIT 95% AI Pilot Finding Actually Means

Andrew MeakinUpdated 5 min read
Framework for measuring an AI pilot against a business baseline

The MIT 95% AI pilot finding doesn't mean that 95% of every AI project fails. It refers to a preliminary 2025 Project NANDA report that found most enterprise generative AI initiatives in its research did not show measurable profit-and-loss impact under the report's definition of successful implementation.

That is a narrower and more useful finding than the headline. It concerns enterprise GenAI initiatives, a particular research sample and a measure of visible P&L impact. It doesn't say that individual employees received no benefit or that a specific, well-measured workflow has a 95% chance of failure.

What Did the Report Actually Study?

The GenAI Divide: State of AI in Business 2025 described preliminary findings from Project NANDA. It drew on public enterprise deployments, interviews and a survey of senior leaders to examine the difference between widespread experimentation and measurable business impact.

The report defined successful task-specific GenAI implementation through a marked and sustained productivity or P&L impact reported by users or executives. Its 95% figure described the share of enterprise initiatives that did not meet that threshold in the research.

Three qualifications matter:

  • the report was labelled preliminary
  • its success measure was specific, not a universal definition of project value
  • the result described the initiatives studied, not every AI use case in every organisation

Use the number as a prompt to examine implementation discipline, not as a forecast for your own project.

Why Can AI Pilots Struggle to Show Financial Impact?

A pilot may produce an impressive demonstration without changing the operating result that matters. Common causes include:

  • no baseline for the current workflow
  • a use case selected for novelty rather than business consequence
  • poor access to approved knowledge and data
  • no accountable workflow owner or reviewer
  • a test that excludes difficult and incomplete cases
  • no route from the pilot environment into everyday work
  • released time that isn't used or converted into another measurable result

These are design and operating-model problems. A stronger model can improve the output, but it can't decide who owns the process or whether the business will change how the work is done.

What Counts as AI ROI?

Start with the result the workflow owner can verify. Examples include:

  • less elapsed time from request to completed work
  • fewer manual touches or corrections
  • more complete records at hand-off
  • less senior time spent finding or assembling information
  • fewer exceptions that require rework
  • faster response without a reduction in quality

Then decide how that operating result creates value. Reduced task time is potential capacity, not automatically cash. It becomes financial value when the business avoids cost, increases throughput, improves retention, reduces an exposure or uses the time for another valuable activity.

How Should a Business Design a Measurable AI Pilot?

Define One Workflow

Write down the trigger, inputs, current steps, output, owner and reviewer. Avoid a pilot with the goal of proving that AI can help the whole company.

Record the Baseline

Measure the current process using representative work. Choose a small number of measures the workflow owner already understands.

State the Hypothesis

Use a falsifiable statement. For example: the capability will reduce preparation time for this report while maintaining the agreed completeness and review standard.

Test Difficult Cases

Keep a separate test set. Include incomplete inputs, conflicting sources and the cases where a person should stop the workflow or escalate.

Define Human Control

Name who checks the output, what evidence they see and which decisions remain outside the system. A person needs both authority and enough context to reject the result.

Plan the Production Path

Decide how identity, permissions, source updates, monitoring, support and ownership will work if the pilot succeeds. A proof of concept without this path can pass its demo and still go nowhere.

Our AI pilot guide provides a detailed checklist. The business AI strategy guide helps choose the workflow and connect it to a business priority.

What Should Leaders Ask Before Funding a Pilot?

Ask five questions:

  1. Which business result will change if this works?
  2. What evidence describes the current result?
  3. Who owns the workflow and can change it?
  4. What must remain under human review?
  5. What happens after the pilot meets its acceptance criteria?

If the team can't answer these, narrow the work before increasing the budget.

How Should You Use the 95% Statistic?

Use it accurately. Say that preliminary 2025 Project NANDA research found that most enterprise GenAI initiatives studied did not show measurable P&L impact under its definition. Link the report and state what your own business will measure.

Don't say that MIT proved 95% of AI projects fail. That wording removes the population, measure and research status that give the finding meaning.

If you want to turn one business priority into a measurable test, tell us about your business. We will help define the workflow, baseline and smallest useful scope before choosing the technology.

AI ROIAI StrategyAI ImplementationGenerative AIAI Pilots

Frequently Asked Questions

No. The widely shared figure came from preliminary Project NANDA research into enterprise generative AI initiatives and whether they showed measurable productivity or P&L impact under the report's definition.

Not necessarily. Employees may save time or improve an output without the organisation converting that change into visible financial impact. A business still needs to measure the workflow and decide how released capacity creates value.

Pilot purgatory describes work that demonstrates technical potential but never becomes an owned production workflow. Missing integration, controls, adoption, funding or accountability can all keep a pilot there.

Record the current workflow baseline, define the expected operating change and track quality and human review alongside time or cost. Convert the result into financial value only when the business can explain how it will use it.

Choose a frequent, bounded and reviewable workflow with a clear owner and approved source information. It should matter enough to measure but remain controlled if the output is wrong.

Choose the Right Starting Point for Your Business

Tell us what you'd like your business to do better, or where you're getting stuck with AI. A few sentences are enough.

From ELab AI

In the Loop Newsletter

Model releases worth paying attention to, practical lessons from client work and useful ways to apply AI inside your business.