A team that plans well and ships on time can still slow to a crawl if the codebase quietly decays underneath it. As a manager you are the person who decides how much effort goes into new features and how much goes into keeping the system healthy, and who has to explain that trade-off to people who don't read code.
You'll start with technical debt: where the idea came from, what its inventor actually meant, and the different forms it takes beyond messy code. From there the module looks at strategy and quality, including how to prioritize debt using real data, how to see why teams fall into the debt trap, and how to talk about it so that the work gets approved and done.
Once you can keep quality high while the team keeps delivering, you'll be ready for the next module, Communication & Stakeholders, which looks at how to share plans, risks and trade-offs with the people who depend on your team.
The person who coined the term explains what he really meant: shipping with partial understanding can be a smart choice, as long as you pay it back by refactoring as you learn.
Dave Farley looks at where technical debt comes from, why it is rarely repaid on schedule, and how design and quality practices help teams manage it over time.
A conference talk on how teams slide into a spiral of shortcuts and slower delivery, and what leaders can do to stop the debt from taking over.
Adam Tornhill explains why debt is hard to measure and shows how to use data from your own code and history to decide which debt is worth paying down first.
An engineering leader shares how reframing the conversation helped her get important technical work prioritized, without having to argue for tech debt.