Saved hours are not a saving

Eingesparte Stunden sind keine Einsparung

Written by

in

Business cases built on “saved hours” almost never materialize. Not because the math is wrong — but because nobody ever actually takes those hours away from anyone.

Here is the mechanism: when an automation saves someone two hours a day, those hours don’t leave the payroll. The person fills them. The business case assumed a second decision — headcount reduction or redeployment — that nobody modeled and nobody made.

For a few years I ran portfolio management. Colleagues came to request project budget. They brought business cases to justify the investment. Almost every time, the savings were built on reduced effort — not reduced cost. And that distinction is everything. Effort that is never recaptured is not a saving. It is a forecast that never closes.

The structural reason is Project Mode. Once a business case clears the approval gate, it stops being a measurement tool. It becomes a justification artifact, recalculated each funding cycle to keep the numbers acceptable — not to track reality.

Sriram Narayan’s article on Product vs. Project Mode, “Products Over Projects” on martinfowler.com, names the fix: a persistent team that owns the outcome continuously has no gate to hide behind. The business case becomes a live dashboard.

Stop counting saved hours. Start owning the outcome.

Have you ever seen a business case that survived first contact with reality — and if so, what made it different?