Stop Focusing on Tech Debt
summary
Argues that obsessing over tech debt hits a ceiling and recommends building tech capital instead: invest in faster builds and safer deploys, a marketing editor that frees 85% of requests, and a two-day sales web app that surfaced location clusters. Recommends regular intermissions (~every 7–8 weeks) to prototype chunked bets, accept failure, and shift engineers to product mastery. Gives board-level outcome: engineers at two firms used these practices to pivot from single-tenant/on‑prem to viable SaaS models, one now succeeding.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 12:40Tech Capital
- 16:52Adopt a Mindset
- 17:42Use Internal Tools
- 18:22Innovation
- 19:06Make time for innovation
- 20:22Intermissions
- 22:07Embrace Failure
- 23:25Create Intermissions
- 27:33Product Mastery
- 29:18Speak Up
- 32:04Questions
related talks
23mCan We Please Stop Talking About Tech Debt?
46mStop calling it technical debt and listen to your engineers
06mManage your tech debt like a mortgage
31mDealing with Technical Debt
34mBuilding a Culture For Developer Productivity
05mAll Tech is Debt
24mInnovating Beyond Hackathons
01h 12mBuilding a Technical Credibility to Fight Technical Debt
