Loading content
Technical Debt Management defines processes and decision rules to identify, prioritize, and reduce technical debt. It aligns technical assessment with product and governance goals and specifies ownership, metrics, and repayment strategies. The method covers tactical remediation and strategic roadmaps to sustain code quality and lower long-term costs.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Technical debt management makes technical compromises visible, assesses their future cost, and steers their removal.
Ward Cunningham coined the term technical debt in 1992 for the future work created by a quick technical decision. Martin Fowler popularized distinctions between kinds of debt.
Record concrete debts, name their interest and risk, prioritize them against product work, and schedule repayment as visible work.
Future effort created by a technical shortcut.
Recurring cost created by a debt.
Work that reduces a technical constraint.
A visible debt inventory connects technical quality with traceable product decisions.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.