Module 5 of 6Lesson 2 of 2~15 min
Technical debt, a product decision
Technical debt slows the roadmap long before it takes production down, which is why a PM benefits from framing it as a product cost. This lesson explains debt and its interest, how to classify it, how to argue for it as an investment, and how to decide with the team when to pay it down.
Lesson objective
By the end of this lesson, you will be able to explain what technical debt and its interest are, classify it with Martin Fowler's quadrant, express a debt as a cost to the product and decide with the team when and how to pay it back.
Topics covered
- technical debt
- Fowler's debt quadrant
- paying down debt
- roadmap prioritization
In the glossary
Where it fits
Deciding and recording
How do you choose between two options, keep a record of the decision and deal with technical debt?
Lessons in this module
- Framing a trade-off and recording it in an ADR
- Technical debt, a product decision (this lesson)
What you will learn in this module
This lesson is part of the course Read and challenge a technical architecture
- Frame an architecture trade-off, record it in an ADR and treat technical debt as a product decision.
Related courses
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Git for PMs: ship as a team without putting production at risk
3 hr 30 min
- Tech for PMsAll levelsNo prerequisites: accessible to everyone.
Explain how a web product works, from browser to server
2 hr 30 min
- Tech for PMsJuniorSome basics are useful: introductory knowledge of the topic.
Design and test an API integration as a PM
3 hr