"AI Saved Us Time" Is Not Enough
The ROI lives in what happens next.
Many meetings I’ve been in lately have featured the same flourish: X hours saved using AI tools. The room always eats it up because it makes our AI investment look like it’s paying off.
I get the appeal. For the past couple of years, I’ve been trumpeting the same line: outsource the time-consuming toil to AI so people can do more, better work. I still believe it.
My concern isn’t with “time saved.” It’s a warning about stopping there. Fixate on one metric, and you may limit how much return it can ever achieve.
Saving time doesn’t create value. It creates capacity: open space on the calendar. Whether that space becomes anything depends on what happens next, and “next” is the part that almost no one measures or defines.
So how do we define “next” and work towards maximizing our AI investment? Two simple dimensions point the way.
1. Value
Did the freed-up time create anything?
Saving 20% of an organization’s hours is great, but the win is what fills the gap. Capacity only counts if it turns into work that matters, and that work comes in two flavors:
Deferred work you finally did. The memory leak. A real threat model before the new API shipped. The flaky tests that slowed every release. Valuable things that the organization could have done, but kept putting off.
Work that wasn’t possible before. Yes, good ole capability enablement. A load test you’d never had the capacity to run. Real experimentation. The architecture and resilience work that keeps paying off. New capacity didn’t just help the organization catch up. It moved the boundary of what they could do at all.
Room to think. The most overlooked use of reclaimed time isn’t more output. It’s space. Space to define the right problem. Space for creativity and collaboration. Space for self-care. Dave Laribee calls the alternative the “busy is the new stupid” trap: confusing motion with progress. Reclaimed capacity gives organizations a chance to slow down enough to recharge and think. Sharper judgment, better decisions, and fewer misses come from people who aren’t running on empty.
2. Displacement
Did the work disappear, or just move?
Speeding up one stage of a jammed system doesn’t fix the jam. In fact, I’d argue it pushes work toward the jam faster.
The effort doesn’t vanish. It moves downstream, into review queues, incidents, rework, and support, where the original “we saved time” story can’t see it. Industry telemetry is already showing the pattern: throughput up at the top, review time and incident rates climbing underneath.
Watch for the sneakier version, too. People stop checking AI output carefully because the tool has been reliable (We'll take Automation Bias for $500.) Useful becomes trusted, trusted becomes assumed, and verification becomes optional.
Your Move
Pick one AI rollout your organization is proud of. Do three things:
Write down the valuable work you keep deferring, plus the things your organization never even attempts. That’s your value baseline.
Record today’s downstream numbers: review time, incidents, rework, support load, etc. That’s your displacement baseline.
Put a date on the calendar to come back and check both, and pick it deliberately. DORA’s ROI of AI-assisted Software Development report describes a J-curve, where AI value often dips before it climbs as organizations absorb the learning curve and the tax of verifying AI output. Check too soon, and you’ll mistake that dip for failure. Check only at the time-saved peak, and you’ll declare victory before the real value shows up.
Protect some of the reclaimed time before the backlog claims it. Block it for thinking, learning, and recovery on purpose. If you don’t name it, it disappears.
Next time that slide goes up, and the room nods along, be the person who asks where the hours went, or where they’re going. X hours saved is a great opening line, but make sure it isn’t the whole story.