When debt grows despite repayment, simplify the system…
When a system's operational debt register grows despite consistent repayment, shift from maintenance to simplification rather than increasing maintenance effort.
Why This Is a Rule
When a system generates operational debt faster than you can repay it — despite consistent maintenance effort — the problem is structural complexity, not insufficient maintenance. The system is too complex for its maintenance budget. Increasing maintenance effort treats the symptom (growing debt) while ignoring the cause (excessive complexity). You'll spend more time maintaining while the register continues growing.
This is analogous to financial debt with interest exceeding income: paying more doesn't help if the interest rate is too high. The solution is to reduce the principal (simplify the system) rather than increase payments (more maintenance effort).
The diagnostic signal is clear: debt register growing despite consistent repayment. You're doing maintenance every week, but the register has more items at the end of the month than the beginning. The system is generating complexity faster than you're resolving it. The only sustainable response is to simplify the system until its complexity generation rate drops below your maintenance capacity.
When This Fires
- Your operational debt register has more items this month than last month despite regular repayment
- Maintenance consumes an increasing percentage of your available capacity
- You fix one issue and two more appear in its place
- Any system where keeping up with maintenance feels like a losing battle
Common Failure Mode
Doubling down on maintenance: "I just need to be more disciplined about cleaning up." But the system's complexity is the generator, and no amount of cleanup discipline can outpace a generator that's running faster than the cleaner. You need to shut down parts of the generator (simplify), not hire a faster cleaner (more maintenance).
The Protocol
When the debt register grows despite consistent repayment: (1) Stop increasing maintenance effort — it's not the solution. (2) Identify the complexity sources: which parts of the system generate the most debt? (3) Apply the eliminate-simplify hierarchy (Eliminate first, simplify second, automate last — never…): can you remove components entirely? Can you simplify remaining components? (4) Target: reduce system complexity until the debt generation rate drops below your normal maintenance capacity. (5) Validate the simplification over two cycles (Run simplified systems for two full cycles before…) before declaring the balance restored.