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.
Section 2
How to See It
Organisational debt reveals itself through friction — the kind that doesn't show up in metrics but shows up in how long everything takes. Decisions that should require one meeting require five. Projects that should involve three people involve twelve. Information that should flow directly routes through intermediaries who add no value but whose position in the hierarchy makes them mandatory checkpoints. When people inside the company start saying "that's just how it works here" about a process no one can explain the origin of, you are looking at organisational debt.
The most reliable diagnostic is the workaround. Every organisation with significant debt develops informal systems to route around the formal ones. The engineer who messages the designer directly instead of filing a ticket through the project manager. The sales rep who escalates directly to the CEO because the VP of Sales is a bottleneck rather than an enabler. The shadow org chart — the actual network of who-talks-to-whom that diverges from the official reporting structure — is a map of where organisational debt has accumulated. The larger the gap between the formal structure and the shadow structure, the greater the debt.
Startups & Growth-Stage Companies
You're seeing Organisational Debt when a startup at eighty people still has the flat structure it adopted at fifteen. Every engineer reports to the CTO. There are no engineering managers. The CTO spends their entire day in one-on-ones and has written zero code in eighteen months. The original structure was correct for fifteen people. At eighty, it is organisational debt — a structure that persists not because it works but because no one made the uncomfortable decision to change it.
Enterprise & Corporate
You're seeing Organisational Debt when a large organisation has a "transformation office" or "change management team" — a permanent bureaucracy whose existence is evidence that the organisation's normal operating structures cannot adapt without a dedicated intervention team. The transformation team is the interest payment on accumulated organisational debt: a recurring cost incurred to manage the consequences of changes that should have been made incrementally over years.
Product & Engineering
You're seeing Organisational Debt when product decisions are still shaped by the preferences of a customer who churned two years ago, or when feature priorities reflect the political power of the team that built them rather than the strategic value they deliver. A feature that no one uses but that survives every prioritisation exercise because its team is politically connected is organisational debt encoded in the product roadmap.
Leadership & People
You're seeing Organisational Debt when a leader who was exceptional at twenty employees is visibly struggling at two hundred — and everyone knows it but no one will say it. The performance conversation that should have happened at one hundred employees was deferred because the leader was loyal, well-liked, and had been there since the beginning. At two hundred, the leader has hired a team of thirty in their image, created a subculture within their function that diverges from the rest of the company, and become an obstacle to the coordination the company now requires. The deferred conversation now involves thirty people instead of one.
Section 3
How to Use It
Decision filter
"Every quarter, I ask: what decision am I deferring because it's uncomfortable? The deferred decision is organisational debt. I estimate the compounding cost — how much harder will this be in six months? In twelve? If the cost is increasing, I make the decision now. The interest rate on organisational debt is always higher than you think."
As a founder
Build the discipline of periodic organisational audits — deliberate reviews of every role, process, and structure against the company's current needs rather than its historical ones. The question for each element: if we were designing this company from scratch today, would this role exist? Would this process exist? Would this reporting structure exist? If the answer is no, you've identified organisational debt. The audit should happen at every doubling of headcount — at minimum. Stripe's three reorganisations between one hundred and one thousand employees represent roughly this cadence.
The hardest form of organisational debt for founders is the loyalty tax — keeping early employees in roles they've outgrown because they were there when it mattered. The loyalty is real. The cost is also real. Every month an under-qualified leader remains in a role that requires someone more capable, the team beneath them accumulates debt: wrong hires, wrong processes, wrong priorities. The founder's job is to honour the loyalty without subsidising it with the company's future.
As an investor
Organisational debt is the most underweighted risk in due diligence. Financial models capture revenue, margins, and growth rates. They don't capture the organisational friction that determines whether the company can execute the plan the model assumes. The diagnostic questions: how many layers are between the CEO and the customer? When was the last time the company reorganised, and what triggered it? Are there roles or processes that the management team acknowledges are suboptimal but hasn't addressed? The speed of the answer tells you as much as its content. A CEO who immediately names three pieces of organisational debt and explains the paydown plan is operating with awareness. A CEO who insists the organisation is "fine" at two hundred employees with the same structure they had at forty is sitting on a balance sheet liability that doesn't appear in the financials.
As a decision-maker
Treat organisational design as a product that requires iteration, not a structure that requires stability. Most leaders design their organisation once and then defend the design against change — treating any reorganisation as a sign of failure rather than a sign of growth. The reframe: a reorganisation is a product update. The previous version shipped, served its purpose, and is now being replaced by a version better suited to current conditions. The companies that restructure proactively and regularly accumulate less organisational debt than the companies that restructure only in crisis — because each incremental restructuring pays down a small amount of debt before it compounds, while the crisis restructuring pays down a decade of accumulation at once, with all the disruption that implies.
Common misapplication: Treating every organisational friction as "debt" that must be eliminated immediately. Some structures that feel suboptimal exist for reasons that aren't visible to the person who wants to change them. A process that seems bureaucratic may encode hard-won lessons from a previous failure. A reporting structure that seems redundant may protect against coordination failures that only manifest under stress. The discipline is distinguishing between genuine debt (structures that persist because no one made the decision to change them) and deliberate architecture (structures that persist because they serve a purpose that isn't immediately obvious). The diagnostic: can anyone explain why this structure exists? If yes, it may be architecture. If no one remembers, it's debt.
Section 4
The Mechanism
Section 5
Founders & Leaders in Action
The leaders who manage organisational debt most effectively share a counterintuitive trait: they restructure when things are working, not when things are broken. They treat organisational design as a continuous practice rather than an emergency response. The result is a company that evolves its structure in step with its scale — paying down debt incrementally rather than allowing it to compound until a crisis forces a painful reckoning.
Hastings built Netflix's culture around the systematic prevention of organisational debt. The Netflix Culture Deck — which Sheryl Sandberg called "one of the most important documents ever to come out of Silicon Valley" — was an explicit anti-debt manifesto. Its core principle: hire exceptional people, pay them at the top of the market, and remove anyone who is merely adequate. The "keeper test" — asking every manager "if this person told you they were leaving, would you fight to keep them?" — was a mechanism for surfacing organisational debt before it compounded. If the answer was no, the person was transitioned out with generous severance that reduced the emotional cost of the decision.
Hastings restructured Netflix repeatedly as it scaled. The DVD-by-mail operation was a different organisation than the streaming service, which was a different organisation than the content studio. Each transition required dismantling structures that had served the previous phase and building new ones for the next. The Qwikster debacle of 2011 — a failed organisational split — demonstrated that even Hastings got the restructuring wrong sometimes. The lesson he drew was not to restructure less but to restructure better: gather more information, move faster once the direction is clear, and accept that some restructurings will fail. The alternative — preserving a structure past its useful life — was always worse.
Lütke has been the most explicit contemporary CEO about the necessity of periodic organisational paydown. He has described his job as "rebuilding the company every few years" — not because the previous version failed but because the company outgrew it. Shopify's organisational architecture at fifty employees was designed for a single product serving small merchants. At five thousand employees serving enterprises, that architecture was debt.
In 2023, Lütke executed one of the most aggressive organisational debt paydowns in recent tech history. Shopify eliminated its Deliverr logistics division (acquired for $2.1 billion just a year earlier), cut roughly twenty percent of the workforce, and publicly committed to keeping the company intentionally lean relative to its revenue. Lütke's internal memo was striking for its directness: the company had accumulated organisational complexity that was slowing it down, and the solution was subtraction. He eliminated standing meetings that had lost their purpose, dissolved committees that had become political rather than productive, and reset team sizes to force prioritisation. The restructuring was painful. The alternative — carrying the accumulated debt into the next phase of growth — would have been terminal.
Section 6
Visual Explanation
Section 7
Connected Models
Organisational debt sits at the intersection of systems thinking, leadership practice, and organisational theory. Its connections reveal the forces that cause debt to accumulate, the structures that determine where it concentrates, and the thinking tools required to anticipate its compounding effects before they become unmanageable.
Reinforces
Technical Debt
The analogy is structural, not rhetorical. Technical debt is expedient code that works today but requires future refactoring. Organisational debt is expedient structure that works today but requires future restructuring. Both compound — technical debt through code dependencies that make refactoring progressively harder, organisational debt through people dependencies that make restructuring progressively more disruptive. Both are rational to incur in small doses under time pressure. Both become lethal when the interest payments — time lost to workarounds, talent lost to dysfunction, speed lost to coordination overhead — exceed the capacity to pay them down. The reinforcement is bidirectional: companies with high technical debt tend to accumulate organisational debt (because the engineering dysfunction produces workaround structures), and companies with high organisational debt tend to accumulate technical debt (because dysfunctional organisations make poor architectural decisions).
Reinforces
[Entropy](/mental-models/entropy)
The second law of thermodynamics applied to organisations: without constant energy input, systems tend toward disorder. Organisational debt is entropy made specific — the natural tendency of structures, roles, and processes to degrade as the environment they were designed for changes. A role that was well-defined at twenty employees becomes ambiguous at two hundred as responsibilities overlap and boundaries blur. A process that was efficient for one product becomes a bottleneck for five. Entropy doesn't require bad decisions. It requires only the passage of time and the absence of deliberate maintenance. The reinforcement: entropy generates organisational debt continuously, and unaddressed organisational debt accelerates entropy by preventing the structural maintenance that would counteract it.
Reinforces
Conway's Law
Section 8
One Key Quote
"Day 2 is stasis. Followed by irrelevance. Followed by excruciating, painful decline. Followed by death. And that is why it is always Day 1."
— [Jeff Bezos](/people/jeff-bezos), 2016 Letter to Amazon Shareholders
Bezos was describing the accumulated weight of an organisation that stops questioning its own structures. Day 2 is what happens when organisational debt compounds past the point of recovery — when the processes, hierarchies, and cultural norms designed for a previous era become so deeply embedded that they resist adaptation entirely. The company continues to operate. It holds meetings, ships products, files reports. But the gap between its structure and its environment widens with each quarter, and the energy required to maintain the outdated structure exceeds the energy available for adaptation.
The "Day 1" philosophy is an anti-debt discipline. Bezos institutionalised it through mechanisms like the empty chair (representing the customer in every meeting), the six-page memo (forcing clarity that PowerPoint obscures), and the two-pizza team (keeping units small enough to avoid the coordination overhead that organisational debt creates). Each mechanism was designed to prevent the specific forms of debt that Bezos had observed in other large organisations — customer distance, decision opacity, and bureaucratic expansion. The mechanisms don't eliminate debt. They slow the accumulation rate enough to keep the company functional at scale.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Organisational debt is the single most common cause of death in companies that have already achieved product-market fit. The company that dies at the seed stage dies from lack of demand. The company that stalls at Series B stalls from organisational debt — the accumulated weight of expedient decisions that made sense at ten people and became lethal at a hundred.
The compounding rate is the part founders consistently underestimate. A bad hire at employee twenty is one bad hire. That same person, unfired at employee sixty, has built a team of eight in their image, established processes that protect their authority rather than serve the company, and created a cultural pocket that diverges from the rest of the organisation. The original hiring mistake now requires a restructuring that affects thirty people and takes six months. The interest on the original debt exceeds the principal by an order of magnitude.
The diagnostic I use most: ask the CEO to describe their organisational architecture, then ask five employees at different levels to describe the same architecture. The divergence between descriptions is a direct measure of organisational debt. In healthy companies, the descriptions converge — everyone understands the structure, their role within it, and how decisions flow. In debt-laden companies, the descriptions diverge radically — the CEO describes one organisation, and the employees describe a different one, complete with shadow hierarchies and workaround processes the CEO doesn't know exist.
Chesky's Airbnb restructuring is the case study I reference most. After a decade of professional management — hiring experienced executives, delegating authority, building the organisational layers that conventional wisdom prescribed — Chesky concluded that the accumulated layers had diffused accountability to the point where no one owned anything. His response was to pay down the debt all at once: flatten the hierarchy, centralise product decisions, eliminate the middle management layer that had become a translation layer between leadership and execution. The company's subsequent performance — record revenue, first sustained profitability — suggests the debt paydown unlocked execution capacity that the accumulated structure had been suppressing for years.
The most dangerous form of organisational debt is cultural. Structural debt — wrong roles, wrong processes — is visible and fixable. Cultural debt — norms, assumptions, and behavioural patterns that persist from a previous era — is invisible and self-reinforcing. A company that tolerated mediocre performance during its growth phase because hiring was hard and retention mattered more than excellence carries that tolerance as cultural debt. The tolerance becomes a norm. The norm attracts more mediocre performers. The mediocre performers resist any attempt to raise standards because the current standards are the ones they were hired under. Paying down cultural debt requires changing what the organisation considers normal — the hardest restructuring of all.
Section 10
Test Yourself
Organisational debt is invoked loosely — every founder who fires someone calls it "paying down debt." The scenarios below test whether you can distinguish genuine organisational debt (structural choices that persist because no one made the decision to change them) from other forms of organisational challenge (growing pains, strategic disagreements, or normal coordination costs at scale).
Is Organisational Debt the right diagnosis here?
Scenario 1
A 300-person company still uses the same all-hands meeting format it adopted at 30 people: the CEO presents updates, takes questions from the audience, and makes decisions in real time based on crowd input. At 30 people, this worked — every employee could participate meaningfully. At 300, the meeting runs two hours, fewer than 10% of employees speak, and the 'real-time decisions' are actually pre-made decisions performed as if spontaneous. Senior leaders complain the format wastes their time. The CEO refuses to change it because 'this is how we've always done it.'
Scenario 2
A rapidly growing startup has three engineering teams, each with a different deployment process. Team A deploys continuously. Team B deploys weekly with a manual QA step. Team C deploys monthly after a formal review. The CTO acknowledges the inconsistency but explains that each team's process reflects the risk profile of their product: Team A works on internal tools (low risk), Team B on the core product (medium risk), and Team C on the payments system (high risk, regulatory requirements).
Scenario 3
A 500-person company has a VP of Marketing who was the founder's college roommate and first employee. The VP manages a 40-person team but struggles with the analytical, data-driven marketing the company now requires. Three high-performing marketing managers have left in the past year, each citing the VP's resistance to modern practices. The founder is aware of the problem but says 'we'll find a way to make it work' every time the board raises it.
Section 11
Top Resources
The literature on organisational debt draws from startup strategy, organisational theory, and leadership practice. The concept is recent — Blank coined the term in 2015 — but the underlying dynamics have been described by management theorists for decades under different names: organisational inertia, structural lag, institutional sclerosis. The resources below progress from the original framing through the theoretical foundations to the operational playbooks for paying down debt in practice.
The original articulation of the concept. Blank draws the explicit parallel between organisational debt and technical debt, identifying the three categories — people, process, structure — that generate the most damaging accumulation. Short, direct, and foundational. Read this first for the framing that made the concept legible to an entire generation of founders.
The most operationally honest book about the decisions that generate and pay down organisational debt. Horowitz writes about firing executives, demoting friends, and restructuring teams with a directness that most leadership books avoid. The chapters on hiring, firing, and organisational design are the practitioner's guide to managing the debt that Blank's blog post identifies but doesn't operationalise.
The most detailed case study of an organisation designed to prevent organisational debt from accumulating. Hastings's keeper test, talent-density philosophy, and approach to radical transparency are all mechanisms for surfacing and paying down debt before it compounds. The treatment of how Netflix restructured through multiple business model transitions demonstrates what periodic debt paydown looks like at scale.
Grove's management framework provides the structural tools — span of control, task-relevant maturity, dual reporting — for designing organisations that accumulate less debt. His treatment of when to restructure and how to evaluate organisational design against output is the most rigorous analytical framework for diagnosing structural dysfunction. The book doesn't use Blank's terminology, but every chapter addresses the dynamics that generate or prevent organisational debt.
Adizes's lifecycle model describes the predictable stages through which organisations grow — and the predictable crises that occur when the organisation fails to transition between stages. Each crisis is a manifestation of accumulated organisational debt: structures designed for the previous stage that constrain the current one. The model provides the theoretical framework for understanding why debt accumulates in discrete jumps at stage transitions rather than continuously.
Organisational Debt — Structural choices compound as the company scales. Companies that pay down debt at each growth stage (periodic reorgs) maintain execution capacity. Companies that defer accumulate a burden that eventually forces crisis-level restructuring.
Conway's Law states that organisations design systems that mirror their communication structures. The reinforcement with organisational debt is direct and damaging: an organisation carrying significant structural debt will produce products and systems that encode that debt. If the engineering organisation has two teams that don't communicate effectively because of a political rivalry between their directors, the software they produce will have an integration gap at exactly the boundary between those teams. The organisational debt becomes product debt becomes technical debt — a compounding chain where structural dysfunction propagates into every artifact the organisation produces.
Tension
Second-Order Thinking
Second-order thinking — the discipline of tracing consequences beyond the immediate effect — creates productive tension with the expedient decisions that generate organisational debt. The founder who promotes the loyal early employee without considering the second-order effects (the team that person will build, the culture they'll create, the capability gap that will emerge) is accumulating debt through first-order thinking. The tension: genuine second-order thinking would prevent most organisational debt from accumulating. The resolution: second-order thinking is cognitively expensive, and in the chaos of a fast-growing startup, the cognitive budget is finite. Some organisational debt is the inevitable consequence of bounded rationality under time pressure. The discipline is not to eliminate all debt but to be deliberate about which debts you incur — and to schedule paydown before the interest compounds.
Leads-to
Dunbar's Number
Dunbar's Number — the cognitive limit of approximately 150 stable social relationships — explains why organisational debt accumulates in discrete jumps rather than linearly. Below 150 people, informal coordination works. Everyone knows everyone. The founder can maintain direct relationships with every employee. Above 150, the organisation must formalise — creating structures, processes, and hierarchies that substitute for the informal coordination that Dunbar's limit makes impossible. Each crossing of a Dunbar threshold (roughly 15, 50, 150, 500) requires a different organisational architecture. The debt accumulates when the company crosses a threshold without redesigning the architecture — running a 200-person company on a 50-person structure because no one recognised that the threshold had been crossed.
Leads-to
Span of Control
Span of control — the number of direct reports a manager can effectively oversee — is the mechanism through which organisational debt manifests in daily operations. When a company grows without adjusting its management structure, spans of control widen beyond effectiveness. A VP with four direct reports at fifty employees has fifteen at two hundred because no one created the management layer between them. The VP becomes a bottleneck. Decisions slow. Information distorts as it passes through an overloaded node. Span of control problems are the most visible symptom of organisational debt — and the first thing experienced operators fix when they audit a company's structure.
For investors: organisational debt is the hidden liability that explains why some companies with strong product-market fit still feel slow. The revenue masks the dysfunction. The growth masks the friction. The best diligence question is not "how fast are you growing?" but "what organisational decisions have you been deferring, and what's your plan to address them?"
My operational rule: the right time to restructure is when you can still afford to. By the time the debt forces a crisis-driven restructuring, you've already paid years of unnecessary interest. The best operators restructure from a position of strength — when the company is performing well and has the resources to absorb the disruption. The worst operators restructure from a position of desperation — when the accumulated debt has degraded execution so severely that the restructuring is a survival measure rather than an improvement measure. The first approach is proactive maintenance. The second is emergency surgery. The outcomes differ accordingly.
