A head of claims operations walks the executive team through the results of an AI-assisted document review rollout: a sharp, real cut in average review time. The room comes alive over it: not skeptical, enthusiastic. Someone's already running expense-ratio math out loud before she's finished the slide. Someone else wants to know if the same approach works in underwriting. The head of claims tries to steer the conversation toward what else those hours might be worth doing instead of cutting them, but there are three more items on the agenda, 15 minutes left in an hour that's already running long, and a room half-checked-out toward the next meeting.
The cost-savings read isn't wrong. It's just the only idea that got any airtime.
By the following week, the number is sitting in the forecast as a bottom-line improvement, and HR has scheduled a meeting to talk through the actual headcount reductions. Nobody chose this outcome over another one; it's just the one with momentum, and momentum in a room with an hour on the clock beats an idea nobody had time to finish developing. The room did what rooms do under time pressure: it ran with the fastest, most defensible read, and by the time anyone might have asked a second question, the decision was already operational.
This is the mechanism I keep running into with insurance and financial-services leaders working through AI at scale. It isn't that no one owns the question of what to do with freed capacity. Someone owns it, in exactly the moment described above: usually whoever's in the room when the result lands, or Finance once it's in their model. The problem is they're answering a question nobody asked out loud: is this time worth more as a saving, or as something redirected? By default, the answer is savings, because savings is the fastest, most comfortable story a room on the clock can agree on.
There's a harder truth underneath the reflex, too. Even if the head of claims had been able to keep the floor, she probably couldn't have made the case: nobody had set up a way to measure what those hours would be worth doing something else. Under real forecast pressure, with downside risk already sitting in the numbers, the room isn't choosing the fast story over the slow one. It's choosing the only story it actually has data for.
The default doesn't hold up, and two firms now say so independently
Gartner surveyed 350 business executives this spring at companies with at least $1 billion in revenue. Eighty percent of the organizations that had piloted an AI or autonomous technology followed with a workforce reduction. But there was no meaningful ROI difference between companies that cut staff and those that didn't. The strongest returns weren't at the companies that cut deepest; they were at the ones using AI to make people more productive, not to replace them. Gartner's Helen Poitevin put it directly: chasing value through headcount reduction alone leads most organizations toward limited returns, not the returns they modeled.
Deloitte's research puts a number on the other half of that same gap. Eighty-four percent of organizations are increasing their AI investment. Only 20% report meaningful revenue impact. But organizations that redesign the work itself, rather than just removing roles, are roughly twice as likely to exceed their AI ROI expectations, and nearly two and a half times more likely to see real financial gains.
Two firms, two survey populations, the same finding: cutting the role doesn't reliably convert a technology gain into a business gain. Redesigning the work does, by a wide margin. This isn't a values argument about protecting jobs. It's a return argument, made with the same data the cost-saving case leans on.
Why the default survives unquestioned
Part of why this default never gets challenged is that the dashboard isn't built to challenge it. A rollout dashboard answers one question the week the tool launches: did the tool work? It was never built to ask the second question: now that the tool freed something up, what's the best use of it? Nobody updates the dashboard to ask that, because nobody built a version where the question has a place to live.
The result is a familiar split. Leadership sees a rollout that delivered the projected time savings and reads that as ROI, declared and closed. The people managing the work six months later are living inside whatever happened to that time, usually nothing or usually cost-cutting, and see a different number entirely. Both readings are accurate: they're reading two different moments, off two different instruments, and only one of those instruments ever looks past launch week.
This lands harder in insurance and financial services for a specific reason: the executive team is tracking results weekly, which is exactly the speed that produces a room like the one above. A real redesign case takes longer than a week to build. By the time underwriters or claims reviewers could show what redirected hours would be worth against loss ratios or retention, the quarterly external reporting cycle has already locked in the launch-week number as a win, and the budget conversation has moved on.
What interrupts the default
Naming the pattern doesn't fix it, so here's what I'd tell a claims or underwriting leader sitting inside this right now.
Put the redirection case on the roadmap when the rollout is designed, not after the results land. That claims leader's slide only had one story on it because only one story had data behind it. Building the other one is real work: further experimentation and analysis, beyond what it takes to simply validate that the tool works. Naming that work up front, as part of the rollout plan rather than an afterthought raised in the meeting, is what gives the room something to weigh against the savings read before momentum decides for everyone.
Reuse a review cycle you already trust. Regulated organizations already run disciplined quarterly and annual reviews for compliance and audit. Add one standing question to that cadence: what did we say this rollout would free up, and which path, saved or redirected, did it take? You don't need a new process. You need one more question inside a process that already has teeth.
Track what changed in the work, not what changed in usage. A login count says the tool got turned on. It doesn't say whether a reviewer, underwriter, or claims handler is doing anything differently on Thursday than in January: the real measure of whether freed time went anywhere.
The open question underneath this one
There's a third factor sitting under both of these that I don't think the data above fully answers, and I'd rather name it honestly than force a tidy conclusion: why doesn't anyone stop to ask the redirection question at all? Do organizations reward speed and visible activity over the slower work of finding a better use for freed time? Is the savings number just easier to defend than a redirection bet that might not pay off for multiple quarters? I don't have a clean answer, and I'd rather leave the question open than manufacture certainty. It's worth its own room, not a paragraph tacked onto this one.
What the data above does settle is narrower, and it's enough: cutting the role may feel like the safe, obvious way to capture value from AI. Two independent studies now say the opposite is the better path. The next time a rollout result lands in a room, and everyone reaches for the cost-savings read in the same breath, it's worth asking whether anyone had a number for the alternative, or whether the room just did what rooms do.
