Software developers have a useful phrase: technical debt. It describes the shortcuts, the quick fixes and the “we’ll tidy it up later” decisions that accumulate in a codebase until everything new becomes slow and risky to build. The phrase matters because naming the problem lets a team see it, talk about it, and decide to pay it down. Businesses have exactly the same phenomenon in how they operate. It just does not have a name, so it builds up unnoticed and unaddressed. Call it process debt.
How it accumulates
Process debt builds the same way technical debt does: one reasonable shortcut at a time. A workaround for an urgent problem becomes permanent. A step gets added to fix a one-off and never removed. A new tool gets bolted on beside the old one instead of replacing it. An approval is introduced for a situation that no longer exists. None of these is wrong in the moment. Each is a sensible local decision. But they compound, and over a few years they leave you with operations that nobody designed and nobody fully understands — a tangle that works, but only just, and only because people have memorised the workarounds.
What it costs
Like its technical cousin, process debt charges interest. The interest is paid in the slow, daily friction of getting anything done.
- Everything takes longer. Simple tasks route through unnecessary steps because removing them was never anyone’s job.
- Change gets scary. Nobody is quite sure what depends on what, so improving anything feels risky, and so nobody does.
- New people drown. Onboarding means learning a pile of undocumented exceptions, because the real process bears little resemblance to the official one.
- Mistakes hide in the seams. The handoffs nobody owns and the steps nobody understands are exactly where things fall through.
Why it goes unpaid
Technical debt at least gets discussed, because engineers feel it constantly and have the language to raise it. Process debt is worse off, because it is invisible and nameless. There is no line in any budget for “the way we do things has quietly become a mess.” It does not announce itself; it just makes everything a little harder, forever, and everyone adapts to the friction until they stop noticing it is there. You cannot fix a problem the organisation has no words for.
Paying it down
The fix starts with naming it, which is most of why the phrase is useful. Once a team can say “that’s process debt,” they can treat it the way good engineers treat the technical kind: deliberately, a bit at a time. Map how a painful process actually works today. Find the steps that exist for no current reason and remove them. Replace the workarounds with something designed on purpose. You do not need a transformation programme; you need permission to question the accumulated “this is just how we do it” and the discipline to tidy a corner of it regularly.
Every business carries process debt, and most carry far more than they realise, because they have never had a name to hang it on. Give it one. You cannot pay down a debt you refuse to see.