Technical Debt Isn't the Enemy: A Strategic Framework for Engineering Leaders

In this episode, Kevin tackles one of the most misunderstood topics in software development: technical debt. Drawing on his experience at Microsoft, Spotify, and early-stage startups, he challenges the common assumption that all technical debt is bad, explaining why healthy teams intentionally take on debt as part of shipping software effectively.

Kevin introduces a practical four-part framework for understanding technical debt: pragmatic debt (taken on deliberately to validate ideas or meet constraints), required debt (that directly impacts reliability, security, or delivery capability), incidental debt (stable, low-risk code that's safe to ignore), and symptomatic debt (a signal of deeper organizational problems that code fixes won't solve). He explains how to identify each type and, more importantly, how to decide what deserves your team's attention and what doesn't.

The episode explores why teams often struggle to get product support for addressing technical debt, how to tie debt decisions to business outcomes, and why some debt is actually a symptom of broken systems rather than poor engineering choices. Kevin shares real examples from his own career, including inheriting a monolith that had outlived its usefulness and intentionally taking on debt at Spotify to learn faster.

Whether you're an engineering leader trying to prioritize what debt to fix, a product manager wondering why engineers keep talking about refactoring, or an executive trying to understand which debt threatens business outcomes, this episode provides a strategic lens for making better decisions about the inevitable trade-offs in software development.

• ConFoo 2026 (https://confoo.ca/en/2026)
• Listener Survey: https://forms.gle/JVeKHsHJKhEM3dvK6
• The book: It Depends: Writing on Technology 2012-2022 (https://itdependsbook.net)
• Your host: Kevin Goldsmith (https://kevingoldsmith.com)