Renee Thompson Renee Thompson

Management Debt: The Cost of Staying Scrappy

Growth isn’t what breaks most companies.
What breaks them is what they didn’t build while they were growing.

Management debt starts quietly. A promoted manager without clarity. A decision that gets escalated instead of owned. A system that gets deferred because things are still working.

Then one day, everything is slower. Decisions stall. Your best people are frustrated, and nobody can quite explain why.

That’s not growing pains. It’s accumulated debt coming due.

Your company is growing. Revenue is moving. Headcount is climbing. From the outside it looks like success.

From the inside, your best people are frustrated. Decisions are taking longer than they should and nobody can say exactly why. A question that should take thirty seconds to answer is still unresolved at the end of the day. Hiring is a permanent state of catchup. New hires seem to take forever to ramp. Your managers are escalating things to you that you're fairly sure they should be handling themselves.

No single thing is catastrophically wrong. Everything is slightly more difficult than it used to be, and slightly more difficult than it should be, and it keeps getting worse.

That's not growing pains. That's management debt. And it started accumulating the day someone said we'll worry about that later.

What you deferred, and why it felt right

In the early stage, informality works. When the team is small enough that the founder can see everything, the founder is the operating system. They know who's performing and who isn't. They know what every decision requires. They can course-correct in real time because they're close enough to everything to see it.

You don't need a performance management system when you have twelve people and you can feel the pulse of the organization from your desk. You don't need documented decision rights when the four people who make decisions are in the same room. You don't need a structured onboarding process when a new hire can sit next to someone for a week and learn everything they need to know.

Informality isn't dysfunction at that stage. It's efficiency. It's exactly the right way to operate.

The problem isn't the decision to stay informal. The problem is the moment that decision stops being right, which arrives earlier than almost anyone expects, and quietly, without announcing itself.

The invisible accumulation

Here's what management debt actually is.

Every month your team grows without building the infrastructure to support that growth is a month of debt accumulating. Not financial debt. Structural debt. The kind that doesn't show up on a balance sheet and doesn't trigger an alert. The kind that accumulates in the gap between the organization you are and the systems that organization needs to function.

Your team doubles. The systems don't. Managers get promoted because they were your best individual contributors, which is a completely logical thing to do, but nobody tells them what they're now allowed to own. What decisions are theirs to make. What performance issues they're expected to address directly rather than escalate.

So they do what any reasonable person does in an ambiguous situation. They defer. They escalate. They wait for clarity that never comes because nobody's built the system that would provide it.

Nobody has written the approval policy. So a manager who needs to spend six grand on something genuinely urgent asks their director. The director isn't sure either, so they ask their VP. The VP is in back-to-back meetings and doesn't respond until tomorrow. By the time the answer arrives the moment has passed. Multiply that across every manager in the organization, every week, and you begin to understand what the founder means when they say everything feels slower than it used to.

New hires arrive. Nobody's written the job description precisely enough for the recruiter to screen effectively, so hiring managers spend their time interviewing candidates who were never right for the role. The new hire who does get through arrives to an onboarding process built for a company half the size. They're confused about their role within weeks because the company has already changed shape around them.

None of this feels like a crisis. The company is still growing. Revenue is still moving. The debt is invisible because the consequences haven't yet surfaced as numbers.

But the debt is there. And it's compounding.

The instruments you're not reading

Management debt stays invisible as long as it does for a specific reason. The systems that would make it visible are the same ones that got deprioritised.

You can't measure time to productivity if you never defined what productive looks like in the role. You can't track whether your turnover is a problem or a coincidence if you're not distinguishing between the people you would have fought to keep and the people you were relieved to see go. You can't identify which managers are creating momentum and which are creating drag if you have no framework for evaluating manager effectiveness. You can't see the escalation rate climbing if nobody's tracking how often manager-level decisions are landing on your desk instead of resolving below you.

The debt accumulates in the dark because you deferred building the lights.

But here's the part that matters most, and that almost nobody explains clearly enough.

These metrics don't exist in isolation. They depend on each other. And they all depend on foundations that scaling companies almost universally skip.

To know whether your turnover is a problem, you need to know who your high performers are. To know who your high performers are, you need a performance management system capable of making that distinction. To run a performance management system that actually works, you need role definitions precise enough to say what good looks like in each specific role. And role definitions, job descriptions precise enough to be useful, are the first thing that gets skipped when the team is small and everyone seems to know what they're doing.

So the company that deferred the job descriptions in the early days hasn't just created a hiring problem. It's made it structurally impossible to measure the thing that would tell them their business is in trouble. They can't see the regrettable exits for what they are because they can't define regrettable. They can't define regrettable because they never defined exceptional. They never defined exceptional because they never built the foundation that would make that definition possible.

The cost of that gap isn't abstract. Gallup research puts the cost of replacing a manager or senior leader at up to 200% of their annual salary. Organizations with functioning performance management processes retain top talent at a 44% higher rate than those without. The foundation of that process is knowing what good looks like in each role. That starts with a job description. Which is the thing you skipped.

This isn't an HR problem. It's a visibility problem. And visibility is what every business decision depends on.

What it feels like from the inside

You won't wake up one morning and think “we have a management debt problem.”

If you're reading this and thinking “this doesn't quite sound like us, we're more on top of it than this”, that response is worth paying attention to. Not because it means you're wrong, but because it's the same response every founder has at month eight. The ones who were right say so in retrospect. The ones who were wrong wish someone had pushed harder on the question.

Here's what management debt actually feels like before anyone has named it.

Work that used to flow has become a slog. Decisions that should take minutes are taking days. Your calendar is full of meetings that exist to resolve things that should have resolved themselves. Your best people seem frustrated but can't quite name why. Hiring is always behind, always overwhelming, always a game of catchup you never quite win.

A question that should take thirty seconds to answer is still unresolved at the end of the day. Not because nobody cares. Because nobody knows who has the authority to answer it. So it goes to five people, each of whom redirects it to someone else, and by the time it resolves the person who asked has either improvised a solution or quietly given up. That's not a communication problem. That's a missing system revealing itself.

It feels like burnout. It feels like growing pains. It feels like a hundred small things going wrong simultaneously with no obvious common cause, no single thing you can point to and fix.

That's the signature of management debt- death by a thousand paper cuts, each individually manageable, collectively creating drag that compounds quietly and costs you momentum you can't afford to lose.

Some questions worth sitting with honestly. How long does it take a new hire in your organization to reach full effectiveness in their role? Do you know? Does your HR team? Does the hiring manager? If three people gave you three different answers, that gap is the debt making itself visible. How many decisions required your personal involvement last week that should have resolved below you? How many have been on your calendar for more than one week? The answer to both questions is probably higher than it was six months ago. That trajectory is the signal.

When founders finally name it

Most founders name this problem when revenue has missed projections for three consecutive quarters.

That's far too late.

By the time the revenue line makes the problem impossible to ignore, the debt has been compounding for a year or more. The turnover has been telling you for months. The hiring manager who can't describe what good looks like in the role they're trying to fill has been telling you. The manager who keeps escalating everything upward has been telling you. The HR team that can’t do anything strategic because all they’re doing is hiring has been telling you.

These signals read like HR problems. Inconvenient, worth addressing eventually, not mission-critical right now. They're not HR problems. They're early data on a structural failure that will eventually show up in your revenue line, your delivery dates, and your ability to retain the people who are carrying the organization forward.

The exits aren't random. The people leaving are the ones who can see most clearly that the systems aren't keeping pace. They have options. They leave. What remains, without a structured way to evaluate it, is a workforce that looks intact from the outside and is quietly hollowing from within.

By the time the revenue data makes the argument undeniable, you're not looking at a systems problem. You're looking at the consequences of a systems problem that's been running for twelve to eighteen months unchecked, compounding the whole time.

Why it gets worse faster than you expect

Management debt doesn't scale linearly with headcount. It scales multiplicatively. In some cases exponentially.

Every new hire added to a broken onboarding system compounds the problem. Every manager promoted without clarity about what they own multiplies the decision paralysis. Every process that was never built creates three downstream processes that can't function properly because they depend on the one that doesn't exist.

I've watched this play out in organizations across different industries and different growth trajectories. The infrastructure problems that are manageable at a hundred people become catastrophic at a thousand. A missing policy means nobody knows who can approve a budget. So nobody approves anything. So decisions that should take minutes take days. So the people who need answers stop asking and start improvising. So the improvisation creates inconsistency. So the inconsistency creates conflict. So the conflict escalates upward to a leadership team that's already overwhelmed.

One missing system. Cascading failures across five downstream processes. Multiplied across every function. At the speed of hypergrowth.

WeWork was valued at 47 billion dollars. The reasons for what followed have been exhaustively analysed. But underneath the headlines, one of the things I watched was an organization that had grown faster than any of its systems, people systems included, could bear. The debt became structural. At the speed they were moving, the cost of that wasn't gradual. It was sudden, and it was total.

That's the extreme. Most companies won't go there. But the mechanism is the same whether you have fifty people or five thousand. The speed of growth determines how fast the debt compounds. The size of the ambition determines how much it costs when it does.

The window

Addressing management debt at month six is a fundamentally different problem from addressing it at month eighteen.

At month six the team is still small enough that you can build the systems with relatively low disruption. The managers promoted without clarity can be given clarity before the absence of it has calcified into habits that are hard to change. The onboarding process can be built before multiple cohorts of new hires have normalised the broken version. The decision rights framework can be established before the organization has learned to route everything upward.

At month eighteen you're not building systems. You're rebuilding them while the organization is running at full speed, carrying the habits and workarounds that filled the vacuum left by the systems that were never built. That's a harder, slower, more expensive intervention. Not impossible. But categorically different from what it would have been a year earlier.

The window isn't closing gradually. In a hypergrowth environment, it closes fast.

This is the part where founders push back

This is the point where founders sometimes think: this sounds like an HR person making the case for HR.

It's worth sitting with that objection for a moment.

The argument here isn't that you need more process. It's that without the specific infrastructure described above, you can't see your own risk. You can't measure who your high performers are, so you can't retain them deliberately. You can't define what good looks like in each role, so you can't onboard effectively or evaluate performance accurately. You can't clarify decision rights, so your management layer defaults to escalation and your calendar fills with decisions that should never have reached you.

The cost of that isn't an HR metric. It's a business metric. When you lose a manager you were counting on, replacing them costs up to 200% of their salary. That's before you calculate the productivity loss of their team during the vacancy, the institutional knowledge that walked out with them, or the downstream effect on the people they were leading. For a company of 150 people losing three managers in a year, that's a potential seven-figure event that appears nowhere in the budget because nobody was tracking the conditions that made it inevitable.

The most common plan at this stage is to hire a strong HR leader at 150 people and let them sort it out. That plan has two problems. The first is that 150 people is already late. The second is that the HR leader you hire will spend their first year doing nothing but reactive hiring and damage control because the debt that accumulated before they arrived will consume all of their bandwidth. You won't get the strategic function you needed. You'll get an expensive firefighter.

The argument also isn't that you need to build everything at once. It's that three specific foundations, role definitions, decision rights, and a functional performance framework, are the ones that make everything else possible. Without them you're not staying lean. You're flying blind at increasing speed.

The question isn't whether process slows you down. The right process, built at the right moment, is what allows you to move faster with more people than you can move right now.

The decision that still seems reasonable

The choice to stay informal still makes sense to most founders reading this right now.

The team is small enough. The work is flowing. Building process feels like what corporations do, and you're not a corporation. You'll get to it when things slow down a little.

Things don't slow down. The debt doesn't wait.

The question isn't whether that decision seemed reasonable when you made it.

The question is when the bill will come due.

Read More