Lead · Practice
Making technical debt visible enough to pay
Debt nobody can see never gets budget. Give each item a cost, an interest rate and a place on the same list as features, then pay it inside feature work.
- Technical debt that is only described as a feeling competes against features that have numbers attached, and it loses every quarter.
- Each debt item needs three things written down: where it hurts, what it costs to fix, and the interest, meaning how much slower each release gets while it is unpaid.
- Deliberate debt was chosen for a reason and can be recorded and revisited, while mess was never chosen by anyone, and the two need different conversations.
