The Adoption-Value Gap
Everyone has AI; almost nobody has AI value
- Be able to state the adoption–value gap in one sentence and back it with the converging McKinsey, BCG, and MIT NANDA findings (with sources and years)
- Be able to explain why near-universal adoption coexists with rare enterprise value — the 'pilot purgatory' diagnosis
- Be able to identify the real differentiator between value creators and laggards: workflow redesign and operating model, not model quality
- Be able to recognize and reject the false explanations leaders reach for (wrong model, not enough pilots, not enough seats)
- Be able to apply the frame 'if pilots aren't moving EBIT, the problem is rarely the tech' to your own AI portfolio
- Be able to ask the diagnostic questions that separate a stalled tool rollout from a value-creating transformation
By 2026, almost every large organization uses AI somewhere, yet only a small minority can point to enterprise-level financial value from it — a gap three independent studies (McKinsey, BCG, MIT NANDA) measured and agreed on. This lesson shows that the gap is overwhelmingly about operating model and workflow redesign, not about the model or the technology. It gives leaders the durable frame — 'if pilots aren't moving EBIT, the problem is rarely the tech' — that the rest of the value module builds on.
- 1The one headline every executive needs in 2026
- 2Three studies, one conclusion
- 3Why so many pilots stall: 'pilot purgatory'
- 4The real differentiator: the 70% no one funds
- 5The diagnostic frame: 'if pilots aren't moving EBIT, the problem is rarely the tech'
- 6What this means for how you lead
The one headline every executive needs in 2026
If you remember a single sentence from this entire module, make it this:
Everyone has AI; almost nobody has AI value yet.
This is not cynicism — it is the most consistent finding in the 2025–2026 research, and it reframes the executive's job. The question that matters is no longer "are we using AI?" (you almost certainly are, in more places than you realize). The question is "are we extracting enterprise value from it?" — and for most organizations, as of early 2026, the honest answer is not yet.
The danger of getting this wrong is specific. A leader who hears "88% of companies use AI" concludes the race is half-won and the work is technical. A leader who understands the adoption–value gap knows the opposite: adoption is the easy part that everyone has already done, and value is the hard part that almost no one has cracked — and the hard part is organizational, which means it lands squarely on the executive's desk, not the engineering team's.
The rest of this lesson does three things: shows you the data behind the headline (so you can defend the claim in a board meeting), names the real cause of the gap, and gives you the diagnostic frame to apply to your own portfolio.
Key insight
The reframe
Adoption is table stakes — a starting line everyone has crossed. Value is the race. Treating adoption as the achievement is the single most common executive misread of where AI actually stands.
Three studies, one conclusion
What makes the adoption–value gap credible is that three very different research efforts — a consulting megasurvey, a strategy-firm benchmarking study, and an MIT-affiliated field study — arrived at the same place from different angles. When McKinsey, BCG, and MIT independently measure a gap and agree, a board should treat it as real.
| Study (source, date) | Adoption | Value realized |
|---|---|---|
| McKinsey, State of AI (Nov 2025) | ~88% of orgs use AI in ≥1 function | Only ~39% report enterprise-level EBIT impact; ~94% say they are not yet seeing significant value |
| BCG, Widening AI Value Gap (Sept 2025, n≈1,250) | Near-universal investment | Only ~5% are "future-built" value creators; ~35% "scalers"; ~60% "laggards" with minimal gains despite spending |
| MIT NANDA, GenAI Divide (July 2025) | >80% have piloted tools like ChatGPT/Copilot | ~95% of enterprise GenAI pilots delivered no measurable P&L return; only ~5% reached rapid value |
Notice the shape repeats: a very large number adopting, a very small number — somewhere around 5% in the most demanding studies — actually capturing value. The numbers themselves will move (these are dated findings, re-verify before you cite them), but the pattern is durable: wide adoption, narrow value.
BCG also quantified what that narrow group of value creators looks like financially. As of its September 2025 study, "future-built" firms showed roughly 1.7× the revenue growth, 1.6× the EBIT margin, and 3.6× the three-year total shareholder return of trailing firms. The gap between leaders and laggards is not cosmetic — it is widening, and it shows up in the financials the board already watches.
Watch out
Statistics are volatile — attribute, don't memorize
Every percentage here is a time-stamped finding from a named 2025 study, not a timeless law. Adoption rises and value figures shift each survey cycle. Teach and cite the pattern (wide adoption, narrow value) and re-verify the live number before you put it in a board deck. The sources are in the resources list precisely so you can re-check them.
Example
The MIT NANDA 95% figure
The most cited single statistic — ~95% of enterprise GenAI pilots show no measurable P&L return (MIT NANDA, July 2025) — is striking, but the part leaders skip is the root cause MIT identified: the failure is a 'learning gap' in workflow and integration, not weak models. That distinction is the whole point of this lesson.
Why so many pilots stall: 'pilot purgatory'
If the technology works in a demo, why does value so rarely follow? The research points to a recognizable failure pattern — leaders call it "pilot purgatory": a stream of promising proofs-of-concept that impress in the room and then never scale into the business or move a financial number.
The causes are consistent across MIT, McKinsey, BCG, and Deloitte, and almost none of them are about the model:
- The 'learning gap' (MIT NANDA). Pilots fail because the tools don't integrate — no memory, no feedback loops, no redesign of the surrounding process. The model is fine; the workflow around it never changed.
- The 'gen AI paradox' (McKinsey). Easy, horizontal copilots and chatbots scale fast but spread diffuse, unmeasurable gains. The deep, vertical, function-specific use cases — where the real money is — stay stuck in pilots.
- No workflow redesign (McKinsey). As of its 2025 research, McKinsey found workflow redesign has the single biggest effect on EBIT impact — yet only ~21% of firms had fundamentally redesigned a workflow. Most simply "bolt AI onto" the legacy process.
- Budget pointed at visibility, not value (MIT NANDA). More than half of GenAI budgets went to visible front-office (sales/marketing) tools, even though the better near-term ROI sat in less glamorous back-office automation.
- Pilot fatigue (Deloitte). Repeated failed cycles don't just waste money — they erode the organization's capability to run the next pilot well. Deloitte reported the share of enterprises abandoning most AI initiatives rose sharply from 2024 to 2025.
Read that list again and notice what is not on it: "we picked the wrong model." Pilot purgatory is an operating-model disease, and the executive owns the operating model.
Tip
The leadership move
When a pilot stalls, resist the instinct to swap vendors or upgrade the model. Instead ask: did we redesign the workflow around it, or did we drop AI onto an unchanged process? Nine times out of ten, the second is true — and that is a leadership fix, not a procurement one.
The real differentiator: the 70% no one funds
If the model isn't the bottleneck, what is? The most useful framework here is BCG's 10-20-70 rule, and it is worth committing to memory because it tells an executive exactly where to look:
| Share of effort & value | What it covers | Who in the org owns it |
|---|---|---|
| ~10% | The algorithms / models themselves | Data science, vendors |
| ~20% | Technology and data infrastructure | Engineering, IT |
| ~70% | People and process — adoption, workflow redesign, reskilling, incentives, change management | The executive team |
The whole adoption–value gap lives in that bottom row. Winners invest in the 70%; stalled organizations invert the ratio — pouring attention into models and platforms while treating people and process as an afterthought. And the 70% is exactly the part executives own and engineers cannot do for them.
The evidence that this is the binding constraint is strong:
- McKinsey's analysis found that, of all the attributes it tested, CEO oversight of AI governance was the factor most strongly correlated with bottom-line impact — a leadership variable, not a technical one.
- BCG found that nearly 100% of "future-built" firms have deeply engaged C-suites — versus a small fraction of laggards. AI delegated downward to mid-level managers stalls.
- Yet, per Deloitte, only ~37% of organizations invest significantly in change management — meaning most are under-funding the exact 70% that determines whether value appears.
This is the optimistic part of the story. If the gap were caused by model quality, you would be at the mercy of vendors and the pace of research. Because it is caused by operating model and workflow, it is within your control.
Key insight
Why this is good news
A model-quality gap would be someone else's problem to solve. An operating-model gap is yours — which means you can close it with decisions you are already empowered to make: where to focus, which workflows to redesign, who owns governance, and what you measure.
Watch out
Where leaders get it wrong
The classic error is to run AI as an IT or tooling project — buy the platform, roll out the seats, declare adoption, and wait for value. That funds the 10–20% and starves the 70%. The result is high adoption metrics and flat EBIT: the adoption–value gap in miniature.
The diagnostic frame: 'if pilots aren't moving EBIT, the problem is rarely the tech'
Here is the frame to carry into every AI review. When an initiative isn't delivering, the reflex in most organizations is to interrogate the technology — is it the model? do we need a newer one? a different vendor? The research says that is almost always the wrong first question.
If pilots aren't moving EBIT, the problem is rarely the tech.
Use it as a checklist. When something stalls, walk the operating-model causes before you touch the technology:
| The instinct (usually wrong) | The better first question (usually the real cause) |
|---|---|
| "We need a better / newer model." | Did we redesign the workflow, or bolt AI onto a legacy process? |
| "We need more pilots." | Are we spread across scores of shallow pilots instead of 2–3 deep ones? |
| "We need more seats / licenses." | Are we measuring usage when we should be measuring value? |
| "The data scientists should fix it." | Is the C-suite actually engaged, or has this been delegated downward to stall? |
| "It's a build problem." | Should we have bought/partnered instead? (MIT NANDA: buying succeeds ~67% of the time vs. roughly a third of that rate for internal builds.) |
Each right-hand question points at people, process, focus, measurement, or ownership — the 70%. That is not a coincidence; it is the whole thesis of this lesson restated as a working tool. The next lessons in this module unpack each of these — where value concentrates, how to sequence quick wins, how to measure real ROI — but they all rest on this one diagnostic instinct.
Example
Concentrate, don't sprinkle
The winners' pattern is consistent across McKinsey and BCG: pick 2–3 high-value vertical use cases, redesign the end-to-end workflow around them, and tie each to a specific operational number — rather than running 100 disconnected experiments. Spreading thin is one of the most reliable ways to land in pilot purgatory.
Tip
The question to ask in the room
Next time a team reports an AI pilot 'isn't working,' ask one question before any technical discussion: 'What changed about how the work gets done?' If the honest answer is 'nothing — we added a tool,' you have found the problem, and it isn't the model.
What this means for how you lead
The adoption–value gap turns a few comfortable assumptions on their head, and it's worth making the implications explicit before you move on.
- Stop celebrating adoption. "We've rolled out AI to everyone" is a starting line, not a finish line. Usage dashboards measure that you've crossed the line — not that you're winning the race.
- Treat AI as a transformation program, not a tooling project. The organizations capturing value run AI with CEO ownership, redesigned workflows, and real change management — not as a procurement exercise that ends when the contract is signed.
- Own the 70%. Workflow redesign, reskilling, incentives, and adoption are the executive's job and the locus of value. No vendor and no model upgrade will do this part for you.
- Default to buy-and-integrate; build only to differentiate. The evidence (MIT NANDA) favors buying and partnering for most use cases; reserve building for the few places AI is a genuine competitive edge.
- Separate the durable frame from the volatile numbers. The frame — wide adoption, narrow value; the cause is operating model — is stable. The exact percentages are not; re-verify them each cycle.
The through-line: the gap between AI leaders and laggards is real, measured, and widening — and it is being decided in the boardroom and the operating model, not the model lab. That is precisely why this is your problem to solve, and why the rest of this module is about where and how to solve it.
Key insight
The one-line takeaway for your team
"We don't have an AI technology problem; we have an AI operating-model problem." Say it out loud in your next review. It redirects energy from chasing models to redesigning work — which is where the value actually is.
Try it: Diagnose your own adoption–value gap
Goal: apply the lesson's frame to your real AI portfolio and produce a one-page diagnostic you could take to your leadership team. 1) Inventory honestly. List every place AI is used or piloted across your organization right now (include shadow AI you suspect but haven't sanctioned). For each, note: is this a shallow horizontal copilot, or a deep vertical workflow? 2) Score each on the two axes that matter. For each initiative, answer two questions: (a) Did we redesign the workflow around it, or bolt it onto an unchanged process? (b) Is it tied to a specific financial or operational number, or only to usage metrics (seats, logins, tokens)? 3) Find your purgatory. Circle every initiative that is 'tool bolted on + measured only by usage' — these are your pilot-purgatory candidates, the ones unlikely to move EBIT. 4) Apply the 10-20-70 test. Estimate roughly where your AI budget and leadership attention actually go: algorithms, tech/data, or people/process. If you're under-funding the 70%, name the gap in one sentence. 5) Pick your 2–3. From your inventory, choose the 2–3 highest-value vertical use cases worth redesigning a full workflow around — and name the operational number each should move. 6) Write the frame down. End with the single diagnostic sentence in your own words ('if our pilots aren't moving [our metric], the problem is rarely the tech') and one concrete operating-model change you will make this quarter. The deliverable is one page: the inventory, your purgatory list, your 10-20-70 estimate, your 2–3 chosen bets, and your one committed change. This is the exact analysis the rest of this module helps you act on.
Key takeaways
- 1The defining executive reality of 2026 is the adoption–value gap: almost everyone uses AI, almost no one yet captures enterprise-level value from it.
- 2Three independent 2025 studies converge on the same pattern — McKinsey (~88% adopt, ~39% report EBIT impact), BCG (~5% 'future-built' vs ~60% 'laggards'), and MIT NANDA (~95% of pilots show no measurable P&L return). The numbers are volatile; the pattern is durable.
- 3The root cause is the 'learning gap' / operating model, not model quality — pilots stall because the workflow around the tool never changes ('pilot purgatory').
- 4BCG's 10-20-70 rule locates the value: ~10% is algorithms, ~20% tech and data, and ~70% is people and process — the part executives own and most organizations under-fund.
- 5The durable diagnostic frame: 'if pilots aren't moving EBIT, the problem is rarely the tech.' Interrogate workflow, focus, measurement, and ownership before the technology.
- 6This is good news for leaders: an operating-model gap is within your control in a way a model-quality gap never would be — close it with focus, workflow redesign, governance ownership, and value-based measurement.
Quiz
Lock in what you learned
Check your understanding
0 / 4 answered
1.Three 2025 studies (McKinsey, BCG, MIT NANDA) are cited together to establish the 'adoption–value gap.' What is the main point of citing all three rather than one?
2.A division reports its GenAI pilot 'isn't delivering' and asks to switch to a newer, more powerful model. Based on this lesson, what should the executive ask first?
3.BCG's 10-20-70 rule allocates AI effort and value as roughly 10% algorithms, 20% technology and data, and 70% people and process. Why does the lesson call the 70% 'good news' for executives?
4.McKinsey's 'gen AI paradox' helps explain pilot purgatory. What does it describe?
Go deeper
Hand-picked sources to keep learning
Source for the ~88% adoption / ~39% EBIT-impact figures and the 'gen AI paradox'. Re-verify the live numbers each survey cycle.
Source for the ~5% 'future-built' vs ~60% 'laggards' split and the leader-vs-laggard financial gap (1.7×/1.6×/3.6×).
Coverage of the GenAI Divide study: the ~95% figure, the 'learning gap' root cause, and the buy (~67%) vs build success finding.
Source for workflow redesign having the biggest effect on EBIT, and only ~21% of firms having redesigned a workflow.
The 10-20-70 rule: ~10% algorithms, ~20% tech & data, ~70% people & process — the framework at the heart of this lesson.
Source for under-investment in change management (~37%) and rising pilot-abandonment rates; useful for the 'pilot purgatory' diagnosis.