Winning the Case: Convincing Your Product Manager to Prioritize Technical Debt
summary
Proposes auditing all tech-debt tickets, scoring each by user impact and dev time to build a scoring matrix that PMs can read as business value; prioritizes small, high-impact fixes first and bundles larger refactors into measurable milestones. Recommends concrete proofs like a proof of concept rocket SQL optimization showing elapsed-time drop, tracking API latency, uptime and time-to-market impact, and converting estimates into months and cost to justify work. Advises keeping debates numeric, involving adjacent teams, and avoiding emotional framing.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:08What is technical debt
- 3:17Why PMs don't see the problem
- 6:07How to prioritize debt
- 9:15Convincing your PM
- 12:09Team alignment matters
- 13:56Q&A
related talks
46mStop calling it technical debt and listen to your engineers
01h 12mBuilding a Technical Credibility to Fight Technical Debt
28mManaging Technical Debt at Scale
31mDealing with Technical Debt
36mPrioritizing Technical Debt as if Time & Money Matters
06mManage your tech debt like a mortgage
39mThe cash value of technical debt - How to scare your boss into doing the right thing
33mTackling Tech Debt on Android