The Workflow Dividend

The customer-support study offers strong evidence that AI can raise throughput in a bounded, measurable workflow. It also shows why averages mislead: less experienced agents improved most, while the highest-skilled workers saw smaller speed gains and some quality deterioration. The tool appeared to diffuse practices embodied in high-performing conversations, making the value mechanism partly one of expertise transfer. ¹

The knowledge-worker experiment shows a different boundary. Giving individuals a tool changed a narrow activity—email time—but did not automatically reorganise work. This is precisely what a workflow lens predicts. Individual assistance can create a pocket of capacity while meetings, approvals, hand-offs, service expectations and staffing remain unchanged. ²

The developer trial is a warning against perceived productivity as the sole measure. Participants predicted that AI would make them faster and continued to believe it had, while measured completion time was 19% longer. The sample was small and unusually experienced, and later tools may perform differently. The finding remains important because it exposes the gap between felt fluency and observed outcome. ³⁴

OECD’s 2026 productivity synthesis cites firm-level analysis associating AI use with a short-run labour-productivity increase, but also stresses that adoption definitions are not harmonised, causality is difficult and complementary intangible investment matters. Its broader adoption research likewise treats skills, data, finance, infrastructure and management capability as complements rather than background conditions. The responsible conclusion is not a universal return estimate. It is that leaders must construct local evidence at the level where work and outcomes can actually be observed. ⁵⁷

Provider-native customer telemetry can add useful evidence about usage growth and task mix, but it describes a selected customer population and should not be converted into a universal productivity or return estimate. It is an operating input to investigate, not proof that value has reached the enterprise. ⁸

Before funding a use case, write a one-page theory that links the capability to an enterprise outcome. Start with the baseline: volume, cycle time, quality, cost, risk and current variation. Describe the changed work: which tasks disappear, accelerate or become possible; which hand-offs and decisions change; and what people must do differently.

Then specify the capacity destination. Saved time may be absorbed by higher service levels, more volume, faster revenue, better decisions, reduced contractor spend, fewer errors or a smaller future cost base. Each pathway needs a different measure. If the organisation cannot name the destination, time saved is likely to disappear into work expansion, queues, meetings or unmeasured discretionary effort.

Finally define quality and risk guardrails, full costs and a stop rule. Costs include licences, integration, data preparation, evaluation, human review, change support, monitoring, incidents and model or process maintenance. A use case that looks attractive on inference cost alone can become uneconomic once review and exception handling are visible.

The workflow dividend is therefore not a model benchmark. It is the measured change in the target outcome, adjusted for quality, risk and full operating cost, that can credibly be attributed to the changed workflow.

A credible evaluation begins before deployment. Establish a baseline using the same definitions, population and observation window that will be used after the change. Where possible, use phased rollout, a comparable control group or within-workflow randomisation. Where that is impractical, use a stable interrupted time series and document other changes that could explain the result.

Track a balanced set of measures: outcome, throughput, cycle time, first-pass quality, rework, exception rate, customer or employee impact, control failures, unit cost and total capacity used. Segment results by task and worker experience. An average improvement can conceal harm to expert work, exclusion of difficult cases or a transfer of effort to reviewers and downstream teams.

Separate leading from lagging evidence. Usage, satisfaction and self-reported time saved can guide adoption support. They should not approve scale. Promotion requires observable workflow behaviour and outcome evidence. Finance should validate value claims, while risk and operational owners validate quality and control evidence.

Re-measure after the novelty period. Workarounds, prompt habits, vendor changes, model drift and changing task mix can all alter economics. A workflow that cleared its initial gate should remain subject to periodic value and control review.

Treat AI initiatives as an option portfolio. Early experiments should be cheap and designed to reduce a named uncertainty: technical feasibility, data availability, user behaviour, quality, control effectiveness or unit economics. Money and authority increase only as evidence strengthens.

Use four gates. Discovery confirms the workflow and baseline. Trial tests whether the changed work improves a proximal measure. Controlled production establishes quality, controls and full operating cost under real conditions. Scale requires durable outcome evidence, an operating owner and a capacity-allocation decision.

A stop decision is a sign of portfolio health. Terminate work when the task is too variable, review costs erase the benefit, the workflow cannot absorb saved capacity, adoption requires disproportionate change, or a better non-AI redesign exists. Keeping weak pilots alive creates maintenance debt and obscures the few investments with enterprise potential.

Report portfolio quality through evidence movement: how many hypotheses were tested, what uncertainty was retired, which initiatives advanced or stopped, what value was validated, and where benefits failed to reach the enterprise.

Time savings become value through a management decision. Capacity can absorb unmet demand, improve service, reduce overtime, increase throughput, support training or lower required resources over time. If no destination is chosen, saved minutes fragment across the day and disappear from enterprise accounting.

The destination changes the evidence required. A service-level claim needs queue and response measures. A quality claim needs defects, rework and customer outcomes. A staffing claim needs sustainable workload evidence and a transition plan. A learning claim needs skill progression rather than self-reported confidence.

Team-level experimental evidence suggests AI can alter how expertise is distributed and can enable an individual with AI to match some team outcomes in a product-innovation setting. That is a provocative configuration result, not a general instruction to remove teams. The social, coordination and development functions of teams remain part of the operating decision. ⁹

Finance and operations should therefore agree a capacity ledger before scale: baseline hours and demand, the proposed destination, the mechanism that makes capacity fungible, expected lag, quality guardrails and the owner who will realise the change.

Begin with representative cases sampled across routine work, exceptions and high-consequence edge conditions. Record baseline cycle time, throughput, quality, rework and hand-offs. Define the minimum worthwhile improvement and the quality floor before teams see treatment results.

Where feasible, compare current work, assisted work and a redesigned workflow. Segment by experience because average effects can hide who benefits and who becomes less reliable. The HBS frontier experiment and later customer-support evidence both show why task boundary and worker heterogeneity matter. ¹¹²

Move from trial to operation through an evidence window, not a permanent approval. Continue measuring review burden, exception rate, incident signals, unit cost and the destination of saved capacity. Treat a model, prompt, data, integration or population change as a reason to reassess transportability. NIST’s generative-AI profile supports lifecycle testing and monitoring calibrated to the deployed context. ¹¹

The stop rule should be as specific as the scale rule: terminate or redesign when quality falls below the floor, review consumes the gain, the workflow cannot absorb capacity, risk cannot be bounded or a simpler process change creates a better outcome.

In the first 30 days, choose three material AI-enabled workflows and reconstruct their theory of value. Replace claimed hours saved with a baseline, capacity destination, balanced measures and full-cost estimate. Identify where value currently leaks into review, exceptions or unchanged operating constraints.

By day 60, establish common evidence gates and require a finance, operational and risk sign-off appropriate to each stage. Instrument the chosen workflows so throughput, quality, rework and unit cost can be observed together. Define what result would cause the organisation to stop.

By day 90, make one explicit scale decision, one redesign decision and one stop decision. Reallocate funding based on evidence quality and expected workflow dividend, then publish the assumptions so the executive team can revisit them as models, costs and work change.