Everyone knows what technical debt is. Shortcuts in the code, deferred upgrades, the migration you keep promising to do. It has a name, a backlog, sometimes even a budget line.
Operational debt is the same idea applied to how a team actually runs, and it's sneakier because it rarely shows up in a ticket. It's the runbook that lives in one person's head. The "we've always done it this way" that nobody can explain. The approval step that exists because of an incident in 2019 that no one remembers. None of it breaks loudly. It just quietly taxes everything.
You feel it as friction. Onboarding takes too long. The same questions get re-answered every month. A simple change needs three people who happen to be on vacation. Each instance is small, so it never makes the priority list — and that's exactly why it compounds.
The fix isn't heroics, it's hygiene. Write the thing down. Define who owns it. Standardize the boring parts so judgment gets spent where it matters. Retire the approval no one can justify. I've found that paying down a little operational debt every month does more for a team's velocity than most reorganizations.
The hard part is that it's invisible until you name it. Reliable operations look effortless from the outside, which means the work that creates them is easy to underfund. Part of leading well is making that invisible work legible — so the people doing it get credit, and the debt stops quietly accruing.
