Organizational Debt
Organizational debt is the accumulated cost of structural shortcuts, deferred decisions, and unaddressed dysfunctions in how a company operates. Like technical debt, it's incurred to move faster in the short term — a temporary reporting line, a one-off approval workaround, an unowned process, a broken handoff. Like technical debt, it compounds: every new initiative built on top of org debt inherits the dysfunction and amplifies it. Unlike technical debt, org debt is mostly invisible on dashboards because it lives in calendars, comp structures, decision rights, and human relationships. KnowMBA POV: organizational debt compounds faster than technical debt because every quarter without payment adds new dependencies that make the eventual paydown 10x harder.
The Trap
The trap is treating org debt as something to address 'after we hit the next milestone' — a stance that guarantees you never address it. Each new hire, new product line, and new market entry layers on top of existing debt. By the time the org consciously notices the dysfunction (usually after a missed quarter or a senior departure), the debt is so structurally embedded that paying it down means restructuring decisions, comp, and reporting lines simultaneously. The other trap is mistaking org debt for 'culture' — treating dysfunctional patterns as immutable identity rather than accumulated technical choices that can be unwound.
What to Do
Conduct a quarterly org debt audit using four lenses: (1) Decision Debt — where are decisions being made by the wrong people, at the wrong cadence, or not at all? (2) Process Debt — what workflows have unowners, manual workarounds, or systematic exceptions? (3) Structural Debt — what reporting lines, team compositions, or matrix arrangements exist as historical accidents? (4) Comp/Incentive Debt — where are people being paid for behavior the company says it doesn't want? Score each item by impact and pay-down cost. Pay down at least 2-3 items per quarter. Track 'org debt service ratio' — % of leadership capacity spent working around dysfunction.
Formula
In Practice
The term 'organizational debt' was coined and developed by Aaron Dignan in his book Brave New Work (2019), where he describes it as 'the accumulated changes that management should have made but didn't.' Dignan argues that the average enterprise carries decades of layered org debt — bureaucratic processes, outdated approval chains, residual decision-making structures from earlier company stages — and that this debt is the single biggest drag on adaptive capacity. Companies like Buurtzorg (Dutch home healthcare) and Morning Star (US tomato processing) are cited as organizations that consciously paid down org debt by removing management layers, redistributing decision rights, and eliminating accumulated bureaucracy. (Source: Brave New Work, Aaron Dignan, 2019.)
Pro Tips
- 01
The most predictive signal of high org debt is the volume of 'translation roles' — people whose actual job is to move information across broken handoffs. If you have multiple chiefs of staff, integration PMs, and 'business operations' roles whose work is workflow patching, you're paying enormous interest on org debt.
- 02
Pay down debt during business strength, not crisis. Most orgs only confront debt during downturns or after senior departures, when capacity for restructuring is lowest. Build a default discipline of paying down 2-3 items per quarter regardless of business conditions.
- 03
Make debt visible. Maintain a public 'org debt register' — known dysfunctions, owners, pay-down plans. Visibility creates accountability. The debt that's hidden is the debt that compounds the most.
Myth vs Reality
Myth
“Startups don't have organizational debt — only mature companies do”
Reality
Startups accumulate org debt faster than mature companies because every hiring decision, every reporting line, and every tool choice is being made under speed pressure with thin process. By the Series B, most startups carry significant debt: founder dependencies, ad-hoc decision-making, role overloads. The difference is that the debt hasn't yet generated visible drag because the team is small enough to brute-force around it.
Myth
“Reorgs pay down organizational debt”
Reality
Reorgs frequently add debt rather than reduce it because they reshuffle people without addressing decision rights, process ownership, or incentive structures. A reorg without explicit debt paydown often just moves the debt to new lines and adds the disruption cost on top. Real paydown is usually quieter than a reorg: changing how a specific decision is made, who owns a specific process, or how a specific team is measured.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
You're a new COO at a 2,000-person company. After 90 days, you observe: 4 chiefs of staff, 6 'business operations' people whose role is unclear, 11 standing cross-functional 'sync' meetings, and 3 different OKR cascade processes running in parallel. What's the most likely diagnosis?
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Aaron Dignan / Brave New Work Framework
2019 (book publication; concept developed prior)
Aaron Dignan, founder of The Ready (organizational design firm), formalized the concept of organizational debt in his book Brave New Work. He argued that most enterprise organizations carry decades of layered debt: bureaucratic approvals, outdated reporting lines, accumulated meetings, ritualized processes that no longer serve their original purpose. Dignan's framework draws explicit parallels to technical debt — both are taken on as expedient shortcuts, both compound through neglect, both eventually constrain what the system can do. Companies like Buurtzorg (eliminated middle management in home healthcare), Morning Star (no formal hierarchy in tomato processing), and Haier (broken into thousands of microenterprises) are cited as examples of conscious org debt paydown. The book popularized the term and gave operators a vocabulary for describing dysfunctions that previously felt like immutable 'culture.'
Concept Origin
Aaron Dignan, The Ready
Book
Brave New Work (2019)
Cited Examples
Buurtzorg, Morning Star, Haier
Core Thesis
Most orgs carry decades of layered debt
Naming the problem is the first paydown. Once an organization has a vocabulary for org debt, dysfunctions stop being 'just how things are' and start being items on a list with owners and deadlines.
Decision scenario
The Debt Paydown Bet
You're the COO of a 1,500-person company. An audit identifies 18 org debt items across decision rights, processes, and incentives. Your CEO wants to focus on growth initiatives this year — not 'inward-looking work.' Your data shows ~$3M/year in current debt service costs and degrading decision velocity.
Headcount
1,500
Identified Debt Items
18
Annual Debt Service
~$3M
CEO Priority
Growth, not 'inward work'
Decision 1
You can (a) defer paydown to focus on growth, (b) attempt to pay down all 18 items aggressively, or (c) commit to paying down 3 items per quarter alongside growth work.
Defer paydown — focus the year on growth as the CEO directed.Reveal
Aggressive paydown — tackle all 18 items in two quarters.Reveal
Commit to 3 items per quarter — sustained, named, and measured. Frame it to the CEO as 'execution velocity infrastructure for the growth strategy.'✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Organizational Debt into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Organizational Debt into a live operating decision.
Use Organizational Debt as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.