Organisational Debt

Steve Blank coined the term in a 2015 blog post, and the framing was deliberately borrowed from engineering: organisational debt is the accumulation of changes that leadership should have made but didn't. The wrong person in the wrong role who wasn't moved out. The process built for twelve people that still governs two hundred. The reporting structure designed during a crisis that became permanent by default. The committee that lost its purpose three reorgs ago but still meets on Tuesdays. Each deferred change is a small liability. Left unaddressed, the liabilities compound — and like technical debt, the interest payments eventually consume more resources than the original fix would have cost.

The analogy to technical debt is precise because the accumulation mechanism is identical. A startup writes expedient code to ship fast. The code works, but it carries implicit obligations — refactoring that will eventually be required, tests that weren't written, architecture that won't scale. Technical debt is rational when the cost of delay exceeds the cost of the debt. Organisational debt operates on the same logic. A founder makes an expedient hiring decision — promoting a loyal early employee into a VP role they aren't qualified for — because the cost of a search exceeds the immediate cost of the promotion. The decision is rational in the moment. The debt compounds silently. At fifty employees, the unqualified VP has built a team in their image, hired people who won't challenge them, and created processes that protect their position rather than serve the company. The original expedient decision now governs an entire function.

What makes organisational debt worse than technical debt is that code doesn't have feelings. You can refactor a codebase without worrying about the code's self-esteem, its political allies, or whether it will leave a Glassdoor review. Organisational debt is embedded in people, relationships, and power structures — and paying it down requires conversations that most leaders would rather defer. The deferral is the mechanism. Every quarter the conversation doesn't happen, the debt increases: the wrong person hires more wrong people, the outdated process becomes more deeply embedded, the deferred reorganisation becomes more disruptive when it finally occurs.

Stripe reorganised three times between one hundred and one thousand employees. Not because the previous structures failed — because the company outgrew them. The organisational architecture that enables a hundred-person startup to move fast becomes the constraint that prevents a thousand-person company from coordinating. Brian Chesky's 2023 restructuring at Airbnb — what Paul Graham later framed as the "founder mode" memo — was the most visible recent example of a leader paying down a decade of accumulated organisational debt. Chesky eliminated layers of middle management, centralised product decisions, and reversed delegations that had diffused accountability to the point where no one could name who owned what. The restructuring wasn't a response to a crisis. It was the crisis prevention that years of deferred changes had made inevitable.

The compounding rate accelerates with headcount. A company at fifty employees carries the organisational decisions made at ten. A company at five hundred carries the decisions made at fifty. Each growth stage inherits the structures, roles, processes, and cultural norms of the previous stage — and each inherited element was optimised for a company that no longer exists. The organisational debt is the gap between the company you have and the company you need. The gap widens every day you don't address it.