Stop calling it technical debt and listen to your engineers
summary
Argues that “technical debt” is a lazy label and urges quantifying business value and risk, showing concrete wins like changing a lead form that boosts conversion 3% to 8% in days, building four component libraries and a three‑day refactor that actually reduced incidents, and shipping on a headless e‑commerce stack (not Shopify, totally headless) using Vue/React/TypeScript across UK and Australia warehouses. Recommends clear ticket titles, numeric predictions, a ticket template and a tech‑debt workshop.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 7:46Technical debt problems
- 10:13Why debt tickets ignored
- 18:20Business value and risk
- 26:55Calculating tech improvement value
- 32:16Prioritizing technical work
- 38:15What to call tech work
- 39:40Key takeaways
- 41:26Q&A
related talks
39mStop Focusing on Tech Debt
23mCan We Please Stop Talking About Tech Debt?
28mTechnical Debt: Why it'll ruin your software
31mDealing with Technical Debt
42mTechnical Debt - Why the Term Causes More Confusion than Clarity
17mHow to deal with technical debt in fast-paced environment
01h 12mBuilding a Technical Credibility to Fight Technical Debt
15mWinning the Case: Convincing Your Product Manager to Prioritize Technical Debt