MENTAL MODEL · M9859

Technology Bankruptcy

SystemsmediumSystems Theory

Included

Updated 2026-08-15

Loading revision record…

INTRODUCTION

English translation pending.

CORE DEFINITION

Technology bankruptcy is the terminal condition of a system whose technical debt has accumulated to the point where the marginal cost of each change exceeds its value, maintenance consumes more than a full rewrite would, and adding new features has become practically impossible. The core proposition is that the system is already dead and the only rational moves are a clean rewrite or a managed retirement, because every patch applied from this state spends money to reduce no risk. The key qualification is that the diagnosis must be quantified, comparing rewrite cost against the run-rate maintenance cost, so the declaration rests on arithmetic rather than on developer frustration.

SCAFFOLDING EFFECT

psychology

Reduce cognitive load

- Watch The Threshold: track change failure rate and maintenance cost against the cost of a rewrite. - Declare The Death: call the system bankrupt when the numbers cross, instead of patching harder. - Fund The Replacement: commit to a rewrite or retirement plan with a migration path and parallel run.

anchor

Anchor fast decisions

Each shortcut taken in a system compounds, because later changes must route around it, and the routing itself becomes part of the debt. The interest on the debt is the rising marginal cost of every modification, and it grows superlinearly as the structure rots, until it crosses the cost of building the same capability from nothing. Past that crossing, patching spends money without extending the life of the system, because the failure mode is now the architecture itself and no local fix reaches it.

MINIMUM ACTION

In progress 0/1

Practice this model in one real situation:

Track the maintenance budget, change failure rate and lead time per change. 2. Estimate the cost of a rewrite and the cost of continued operation over the same horizon. 3. When the comparison crosses, declare the system bankrupt and stop approving patches. 4. Fund a rewrite or a retirement, with a migration plan and a parallel run. 5. Freeze the legacy system for all but critical fixes during the transition.

Check to track your progress (stored locally)

Learning progress0%

account_treeGenealogyexpand_more

menu_bookReferencesexpand_more

Source support: Explicit

link
en.wikipedia.orghttps://en.wikipedia.org/wiki/Technical_debtZH · Explicit
verified

RELATED MODELS