Software engineering · Business & strategy
Technical debt.
Design or implementation choices that make future changes more costly, like interest on a debt.
Useful when weighing a shortcut against future maintenance.
“Identify the technical debt in this shortcut and explain which future changes it will make harder.”
A closer look
The metaphor helps connect present delivery decisions to later maintenance costs. A duplicated rule might save time today but require several coordinated edits next month. Name the likely interest and the work that would reduce it rather than treating every imperfection as equally urgent.
Put it to work
“Prioritize debt in the pricing module because its duplication slows every weekly update.”
A useful distinction
An unbuilt feature is not automatically technical debt. The issue is extra future cost caused by the current structure or implementation.