Don't Book the Cut Before the Work Disappears

The workforce plan that books next year’s AI saving from a capability forecast is a common artifact: headcount down by a percentage, signed off before any workflow has been decomposed. McKinsey’s August survey supplies the pair of numbers that should sit next to it. This year 39% of respondents expect AI-related headcount declines in the year ahead, up from 32% a year ago. Last year 32% expected declines, and 14% went on to report them. Expectation rose seven points while reported reality came in at under half the forecast rate.

One year-pair from one survey proves no trend, and I won’t pretend it does. What it provides is a warning label for that artifact. The argument for that label isn’t the survey; it’s the mechanism the survey is consistent with, and the mechanism is old.

A job is a bundle of tasks, and automation eats tasks, not bundles. The model drafts the letter; a human still decides the hard cases, works the exception queue, answers for the output, and does the coordination that never appeared in any task inventory. What disappears is a percentage of each person’s day, scattered, and scattered percentages don’t concentrate into a removable position by themselves. Concentrating them requires reorganizing the work, which is exactly the slow institutional labor pilots skip and diffusion demands . Meanwhile the same tools generate new tasks: review of machine output, evals and tripwires , a new incident class. The ledger has two columns, and capability forecasts read only one.

Note what this does not contradict. A senior driving agents can genuinely out-ship a senior and three juniors ; demonstrated substitution inside a bounded workflow is real, and the arithmetic pays this quarter. The gap is between that observation and an enterprise-wide reduction inferred from it. Bounded substitution is evidence about the workflow you measured. The org-wide cut extrapolates it across bundles nobody has decomposed, and that extrapolation is the step that keeps coming in at under half.

Now the strongest case for the other side: staffing has lead times. Hiring pipelines, budget cycles, and attrition planning all run on forecasts, and a rule of “no workforce planning until proof” guarantees overstaffing in any world where the cuts eventually arrive. Right. So give the forecast the jobs forecasts can hold: scenarios, contingent requisitions, replacement-approval gates, slower backfill on roles the models plausibly thin. What the forecast doesn’t get to govern is the irreversible acts: the layoff, and its quieter twin, the booked saving that finance builds next year on. A booked-but-unrealized reduction is corrosive in a specific way. Teams run short against savings that never materialized, absorb the new verification work uncounted, and when the number misses, the whole program wears the failure, which the bench you stopped filling then compounds. The org that cuts on forecast pays twice: once in the shortfall and once in the rebuild.

So write the promotion rule from scenario to plan, per workflow, decidably. Task elimination observed at representative volume: this queue or review step no longer routes to humans, measured across a full cycle’s case mix, including the bad weeks. Service levels held against named tolerances (error rate, latency, escalation volume) over a fixed window agreed before the change, not after. And the residual netted out: total human touch-time on the workflow, including the new review, exception, and coordination work the change created, down by enough concentrated capacity to equal actual positions rather than confetti. Three tests, thresholds written in advance. A workflow that passes them supports a reduction through attrition with a clear conscience. A workflow that hasn’t been run through them supports a scenario, and the deck should say which one it’s holding.

The board will read about AI layoffs weekly and ask why yours are slower. The answer is the survey’s own shape plus one question: expectations up seven points, reported declines at under half the forecast rate, so which side of that gap should our balance sheet be on? Throughput, tracked honestly , will tell you when the work has actually disappeared. Until it does, the saving is a hypothesis, and hypotheses don’t belong on the income statement.