In 1992, software developer Ward Cunningham gave engineering a piece of vocabulary that changed how the industry worked: technical debt. The idea was simple. A shortcut taken today has to be paid back later, with interest, in the form of harder changes and slower delivery. Naming it made it manageable. You can’t govern what you can’t name. Operations has never had the equivalent and it shows. Every operational leader has felt it: the process that’s slower than it should be for reasons nobody can quite pin down. The improvement project that keeps stalling on the same invisible obstacle. The team that’s genuinely working hard and somehow moving backwards. It has a name. It’s process debt. And every operation carries it.
What process debt actually is
Process debt is the accumulated cost of shortcuts, workarounds, and exceptions accepted at some point for good short-term reasons and never paid back. Like financial debt, it accrues interest. That interest shows up as longer cycle times, higher exception-handling load, and a slow drag on every improvement initiative.
It takes four forms.
- Workaround debt: the temporary fix that became permanent. The Excel step someone added in 2019 to bridge a gap in the ERP. The manual approval loop introduced during a leadership change. Each was a reasonable decision at the time. None was ever revisited.
- Exception debt: special cases absorbed rather than resolved. One customer’s non-standard payment terms. One region’s slightly different approval hierarchy. Individually invisible; collectively, they turn a standard process into fifty overlapping variants that no one has mapped.
- Handoff debt: steps that exist only because two systems don’t talk to each other. A person copying values from one screen to another. A weekly reconciliation that reconciles the same data twice. The step doesn’t add value; it bridges an integration gap that was never closed.
- Visibility debt: parts of the process nobody instrumented. Cycle times inside black-box stages. Approvals that happen “somewhere in email.” Anything you know is happening but can’t measure. This is the most expensive category, because it hides all the others.
Why every operation has it
Process debt isn’t a failure of discipline. It’s the natural consequence of running a business under time pressure. Every operation makes trade-offs between short-term throughput and long-term maintainability and every operation, over time, tilts toward throughput. That’s not bad management. That’s what management looks like when the quarter is closing.
How to recognise the symptoms early
Four patterns tend to appear together, months before anyone connects them:
- Cycle time creeps up quietly, without a clear cause
- The number of “just this one” exceptions rises each quarter
- Tribal knowledge concentrates in fewer and fewer people
- Improvement projects deliver less than the business case promised
If you’re seeing two of these, you’re carrying more process debt than you think.
Debt worth paying, debt worth living with
Not all process debt should be paid down. The right frame is interest rate. High-frequency, high-friction debt (a workaround that fires 500 times a week) has to be paid down. The compounding cost is enormous. Low-frequency, contained debt (a workaround that fires monthly for one edge case) may cost more to fix than to live with.
The mistake most operations make isn’t tolerating debt. It’s not knowing which debt they’re carrying.
A practical first step
Build a process debt register, the operations equivalent of a technical debt register. For each operational process, list every workaround, exception, handoff, and unmeasured step. Rank by two dimensions: frequency of occurrence and friction created. The top-right quadrant is what you pay down first.
Most teams can’t do this by memory. That’s what process mining is for: it surfaces the register you couldn’t build manually, from the event log you already have.
Sparkhs’s Celonis Certified consultants help operational leaders quantify their process debt for the first time, and decide what to pay down.