Most enterprises report AI productivity gains, yet 94% see no significant business value. Here is EY's 3-shift framework for converting what you saved into what your CFO actually tracks.
Published
Last Modified
Topic
AI Use Cases
Author
Amanda Miller, Content Writer

TLDR: Most enterprises are generating AI productivity gains but failing to convert them into measurable enterprise value. EY's Global AI Consulting Leader Dan Diasio, speaking on the Emerj AI in Business Podcast, identified three strategic shifts that separate organizations realizing business-level outcomes from those stuck collecting activity metrics. The gap is not technology; it is reinvestment strategy, attribution discipline, and operating model redesign.
Best For: COOs, CFOs, and VP Operations at mid-to-large enterprises who have active AI deployments generating visible productivity wins but cannot yet show those wins on the balance sheet. Also valuable for transformation leads tasked with converting departmental AI success stories into enterprise-level ROI narratives for the board.
Enterprise AI value creation is the process of converting AI-generated productivity gains into measurable improvements in business outcomes, operating margins, and competitive positioning. Most enterprises are generating some form of productivity gain from their AI deployments, but the gains stop at the departmental level and never aggregate into outcomes that show up in quarterly results. The distinction between productivity and enterprise value is not semantic; it is the gap that explains why companies can simultaneously report high AI adoption rates and flat operating performance.
The Productivity Gap: What the Numbers Actually Show
AI-driven productivity gains are now widespread. According to the EY AI Pulse Survey Wave 4, 96% of AI-investing organizations now report at least some AI-driven productivity gains over the past year, and 57% describe those gains as significant. These are the highest figures EY has recorded across four consecutive waves of the survey. On the surface, they suggest that AI deployment is working.
Dig one level deeper and the picture changes. The same survey found that 65% of senior leaders at AI-investing organizations admit their organization struggles to tie certain productivity gains directly to AI adoption. Even among executives who believe the gains are real, 63% say other senior leaders at their organization do not consistently attribute productivity improvements to AI. And 92% agree that their organization needs more training on how to report on AI-driven productivity gains to demonstrate the technology's value.
This is not a measurement failure. It is a value conversion failure. The AI is generating efficiency in pockets, but those pockets are not connected to the outcomes that matter to a CFO or a board: cost-to-serve, revenue per employee, customer retention, or operating margin.
McKinsey's State of AI research confirms the same structural divide. Nearly nine in ten companies have deployed AI in at least one business function. Yet 94% report not seeing significant value from those investments, and only 39% observe any impact on EBIT. Nearly two-thirds of respondents say their organizations have not begun scaling AI across the enterprise. The scaling gap, not the technology gap, is what holds most enterprises back.
Before addressing how to close this gap, it is worth distinguishing between AI productivity and enterprise AI value. Productivity is a departmental metric: fewer manual steps, faster cycle times, fewer errors in a single process. Enterprise value is a business metric: lower cost-to-serve across a product line, higher revenue per employee across a business unit, or a measurably better customer outcome that shows up in retention data. Most AI deployments produce the first. Very few produce the second, without deliberate reinvestment strategy.
Why Measurement Is Only Part of the Answer
Assembly has covered how to measure AI ROI beyond tool adoption, and measurement discipline is the right starting point. But measurement alone does not generate enterprise value. Knowing that an AP automation tool reduced invoice processing time by 40% does not automatically redirect the recovered capacity toward something that increases revenue or reduces risk. That redirection requires a reinvestment decision, and most enterprises are not making it deliberately.
Dan Diasio, EY's Global AI Consulting Leader and Americas Consulting CTO, put it precisely in his March 2026 appearance on the Emerj AI in Business Podcast: "Productivity gains are usually framed around what is removed: hours of tasks and money saved. For many managers, it's easier to first drive AI adoption, which is crucial and easier to measure. We must challenge ourselves to consider what is added, the value-added activities, the innovation, the outcomes that were always discussed as a possibility off on the horizon that never seemed to arrive until now."
That is about as clearly as anyone has put it. The productivity gains are real. What is missing is the organizational decision to redeploy them toward something that matters to the business.
The 3 Shifts That Separate Enterprise Value Leaders From Productivity Reporters
Shift 1: From Productivity Capture to Deliberate Reinvestment
This one is about strategy. It requires changing what the organization does with the time and capacity that AI frees up, rather than recording that the savings occurred and moving on.
The instinctive response to AI-generated productivity gains is to capture them as cost reductions: headcount attrition without backfills, vendor contract reductions, or efficiency ratios that look better on a budget dashboard. EY's research suggests this is the wrong response. Organizations that are reallocating AI gains toward growth, workforce reinvention, and competitive advantage, rather than treating them as a cost-reduction harvest, are the ones seeing enterprise-level impact.
Bank of America made a different call. Rather than using AI to reduce its 200,000-plus employee workforce, the bank gave 213,000 employees AI tools explicitly to boost growth, not to replace jobs. The Academy, the bank's internal learning and development organization, has since reported a 44% internal mobility rate, with employees moving into higher-value roles. The AI-driven productivity did not show up as headcount reduction. It showed up as workforce capability that the bank reinvested in client-facing growth activity.
Bernard Hampton, who leads The Academy, explained the logic in a recent episode of the MIT Sloan Management Review's "Me, Myself, and AI" podcast: the program is "laser-focused on workforce agility, which means building the right skills in the right roles faster." That is reinvestment. The AI reduces time spent on lower-complexity tasks; the organization redirects that time toward capabilities it needs to compete.
For operations leaders at mid-to-large enterprises, the reinvestment question is concrete: when an AI deployment frees up 20% of a team's weekly capacity, what does the team do with that 20%? If the answer is "we recorded the saving and moved on," the productivity gain will never become enterprise value. If the answer is "we redeployed those hours toward the workflow problem we never had time to solve," there is a pathway to a measurable business outcome.
Shift 2: From Attribution Confusion to Accountability Architecture
This shift is structural and less glamorous. It requires building an accountability architecture around AI investments that connects individual deployments to business-level metrics before deployment begins, not after.
Here is the measurement bind the EY data describes: 88% of senior leaders are evaluated on AI-driven productivity as a key metric, but 65% simultaneously struggle to tie gains directly to AI adoption. Leaders are held accountable for outcomes they cannot reliably attribute. So they report what they can see: deployment counts, adoption rates, hours saved. Not business outcomes.
Diasio's framework for closing this loop centers on what EY calls the "visibility trap": the tendency of organizations to focus on metrics that are easy to see (logins, automations triggered, tickets processed) rather than metrics that matter to the business (margin improvement, capacity redirected, error rate reduction across a product line). Escaping the visibility trap requires building a measurement architecture during the business case phase, not the deployment phase.
For enterprise leaders, this means starting any AI transformation with a structured readiness assessment that includes a clear definition of the outcome metrics the deployment is intended to move. Not "efficiency" as an abstraction, but a specific percentage reduction in a specific cycle time that connects to a specific line item on the cost-to-serve dashboard.
McKinsey's analysis of high-performing AI adopters identifies the same pattern. What separates winners is not access to better models; it is the redesign of work around those models, including a clear accountability structure that links each AI deployment to a business metric that appears in management reporting.
Shift 3: From Process Automation to Operating Model Redesign
This one is the hardest. It requires moving beyond automating existing workflows toward redesigning how the business runs at a structural level.
Most enterprise AI deployments in 2024 and 2025 were automation plays: take an existing process and make it faster or cheaper. That approach generates productivity, but it does not generate competitive advantage because it only makes the same work more efficient. Real enterprise value comes from redesigning which work gets done, by whom, and in what sequence, using AI as a structural input to the operating model, not a bolt-on efficiency layer.
Diasio described this shift in his Emerj conversation as the difference between "automating yesterday's processes" and "redesigning the enterprise for differentiation and growth." Organizations that remain in the first mode will see productivity gains that competitors can replicate as soon as they adopt the same tools. Organizations that move to the second mode are redesigning their operating model in ways that take longer to copy.
McKinsey's research on AI maturity levels shows a meaningful outcome difference at the highest maturity tier. Companies at the "business building" level of AI maturity, where AI is embedded in how the business competes rather than just how it operates, showed a $180,000 increase in median revenue per employee between 2023 and 2025, a 52% jump compared to the maturity level below.
The practical distinction for enterprise leaders is between using AI to do the same work faster and using AI to do work that was previously impossible or uneconomical. The first is productivity. The second is operating model redesign. A structured AI transformation framework gives leaders the structure to pursue the second, but only when it is built around a business model question rather than a technology deployment question.
The Budget Reality: Why Investment Scale Determines Value Return
The EY AI Pulse Survey data reveals a pattern that operations leaders should take seriously when building the business case for deeper AI investment. Among organizations currently investing $10 million or more in AI, 71% report significant AI-driven productivity gains. Among organizations investing less than that threshold, the figure drops to 52%. Investment scale is not just correlated with better outcomes; it appears to be a precondition for moving from marginal productivity to enterprise-level impact.
There is a meaningful gap between what enterprise leaders say they will invest and what they actually do. The EY survey found that a year ago, 65% of senior leaders expected their organizations to invest at least $1 million in AI in the following year. The actual figure when that year arrived was 58%. At the $10 million threshold, a year ago 34% said they would invest at that level; today only 23% actually do.
The consequence is straightforward: organizations that are vocal about AI ambition but cautious about AI investment are the ones most likely to see productivity gains that never aggregate into business outcomes. The scale of investment is what allows organizations to move from point-solution pilots to enterprise-wide deployment patterns, and it is enterprise-wide deployment that converts departmental productivity into operating model change.
Diasio's advice for executive teams facing this dynamic is to connect AI investment goals explicitly to business model goals, not just to efficiency targets. Organizations that pair "we will invest X in AI this year" with "this investment will move metric Y in business unit Z by a defined amount" are more likely to sustain the investment discipline needed to get to enterprise value. EY's research found that senior leaders at organizations with 25% or more of total budget committed to AI report 86% positive ROI in product innovation, up from 76% the year prior.
The Case Against Using AI Gains as a Headcount Arbitrage
Both EY's research and Diasio's Emerj conversation make the same point: treating AI productivity gains as a headcount reduction mechanism is a strategic mistake that limits how much enterprise value you actually capture.
The logic is counterintuitive but well-supported. When organizations use AI to eliminate roles without redesigning what the remaining workforce does, they capture a one-time efficiency saving but do not build the new capabilities that AI can enable. They get a cost reduction. They do not get a competitive capability.
Bank of America's approach demonstrates the alternative. By directing AI-generated capacity toward upskilling and internal mobility rather than attrition, the bank built a workforce capability asset that shows up not in headcount ratios but in its ability to fill roles faster and allocate talent more flexibly. The 44% internal mobility rate is an operating model outcome that no cost-reduction strategy would have produced.
This matters for enterprise leaders because the board conversation about AI is often framed as a question about headcount. The more productive framing, supported by the evidence, is a question about where to redeploy the organizational capacity that AI creates. That redeployment, done deliberately and at sufficient scale, is what produces the kind of measurable AI ROI transformation results that appear in business performance metrics rather than just in operations dashboards.
5 Questions Every COO Should Ask Before the Next AI Investment Cycle
The following questions map to the three value conversion shifts described above. They are intended as a diagnostic tool for operations leaders preparing the next phase of their AI investment cycle.
Question | Shift It Addresses | What a Good Answer Looks Like |
|---|---|---|
Where will we redeploy the capacity this AI frees up? | Reinvestment | A specific workflow or initiative, with an owner and a timeline |
What business metric will this deployment move, and by how much? | Attribution | A named metric in management reporting with a baseline and target |
Are we making existing work faster, or redesigning what work we do? | Operating Model | Evidence that the deployment changes role structure, not just task speed |
How will we sustain investment at the scale needed to reach enterprise-level impact? | Investment Discipline | A multi-year budget commitment tied to business case milestones |
How will we know when a productivity gain has converted into enterprise value? | Measurement Architecture | A defined endpoint metric that connects operational gains to business outcomes |
These questions are most useful when answered before deployment begins. Trying to retrofit attribution and reinvestment strategy after the fact is harder and produces less reliable results.
Common Objections Operations Leaders Raise
"Our AI deployments are already generating real savings. Isn't that enough?"
Departmental savings are a necessary first step, not a finished result. The challenge is that savings at the process level do not automatically aggregate into outcomes at the business level. Unless those savings are tracked through to their impact on cost-to-serve, margin, or revenue capacity, they remain productivity metrics rather than enterprise value. Most organizations that believe their AI is "working" based on savings data would find, with closer analysis, that those savings have not changed any metric their CFO watches.
"We don't have the budget scale that EY's research suggests is needed."
Scale thresholds are averages, not requirements. The EY data shows that organizations investing more see better outcomes on average, but the underlying driver is discipline, not budget size. A mid-market enterprise that deploys AI in one core workflow, measures it rigorously against a defined business outcome, and reinvests the gains into a second workflow can build enterprise-level impact incrementally. The risk is not small investment; it is unfocused investment spread across too many pilots with no reinvestment plan.
"Our executive team still sees AI primarily through a cost-reduction lens. How do we shift that?"
The most effective approach is to build the first use case around a revenue or growth metric rather than a cost metric. When the first measurable enterprise AI outcome is "we expanded capacity in our highest-margin product line without adding headcount," the conversation about AI's role shifts from cost arbitrage to growth enabler. That shift in framing, supported by a single concrete result, tends to change how senior leaders think about the reinvestment question.
Frequently Asked Questions
What does enterprise AI value mean, and how is it different from AI productivity?
Enterprise AI value refers to measurable improvements in business-level outcomes such as operating margin, revenue per employee, or customer retention that result from AI deployments. AI productivity is a departmental metric: faster cycle times, fewer errors, or reduced manual effort. According to EY's AI Pulse Survey, 96% of organizations report productivity gains, but far fewer have converted those gains into outcomes visible on the balance sheet.
Why do so many enterprises report AI productivity gains but not enterprise value?
Most AI deployments automate existing processes without redesigning what work gets done or where recaptured capacity goes. According to McKinsey's State of AI research, 94% of organizations report not seeing significant value despite widespread deployment. The core gap is a failure to reinvest productivity gains deliberately into business model outcomes rather than treating them as one-time efficiency savings.
What is the "visibility trap" in enterprise AI deployment?
The visibility trap is EY's term for organizations that measure AI success through easy-to-see activity metrics, including user adoption rates, automations triggered, and hours saved, rather than through business outcomes. Dan Diasio of EY, speaking on the Emerj AI in Business Podcast, describes escaping the trap as a prerequisite for converting AI pilots into enterprise-level business results.
What are the three shifts EY recommends to convert AI productivity into enterprise value?
EY identifies three strategic shifts: first, moving from productivity capture to deliberate reinvestment of freed capacity into higher-value work; second, building an attribution architecture that links AI deployments to business metrics before deployment, not after; third, redesigning the operating model rather than simply automating existing processes. Each shift addresses a different layer of the value conversion problem organizations face after initial AI deployment succeeds.
How much should an enterprise invest in AI to see significant productivity gains?
According to EY's Wave 4 AI Pulse Survey, organizations investing $10 million or more report significant productivity gains at a 71% rate versus 52% for those investing less. However, for mid-market enterprises, the more relevant variable is investment focus rather than absolute scale. Concentrated investment in one or two core workflows with rigorous measurement outperforms fragmented spending across many pilots.
What happens to AI productivity gains when organizations use them for headcount reduction?
Organizations that route AI gains primarily into headcount attrition capture a one-time cost saving but do not build the new capabilities that AI can enable. Bank of America's alternative, giving 213,000 employees AI tools to boost growth and upskilling them through its Academy program, produced a 44% internal mobility rate and measurable workforce agility improvements that show up in business performance rather than headcount ratios.
What is the difference between automating processes and redesigning the operating model?
Process automation makes existing work faster. Operating model redesign changes which work gets done, by whom, and in what sequence, using AI as a structural input to how the business competes. Dan Diasio distinguishes between "automating yesterday's processes" and "redesigning the enterprise for differentiation." McKinsey research shows companies at the highest AI maturity level, where AI is embedded in the operating model, achieve a 52% higher revenue-per-employee metric than the tier below.
Why is the budget gap between AI investment intentions and actual spending a problem for enterprise value?
EY found that 65% of senior leaders expected to invest at least $1 million in AI in the following year, but only 58% actually did. At the $10 million threshold, the expected-to-actual ratio is even larger. This gap matters because enterprise-level value conversion requires sustained, scaled investment over multiple deployment cycles. Organizations that cut investment midway through a transformation tend to capture departmental productivity without reaching the operating model redesign phase where enterprise value appears.
How should enterprises frame the AI reinvestment question for their CFO?
Frame reinvestment as a capacity reallocation decision rather than a cost-reduction outcome. The question for the CFO is not "how much did we save?" but "where did the recaptured capacity go, and what did it produce?" Linking each AI deployment to a specific business metric the CFO already tracks, before deployment begins, makes this conversation more productive. EY data shows that organizations with 25% or more of total budget committed to AI report 86% positive ROI in product innovation.
What is the role of workforce reinvention in enterprise AI value creation?
Workforce reinvention is the reinvestment of AI-generated capacity into building the higher-value capabilities that AI cannot yet perform autonomously. According to the MIT Sloan "Me, Myself, and AI" podcast featuring Bank of America's Bernard Hampton, the goal is "workforce agility: building the right skills in the right roles faster." When AI frees up time from lower-complexity tasks, organizations that redirect it into capability development compound the value of the initial AI investment.
What does an attribution architecture for AI investments look like in practice?
An attribution architecture connects each AI deployment to a specific business metric at the time of business case approval, assigns a metric owner accountable for reporting it, establishes a baseline and target, and creates a feedback loop that reports results in management language rather than AI-activity language. It typically mirrors existing performance management systems rather than creating a separate AI metrics layer. The McKinsey analysis of leading AI adopters identifies this kind of metric architecture as a key differentiator among organizations that convert AI investment into enterprise performance.
How long does it typically take to convert AI productivity gains into measurable enterprise value?
The timeline depends on the reinvestment strategy and operating model complexity. Organizations that reinvest productivity gains into a second and third use case within the same business unit tend to see cumulative enterprise-level impact within 12 to 18 months of the initial deployment. Operating model redesign, where the business fundamentally changes which work AI handles versus which work humans handle, typically takes 24 to 36 months to show up in business performance metrics. Enterprises that treat each deployment as independent, with no reinvestment plan, may never aggregate individual gains into enterprise value.
What is the "mindset, skill set, tool set" alignment that EY recommends?
Dan Diasio uses this three-part framework to describe the organizational conditions required for enterprise AI value creation. Mindset alignment means leaders at every level understand that AI is a business transformation tool, not a cost-reduction mechanism. Skill set alignment means the workforce has the capability to use AI tools effectively and to do the higher-value work that AI creates capacity for. Tool set alignment means the technology stack is connected to core business processes rather than running in isolated departmental deployments. All three must be in place simultaneously for productivity to convert into enterprise value.
How does enterprise AI value creation differ across traditional industries versus digital-native companies?
Traditional industries, including manufacturing, logistics, financial services, and professional services, face an additional conversion challenge: their operating models were designed around manual and sequential workflows that AI disrupts structurally rather than incrementally. Digital-native companies can redesign processes more quickly because they have fewer legacy workflow dependencies. For traditional industry enterprises, the operating model redesign phase takes longer and requires more change management investment, but the productivity gains are also larger because the baseline inefficiency is higher.
What is the single most important first step for an enterprise that wants to convert AI productivity into business value?
Define one business outcome metric that a specific AI deployment will move before deployment begins, not after. According to EY's research, the enterprises that struggle most with AI value attribution are those that approved AI deployments based on productivity projections and then tried to retrofit business metrics retroactively. Starting with a structured AI readiness assessment that includes outcome metric definition, not just technology readiness, is the single highest-leverage early step.
When should an enterprise bring in an external AI transformation partner to help with value conversion?
External support becomes most valuable when an enterprise has demonstrated AI productivity gains in at least one function but is struggling to aggregate those gains into enterprise-level business outcomes. This is typically 12 to 24 months into an AI program. Earlier than that, the internal team usually lacks the deployment track record to make external support effective. Later than that, misaligned measurement architectures become harder to correct. An experienced AI transformation partner adds the most value at the reinvestment planning stage, when the productivity gains exist but the reinvestment strategy is not yet defined.
Legal
