Unleash Epic
AI & Technology

Why AI Pilots Stall Without Controlled Work

John Vyhlidal12 min
Share:

Why AI Pilots Stall Without Controlled Work

The demo works. On Monday the same work still moves by hand.

The demo works. The pilot gets a slide. Then Monday comes, and the work still moves the old way. Someone pastes a draft into a chat window, checks it by eye, and files the result by hand.

The tool sits beside the work, and the process that already runs the business never takes the result back.

If you've inherited a pilot like that, you already know the meeting. The technology did what the vendor showed. The operation kept running the old process. Project NANDA, McKinsey, and WalkMe counted that stall across 2025 and 2026.

I've written before about running a tech project and calling it a transformation. This article stays with the pilot that already demos, and with the process that never receives a finished result. If you're still learning the tool itself, start with the executive's guide to getting started with AI. This article assumes the pilot exists.

What the research actually says

In July 2025, Aditya Challapally, Chris Pease, Ramesh Raskar, and Pradyumna Chari published The GenAI Divide: State of AI in Business 2025 from Project NANDA. The cover note calls the paper "Preliminary Findings from AI Implementation Research." They reviewed more than 300 public initiatives, interviewed people from 52 organizations, and collected survey responses from 153 senior leaders. They did that work from January through June 2025.

The executive summary says: "95% of organizations are getting zero return." The next sentence says: "Just 5% of integrated AI pilots are extracting millions in value, while the vast majority remain stuck with no measurable P&L impact." They set that result next to $30 to $40 billion in enterprise GenAI investment.

Those two sentences are about organizations, and about measurable profit and loss. The paper is preliminary. The authors say this comes from the interviews, the survey, and the public initiatives.

The same summary reports the funnel for enterprise-grade systems, custom or vendor-sold. "Sixty percent of organizations evaluated such tools, but only 20 percent reached pilot stage and just 5 percent reached production." The authors attribute most of that drop to "brittle workflows, lack of contextual learning, and misalignment with day-to-day operations."

Later the paper uses the phrase "the 95% failure rate for enterprise AI solutions" for the return split. Headlines shortened that phrase again, into a claim that 95 percent of pilots failed. The executive summary says 95 percent of organizations are getting zero return. It also counts how many custom or vendor tools reach a pilot, and how many reach production. The authors put this limit on the funnel: "These figures are directionally accurate based on individual interviews rather than official company reporting. Sample sizes vary by category, and success definitions may differ across organizations." The appendix adds that a six-month window can understate success for complex systems.

In this sample, most organizations saw no measurable P&L return. Custom and vendor tools dropped hard before production.

McKinsey's global survey, "The state of AI in 2025: Agents, innovation, and transformation," came out November 5, 2025. McKinsey ran the fieldwork from June 25 to July 29, 2025, with 1,993 respondents in 105 nations.

McKinsey defines AI high performers as respondents who attribute an EBIT impact of 5 percent or more to AI and who report "significant" value. That group is about 6 percent of respondents. Two practices show up with that group. "High performers are also nearly three times as likely as others are to say their organizations have fundamentally redesigned individual workflows." Redesigning workflows "has one of the strongest contributions to achieving meaningful business impact of all the factors tested." High performers are also more likely to have "defined processes to determine how and when model outputs need human validation to ensure accuracy."

88 percent report regular AI use in at least one function. About one-third say their companies have begun to scale. 39 percent attribute any enterprise EBIT impact to AI. Among organizations using AI, 51 percent report at least one negative consequence, and nearly one-third report consequences from inaccuracy.

The respondents who report a meaningful return are much more likely to say they redesigned the workflow and decided when a person has to check the output.

WalkMe's State of Digital Adoption 2026 is the worker's side of the same stall. WalkMe announced the report on April 9, 2026. The method section describes two surveys in the first quarter of 2026: 3,750 participants at organizations with 1,000 or more employees, across 14 countries. That total is 1,700 senior leaders and 2,050 office and hybrid workers.

The report says: "In any given month, more than half of workers abandon their enterprise tools at least once and do the work manually instead. For a third of them, it's a recurring pattern." It also says 37 percent of workers "skip AI entirely because using it means breaking their workflow and manually moving data between systems."

On the path around the official tools: "45% of workers used unapproved AI tools in the past 30 days. 36% used them with confidential company, customer, or employee data." On trust: "Only 9% trust AI enough to use it for high-impact work," while "61% of executives trust AI for complex work."

People are finishing the job by hand, or in a tool the employer did not approve, sometimes with confidential data in the prompt.

The strongest objection

Approval gates are why enterprise AI moves slowly. The firms that get value move fast with copilots, let skilled people improvise, and accept some mess. The widely shared line that 95 percent of AI pilots fail is a media simplification of a preliminary working paper. A product story built on that line is standing on a soft fact. Workers bypass official tools because official tools are clumsy. Another layer of logging and approval makes them clumsier. A survey that shows high performers redesign workflows still leaves the cause open. Those firms may simply be better operators. They might have done well on any stack.

Most of that objection holds.

The NANDA paper is preliminary. It says so on the second page. The funnel figures come from interviews. Success definitions differ. The authors warn that a short observation window can understate success. The executive summary says 95 percent of organizations are getting zero return. It counts the path to production separately: evaluated, piloted, and in production.

Speed and judgment still matter. The same paper says generic tools such as ChatGPT and Copilot are widely explored, and the people interviewed described them as flexible and immediately useful. A copilot in a skilled person's hands is real help on individual work. The paper's point is that this help has been hard to see in the P&L.

The clumsy-tool point holds too. WalkMe's report says workers skip AI when using it means breaking the workflow and retyping data between systems. A logging layer pasted onto that kind of tool will get the same walk-around. People still finish the job by hand, or in a tool they picked.

The operator point holds too. McKinsey's high performers are a small group defined by reported results. The survey shows which practices they report alongside those results. It leaves open whether the practices caused the results, and whether a weaker operator would get the same outcome by copying the list. NANDA makes a similar caution about one of its own findings. Firms that choose an outside partner may already differ in capability, so the correlation is not yet a cause.

What's left is enough to act on this week.

What still stands

McKinsey's high performers report two design choices together. They redesign the workflow. They define how and when a person has to check the model's output for accuracy. In the WalkMe numbers, people finish the work by hand, or they finish it in a tool the firm did not approve, and a meaningful share of that second path includes confidential data.

That workaround is the control gap.

In Between the Curves, the gap is two curves pulling apart: what the tools can do and how widely people use them, and the risk that grows with that use. The risk sits between the work people actually do with AI and the work the firm can govern. The person who owns the work is the person who can judge whether the output is complete and accurate. IT can help with access and with the log. Accountability for the output stays with the function that does the work.

Put the approval on the moments that can spend money, touch a client, or send something outside the firm. Let the ordinary steps run, and write the finished result back to the record. That puts both high-performer practices on a process you already run. You redesign the workflow. You define the point where a person checks the output. You can run it on Monday. Those two practices show up next to reported return, and there is still room for the other explanation, that better operators would have found some way through on another stack.

What controlled work looks like on Monday

Start with a process the business already runs. A file lands in a folder. A form is submitted. A Slack message arrives. That trigger starts the firm's own steps. Each step is logged under a name. When a step would move money, touch a client, or send something outward, it waits. The owner approves it or sends it back. The run writes the finished result into the system of record the team already uses.

That is controlled work. The run produces a finished artifact. The log shows what happened and whose name is on it. The approval is narrow, and the owner can say no.

I use the name Systems Intelligence for this idea. It is one concept with two angles. One angle is the business around the work: an owner who can make it move, decision rights that are clear, people who know the work, information you trust, and systems that fit the workflow. The other angle is the harness, the part that runs the automation. The harness takes the trigger, walks the firm's steps, keeps the log, holds the sensitive items for the owner, and returns the finished work.

The front door is live. The agents that read and write are still being built. So is the learning loop that files a missing step and builds the next automation. You can run the check below without waiting on those pieces.

Consultancies and MSPs can deliver an AI Execution Plan and the install. Unleash Epic provides the platform. If you want a conversation about one process, the company path is on the services page.

Why a rollout gets walked around

A rollout hands people a tool and asks them to change a habit. The old process is still the one that finishes the job. The file still has to reach the record. The client still has to receive an answer. When the new tool makes that harder, people do the task the old way, or they do it in a tool they picked themselves.

People abandon the enterprise tool and finish by hand. Many skip AI when it breaks the workflow. Others finish in an unapproved tool, and a share of that path includes confidential data. Executives trust these tools for complex work far more often than workers trust them for high-impact work. That distance is the trust gap.

The unapproved path is the control gap, and people are already on it. A process that finishes the work, logs the steps, and waits only where the risk is real gives people a path they can stay on.

Run the check on one live process

Five questions. Yes or no. Use them on one process that already has a trigger you can point at: a dropped file, a form, or a Slack message. The score tells you how many of the five pieces are in place, and which missing piece to fix first.

Control-gap check

Five yes or no questions on one live process

Pick a process that already starts with a trigger. Answer for that process only. The result names the first missing piece.

1. A named owner is accountable for this process.
2. The process is written down in the firm's own steps.
3. Each step leaves a log under a name.
4. Money, client contact, and outbound sends wait for the owner's approval.
5. The finished artifact goes back to the system of record.

Do this in the next working session

Write the trigger in one line. Under it, write three things: the owner's name, where the log of steps will live, and the one action that must wait. Money, a client, or an outbound send. If you can't name the owner, that's the whole task. Name the owner before you add a tool.

The check above is one page, on a single live process. Run it this week.

FAQ

What did the MIT NANDA research actually say about generative AI return?

Project NANDA's July 2025 paper, The GenAI Divide, says 95 percent of organizations in its research are getting zero return. It says 5 percent of integrated AI pilots are extracting millions in value. The vast majority remain stuck with no measurable P&L impact. On custom or vendor tools, 60 percent of organizations evaluated them, 20 percent reached a pilot, and 5 percent reached production. The paper calls itself preliminary. It says the funnel figures come from interviews, and that success definitions differ by organization.

What does controlled work mean in practice?

Controlled work means a trigger starts a process the business already runs. Each step is logged under a name. Money, client contact, and outbound sends wait for the owner. The run returns a finished result to the system of record.

Where should a person still approve model output?

McKinsey's 2025 survey found that AI high performers are more likely to have defined processes for how and when model outputs need human validation. In a controlled process, that check sits on the steps that spend money, touch a client, or send something outside the firm. The other steps can finish and write the result back to the record.

Run the control-gap check on one process you already run.

Leave your email and I'll send the one-page check. If you want help turning that process into finished work, with a log and an owner, reply when it arrives.

No spam. Unsubscribe anytime.

AIOperationsLeadership
John Vyhlidal

John Vyhlidal

Founder & Principal Consultant

Military officer, then the Big 4, then the Fortune 500, and now a business owner. He has spent 25 years learning how work moves and how systems support it, and he runs his own company on the Systems Intelligence platform.