If your AI rollout is stuck, the model is probably not the problem. Stanford's Digital Economy Lab interviewed the people behind 51 enterprise AI deployments that actually delivered measurable value, and asked each of them what was hardest to fix. 77% of the hardest challenges they named were change management, data quality or process redesign, not the technology.
That is the core of The Enterprise AI Playbook: Lessons from 51 Successful Deployments, by Elisa Pereira, Alvin Wang Graylin and Erik Brynjolfsson, published in April 2026. It is a study of what worked. Read it that way and it is one of the more useful documents an enterprise AI leader can hand to a steering committee this year.
What Stanford Actually Studied
The sample matters more than any single number in the report, so start there.
The lab ran structured interviews with executives and project leads at 41 organizations across 7 countries and 9 industries, with the heaviest coverage in manufacturing, financial services and technology. Interviews ran from August 2025 to February 2026. Companies supplemented them with internal metrics, project reviews and financial updates, and each case was scored only on documented evidence.
A deployment had to clear four bars to be included:
- Operational stability: live, integrated into real workflows, used in production.
- Sustained adoption: teams relying on it for at least three months.
- Quantified value: a measured outcome such as productivity, revenue or customer satisfaction.
- Scalability: it could be extended to other teams, regions or business units.
So every one of the 51 cases is a success by design. The authors are explicit about what that rules out. In their words, "we don't claim to provide representative data on how common success is across the broader economy." The report contains no failure rate, and none can be derived from it.
The failure statistic that usually travels with this report comes from somewhere else. The authors open by citing MIT NANDA's 2025 study, which concluded that 95% of generative AI pilots produce no measurable financial impact. Stanford's project is the mirror image: instead of counting failures, it asks what the survivors did differently.
The interviews did cover failure: every one asked about the false starts that came before the result. 61% of the successful projects had at least one prior failed attempt, and the cost of those attempts never appears in the final ROI. Two thirds of the companies had significant failures before they created value.
The Hard Part Is Everything Around the Model
Asked what was hardest to fix, practitioners named invisible costs for 77% of the challenges they listed. One telecom executive put it plainly: "All the hard work is in process documentation and data architecture. If you can do those two things, everything else is quite simple."
This lines up with older research the report cites. Brynjolfsson's own work on the productivity J-curve found that for every dollar of visible technology investment, companies spend up to ten on intangibles such as process redesign and reskilling, which depresses measured productivity before the gains arrive.
For your business case, that means the line items people underfund are the ones that decide the outcome, and a budget made mostly of licences and inference pays for the easy part.
The report's data chapter makes the same point from the other direction. Only 6% of the implementations had data that was fully ready for AI. Yet in most cases with messy data, the language models were part of the fix: they unlocked previously inaccessible data in 88% of cases, working through voice transcripts, scanned documents, legacy code and scattered knowledge bases. The authors add a caveat worth repeating. A sample of successes will underrepresent the projects where data quality really was fatal.
Why Similar Projects Take Weeks or Years
The report found the same use case taking wildly different amounts of time at different companies. A large fintech used a coding agent to migrate millions of lines of legacy ETL code in weeks. A technology company rebuilt its customer support with AI and launched in six months. A major bank attempting the same support use case reported projects taking multiple years.
The lab coded what sped projects up and what slowed them down:
| Accelerates time to value | Share of cases | Slows projects down | Share of cases |
|---|---|---|---|
| Executive sponsorship | 43% | Learning curve and iteration | 25% |
| Building on an existing foundation | 32% | Data quality and preparation | 21% |
| End-user willingness | 25% | Regulatory and compliance | 21% |
| Process documentation gaps | 21% |
Two patterns are worth taking into your planning. First, the second project is faster than the first. One company built a sales copilot in months because it had already built an AI platform for customer support. Second, users who badly want relief adopt fast. Hospital systems adopted ambient transcription despite unclear ROI because physicians were burning out on documentation.
The method finding is the cleanest in the report. Of the cases where the development approach could be identified, all of them iterated. None used waterfall planning. A food delivery executive described their hit rate candidly: "Probably 90% of the pilots and tests fail, but then we iterate on those until we find them and it grows and grows."
How Much Human Oversight Pays Off
The lab classified each deployment by how much a person stays in the loop:
- Escalation: AI handles 80% or more on its own, and humans review exceptions or samples.
- Approval: AI does the work, and a human approves every output before it takes effect.
- Collaboration: human and AI work on each task together.
Escalation models delivered a 71% median productivity gain against 30% for approval models. Before you read that as "remove the humans", note the authors' own caveat: escalation tends to be applied to high-volume, recoverable work, while approval and collaboration serve regulated or high-stakes tasks. Part of the gap is task selection.
The by-function numbers show why the right level depends on the work:
| Function | Typical oversight | Average gain |
|---|---|---|
| IT operations | Escalation | 90% |
| Customer support | Escalation | 71% |
| Claims processing | Escalation | 50% |
| Field service | Approval | 80% |
| Clinical documentation | Approval | 66% |
| Coding | Collaboration | 54% |
Clinical notes are legal documents, so a physician signs every one. Customer support can run on exceptions: one technology company reached 82% ticket deflection after redesigning the workflow around AI-first resolution. Choose the oversight level from error tolerance and regulation, and expect it to differ by function.
What Effective Sponsors Do
"Get executive sponsorship" is advice everyone has heard. The report is more specific about what sponsorship means in practice. It rated sponsors on four levels:
| Level | What the sponsor does | Share of cases |
|---|---|---|
| 2. Periodic oversight | Monthly reviews, removes blockers when escalated | 12% |
| 3. Active steering | Weekly check-ins, proactively removes blockers | 58% |
| 4. Strategic integration | AI adoption in corporate OKRs and incentives | 29% |
Level 1, passive approval (budget signed, everything delegated), does not appear in the breakdown at all. Active steering was the most common pattern and worked well inside a single function. But the seven cases that transformed a whole organization all reached level 4: the sponsor made AI adoption a corporate objective tied to bonuses rather than a project to support.
The other consistent trait was cultural. The most effective sponsors gave teams permission to fail, learn and try again without career damage. Given that 61% of the successes followed a failure, that permission is what made the second attempt possible.
Where Resistance Comes From
Most change plans focus on end users. In this sample, staff functions were the bigger obstacle: legal, HR, risk and compliance accounted for 35% of resistance, against 23% from internal end users.
Each group resisted for its own reason, and each needed a different answer:
- C-level executives wanted measurable proof of ROI.
- Staff functions worried about process risk and who would be blamed when something went wrong.
- End users distrusted inconsistent output.
- Frontline workers feared replacement.
Staff functions can stop a project regardless of executive support, so bring legal, risk and compliance in early as design partners. The report notes that some became enablers once they had bought in.
Security fits the same pattern. Across the 12 cases with complete data, security was never a pure project killer. Where security requirements created barriers, the same controls later let the project handle sensitive data that would otherwise have been off-limits. The cost is real but front-loaded.
What Happened to Headcount
Headcount reduction was the largest single outcome, in 45% of deployments. The alternatives (hiring avoided, redeployment and no reduction) together made up the other 55%.
What predicted the outcome was the purpose of the deployment rather than the technology. Revenue-generating applications more often led to redeployment or growth. Cost-reduction applications more often led to direct cuts. The authors also point to payroll research showing early-career workers in AI-exposed occupations already seeing a 16% relative decline in employment, so the 55% should not be read as reassurance about the wider labour market.
On revenue, the finding is that it is real but rare. Most cases were measured as cost savings. The ones with direct revenue impact followed three patterns: personalisation that converts, speed that wins deals, and internal tools repackaged as products for clients. The distinguishing feature was that someone bothered to measure the revenue side.
Agentic AI and Model Choice
Agentic implementations made up only 20% of the cases, but delivered a 71% median productivity gain against 40% for high-automation deployments. They worked best where volume was high, success criteria were clear and errors were recoverable. The authors attribute the low share mostly to timing, since enterprise agent frameworks only became widely available in 2025.
Model choice mattered less than vendors would like. For 42% of implementations the model was fully interchangeable, 39% rated it moderately important, and only 19% called it a critical differentiator. Routine tasks were four times more likely than advanced ones to treat the model as a commodity. The companies that pulled ahead had built an abstraction layer that let them switch models, and the report expects the commodity share to grow as open models close the gap.
Why the Successes Failed First
The report's appendix is the closest it comes to a failure study, and it is the most practical part. For the 61% of implementations that hit a significant failure before reaching value, the lab grouped what went wrong into six root causes. A case can have more than one, so the shares overlap:
| Root cause | Share of cases | How it showed up | What fixed it |
|---|---|---|---|
| The organization wasn't ready to adopt | 35% | Pilots stalled, low usage, no internal champions | A visible CEO mandate tied to OKRs; training on specific use cases, not just tool access |
| Critical knowledge was never captured | 27% | Generic or wrong answers, users losing trust | Documentation as a prerequisite; using AI to extract tacit knowledge from staff |
| Legal or compliance blocked the project | 18% | Months of approval delays, use cases confined to low-value safe zones | Legal engaged early as a partner; PII scrubbing, redaction and audit trails from day one |
| The technology broke or wasn't mature | 16% | Failure at production scale, costly rework | Modular frameworks; dual-model validation before trusting single outputs |
| Wrong problem or unrealistic expectations | 14% | A solution looking for a problem, leadership killing it early | Mapping processes end to end; telling leadership most first attempts fail |
| A talent or sponsorship gap | 12% | Slow iteration, vendor dependency, lost priority | Dedicated data science roles; sponsorship across more than one executive |
The authors make a useful distinction here. "Stuck in pilot" and "can't prove ROI" are symptoms that appeared constantly, but they are consequences. The table is about causes, and only one of the six, at 16%, is the technology.
On measurement, the appendix is blunt. Teams that defined KPIs before deployment were more likely to show value and keep their funding, and many teams measured only efficiency, often headcount, while ignoring quality, customer value and revenue.
What the Report Cannot Tell You
Three limits are worth keeping in front of anyone who quotes it.
First, the data is mostly self-reported by the executives who ran the projects, supplemented by documents they chose to share. Second, the sample leans toward technology and financial services, which the authors say reflects early adoption rather than the whole economy. Third, every case is anonymized, so none of the numbers can be checked against a named company.
The findings can still guide you, as long as you remember the percentages describe 51 successes. Don't quote them as a success rate, a failure rate or a benchmark for your own ROI.
What This Means for Your Program
The report is a sample of successes, so its numbers describe what working deployments looked like, not your odds. Used that way, it gives you a checklist with evidence behind each item.
This Week:
- Open your current AI business case and total the lines for process documentation, data work and change management. If they are a small fraction of licence and inference spend, the budget is weighted toward the easy part.
- Write down every pilot that was abandoned in the last 18 months and what it taught you. The report's successes mostly came after a failure, so treat this list as an asset.
This Month:
- Name the oversight model for each live or planned use case (escalation, approval or collaboration) and justify it by error tolerance and regulation, not by comfort.
- Put legal, risk, compliance and HR in the design review for your next deployment, before the pilot rather than at the go-live gate.
- Ask your sponsor for weekly involvement on the one project that matters most. Monthly reviews were the weakest sponsorship level among the successes.
Before Next Planning Cycle:
- Decide whether AI adoption belongs in corporate OKRs. All seven organization-wide transformations in the sample had made that move.
- Build or buy the abstraction layer that lets you swap models. In 42% of the deployments, the model was interchangeable anyway.
- Pick at least one use case where you measure revenue impact rather than cost saved.
The Bottom Line
The Stanford playbook does not tell you how many AI projects fail. It tells you what the ones that worked had in common: they iterated, they spent most of their effort on process and data, their sponsors showed up weekly, and they treated the first failure as part of the cost. Earlier enterprise technology waves followed the same pattern: the productivity gains arrived after the reorganisation, well after the purchase.
Start by putting real money against process documentation and data work, because that is where 77% of the hard problems were.
Correction (October 31, 2026): An earlier version of this article attributed a 78% (and elsewhere 95%) failure rate, a 340% average ROI, and several paired adoption and production-rate figures to the Stanford report. The report studies successful deployments only and contains none of those figures. The 95% figure comes from MIT NANDA's separate 2025 study. The article has been rewritten from the report itself. Thanks to the reader who checked the source.
