Software engineers talk about technical debt: the shortcuts taken today that make every change harder tomorrow. Delivery operations accumulate the same thing, and it is just as invisible on a P&L, until it is not.
What operational debt looks like
- The route knowledge that lives entirely in one driver's head, so their holiday becomes a service crisis.
- The manifest workaround everyone does but nobody has written down, which breaks the day a new starter follows the official process.
- The van allocation that "everyone knows", until the person who knows it is off sick.
- The customer arrangement agreed verbally with a depot manager who has since moved on.
- The spreadsheet that only one person can update, feeding decisions everyone depends on.
None of these costs anything today. That is exactly what makes them debt: the cost is deferred, and it compounds.
How it accumulates
Operational debt is not caused by laziness. It is caused by success under pressure. When volumes spike, you do what works and move on. The workaround that saved peak becomes the process. The person who stepped up becomes the single point of failure. Six months later the operation runs, but nobody can quite explain how, and nothing can change without something breaking.
The tell-tale symptom is fragility disguised as efficiency: the operation performs well on a normal day and disproportionately badly on an abnormal one. Efficient and fragile is not the same as good.
Paying it down
You pay down operational debt the same way you pay down any debt: deliberately, a little at a time, starting with the most expensive.
- Find the single points of failure. For each person, ask what breaks if they disappear for two weeks. The answers are your priority list.
- Write down the real process, not the official one. Documentation that describes what actually happens is worth ten polished procedures that nobody follows.
- Make information survive people. Route notes, customer arrangements, depot contacts and rate agreements belong in systems, not in heads and inboxes.
- Rehearse failure. The first time a key driver is absent should not be the first time you discover what their absence costs.
The strategic point
Operational debt is also where technology decisions should start. The right question is never "what can we automate?" It is "where does information die in our operation, and what would stop that?" That framing is central to how we think about advisory work and to the products in our ventures portfolio.