Every tech leader knows technical debt. That comment in the code that says "fix this later." The workaround that became permanent. The system nobody wants to touch because changing one thing breaks three others. 

We budget for it. We schedule sprints around it. We present it to the board. 

But there's a second debt accumulating in parallel — and it never shows up in any audit. 

Technical debt starts small. A quick fix shipped under deadline pressure. A legacy system kept running past its useful life. An integration built for yesterday's architecture. None of it felt irresponsible in the moment. Each decision made sense given the constraints. Now as that debt accumulates migrating to a new technology becomes more expense and with greater risk. 

Management debt accumulates the same way. A difficult conversation postponed because the timing wasn't right. A decision made without explanation that people are still guessing at six months later. Two people sharing one role because no one was willing to choose. A retention offer quietly matched — that everyone already knows about — which just taught your whole team that threatening to quit is the best, if not only, way to get a raise or promotion. 

None of it seemed urgent when it happened. Reasonable trade-offs in the moment. 

But the interest compounds. 

Ben Horowitz at Andreessen Horowitz coined the term years ago, and the pattern he described is still the most accurate: management debt doesn't announce itself. It just makes everything slower, heavier, and harder to diagnose. Decisions take longer. People make assumptions instead of asking questions. Tension builds in places that were never addressed directly. You can feel it before you can name it. 

Here's what makes it dangerous: technical debt throws errors. You get a signal. Management debt just makes the whole system feel like it's running through mud — and leaders are often the last to see it because they're the ones who created it. 

I've been on projects where the technical foundation was solid, the talent was strong, and the project still struggled. Management debt was the hidden variable every time. 

The audit question isn't just "what's in our backlog?" 

It's: 

• What conversations have we been postponing? 

• Do you have the decisions on major projects and initiatives documented on why and who agreed? 

• What are people working around instead of fixing? 

You can refactor code. You can rewrite systems. You can migrate to a new platform. 

You can't refactor your way out of management debt. You have to have the conversation.