The automation ROI that never materializes. What the business case missed.

The business case looked great. The ROI projections were compelling. Leadership signed off. The automation initiative launched on time.

And then the expected returns never showed up.

This happens more often than most organizations want to admit, especially in regulated industries like pharma, healthcare, and financial services. And the reason usually isn't the technology. It's what the business case was built on.

Most automation business cases are built on the documented process. The clean version. The one that assumes every step happens the way it's supposed to, every time, with no exceptions.

But that's not how work actually gets done.

In reality, there are workarounds that exist for reasons nobody documented. There are manual checks that people added because the system doesn't catch everything. There are handoffs that only work because someone picks up the phone and confirms before moving forward. None of that shows up in the business case. But all of it affects the outcome.

When you automate based on the documented version, the savings on paper don't translate to savings in practice. The exceptions don't go away. They just surface somewhere else, often as rework, escalations, or compliance issues that cost more than the original manual process.

The business case didn't fail because the math was wrong. It failed because the inputs were wrong. The process that was modeled wasn't the process that actually existed.

Before building the ROI model, it's worth asking a more fundamental question. Do we truly understand what we're automating? Not the documented version. The real one.

That's where human-centered transformation starts. With the truth about how work actually happens today.