Drill the Findings

The playbook's final synthesis. AI success is not a technology problem; it's an organizational transformation problem. The moats are operating skills, not model choices.

77% of implementation challenges came from change management, data quality, and process redesign — not technology. Put them in the Gantt chart with named owners.

~95% of generative AI pilots fail to produce measurable financial impact. The Stanford 51 are the reverse-engineered profile of the 5% that worked.

AI proposes, human approves at every step. Sounds safe but the human becomes the bottleneck. Underperformed escalation-based in the playbook's data.

"The difference was never the AI model. It was always the organization." Readiness, processes, leadership, willingness to redesign workflows and absorb failure.

Role redefinition, retraining, performance-system rewrites, internal comms. One of the three non-technical cost lines that eat 77% of project difficulty.

Most projects target cost savings — bounded by the size of the cost line attacked. Productization, personalization, and faster cycles have higher ceilings.

Schema work, dedup, lineage tracing, consent / access review. Treat as engineering line items with named owners, not as "the data team will handle."

Stanford economist, co-author of the playbook. Leading researcher on technology and economic productivity (Second Machine Age, Race Against the Machine).

AI handles routine cases end-to-end; humans intervene only on exceptions. 71% median productivity gain — the highest among the three operating-model types studied.

The most-cited failure pattern: teams treat AI projects as side-pocket experiments rather than production systems with control, integration, and operational ownership.

61% of successful deployments had at least one prior failed attempt. High performers treat failure as structured learning. Architect the first attempt with the second in mind.

42% model interchangeability implies treating model as substitutable infrastructure. Architectural pattern: keep model layer thin and replaceable; put institutional knowledge above it.

A case counts as "successful" only if it's live in production, used consistently, delivering measurable business value, and capable of scaling. All four — or not in the dataset.

AI runs end-to-end without human checkpoints. Underperformed escalation-based because risk surfaces too late, after damage is done.

Legal, HR, and compliance are the silent veto. Build parallel adoption tracks with named owners and standing office hours — end-user enthusiasm doesn't unblock them.

Tailored offers, individualized customer journeys, segment-of-one service. One of the high-value revenue use cases the playbook cites, though still rare overall.

Spend it on workflow orchestration, system integration, UX, and evaluation rubrics — the layers that survive model swaps. Don't lock onto foundation model choice.

LLMs interpret unstructured inputs, connect fragmented datasets, fill gaps. Treats "data isn't ready" as obsolete blocker — now usually polite framing of organizational resistance.

In 42% of studied cases, the foundation model was interchangeable without changing outcomes. The empirical case for treating model choice as substitutable infrastructure.

Real AI projects are owned by the operating-unit leader with P&L responsibility — not by the "innovation team." Ownership shift is the first move from experiment to strategic integration.

Weekly standing cadence with the project lead + explicit blocker removal + OKR alignment. The kind of sponsorship that correlated with success — not signing a kickoff deck.

Mapping the as-is workflow, defining to-be, validating with users, rewriting SOPs. Run as discovery + iterative redesign sprints, not as a memo.

Selling AI capabilities as part of the product offering creates net-new revenue. The largest value ceiling in the dataset, and where the highest-multiple cases cluster.

"This is a production system that uses AI" — not "this is an AI experiment." The reframe that distinguishes the 5% from the 95%, per the playbook.

Research lab led by Erik Brynjolfsson studying how digital technology is reshaping the economy. Publisher of the Enterprise AI Playbook report.

Owning AI as a production system embedded in the operating model — KPIs, P&L, control systems, audit. The opposite of "innovation team running an AI experiment."

Stanford Digital Economy Lab report (April 2026, Pereira/Graylin/Brynjolfsson). 51 deployments × 41 orgs × 9 industries × 7 countries. Studies what survived to production.

Identical use cases took weeks in some companies, years in others. Set by exec sponsorship cadence, infrastructure readiness, end-user willingness, and gatekeeper behavior.

Bolt-on captures 10-20% of value. Workflow redesign captures the productivity multiples. The largest single separator: 55% of high performers vs 20% of others.

McKinsey signal cited in the playbook: 55% of high performers redesigned workflows around AI vs only 20% of other companies. The largest single separator.

Productivity gains do not auto-trigger layoffs. 45% of deployments reduced headcount; others redeployed or accelerated growth. Pick the strategy deliberately on day one.