Episode
#239 - Taming Your Technical Debt: Mastering the Trade-Off Problem - Andrew Brown
- Podcast
- Tech Lead Journal
- Published
- Nov 17, 2025
- Duration seconds
- 3989
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/tech-lead-journal-633005/episodes/239-taming-your-technical-debt-mastering-the-trade-off-problem-andrew-brown/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/tech-lead-journal-633005/239-taming-your-technical-debt-mastering-the-trade-off-problem-andrew-brown.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
(06:06) Brought to you by Jellyfish AI tools alone won’t transform your engineering org. Jellyfish provides insights into AI tool adoption, cost, and delivery impact – so you can make better investment decisions and build teams that use AI effectively. See for yourself at jellyfish.co/platform/ai-impact . Why do organizations constantly complain about having too much technical debt? Because they’re solving the wrong problem. In this episode, Dr. Andrew Brown, author of “Taming Your Dragon: Addressing Your Technical Debt,” reveals a profound insight: technical debt isn’t fundamentally a technical problem. It’s a trade-off problem rooted in human bias, organizational systems, and economic incentives. Through his innovative “Technical Debt Onion Model,” Andrew shows how decisions about code quality happen across five interconnected layers, from individual cognitive biases to wicked problem dynamics. Andrew explains why the financial debt analogy is dangerously misleading and, more importantly, how others can rack up debt you’ll eventually pay for. Drawing from behavioral economics, systems thinking, and organizational theory, he reveals why our emotions, not logic, drive most technical decisions, and how to work with this reality rather than against it. Key topics discussed: Why technical debt is a trade-off problem, not technical How emotions override logic in critical decisions The Technical Debt Onion Model framework explained Principal-agent problems sabotaging your codebase Externalities: who pays for shortcuts taken today? Why burning down debt is already too late Ulysses contracts for managing future obligations Systems thinking applied to software development Wicked problems: why different teams see different solutions AI’s impact on technical debt creation Timest…