Business Core · Technology · Module
Technical debt and renewal
What the estate owes to decisions made earlier, which of those debts are worth repaying, and how ageing systems are replaced without stopping the business.
The idea
How it works
Cunningham introduced the debt metaphor in 1992 to explain a deliberate trade: shipping something imperfect now, on the understanding that it would be revisited. It holds because the cost of not revisiting behaves like interest — each change to the affected system takes longer, and the extra time compounds. Debt taken on knowingly is a financing decision; debt nobody recorded simply makes the organisation slower.
Renewal is the larger form of the same problem. Systems reach the end of vendor support, lose the people who understood them, or stop fitting the business. Replacing them in a single step has a poor record; replacing them piece by piece, with old and new running side by side, is slower to start and more likely to finish. The replacement dates and costs of held assets stay in Business Assets under lifecycle; this module decides what the replacement should be and in what order.
Working with it
In practice
- 01
Record debt when it is taken on
A short entry at the moment of the shortcut costs minutes. Reconstructing it later costs an investigation.
- 02
Assess every system on two axes
Business fit and technical condition. Tolerate, invest, migrate or eliminate follows from where each one lands.
- 03
Reserve capacity for repayment
A fixed share of engineering time, agreed in advance, stops repayment from losing every prioritisation meeting to new features.
- 04
Replace incrementally
Move one function at a time to the new system, and retire the old one only when nothing still depends on it.
One level in
The components of technical debt and renewal
A component is something that exists afterwards which did not exist before — a deliverable or a mechanism, not an intention.
Technical debt register
The known shortcuts and outdated parts of the estate, what each costs to carry, and what it would cost to repay.
LearnApplication portfolio assessment
Each system rated for business fit and technical condition, with the resulting course of action.
LearnRenewal roadmap
The phased plan for replacing or modernising systems, sequenced so the business keeps running throughout.
Learn
Debt recorded when it is taken on is a decision. Debt discovered later is only a cost.
The other modules in technology
The technology estate
What systems the organisation runs, how they connect, and the few principles that decide what may be added to them.
LearnBuild, buy or subscribe
Deciding, for each capability, whether to build it, license it or rent it as a service — and recording why, so the reasoning can be revisited.
LearnAI and automation
Where AI and automation are used, who remains accountable for what they do, how well they are shown to work, and what risk each use carries.
LearnSecurity
Protecting the estate as a capability: knowing what is worth attacking, holding a baseline of controls, managing who can get in, and being able to recover.
Learn