Managing Technical Debt: Reducing Friction in Software Development

Technical Debt as a Software Engineering Reality

Technical debt is easy to recognize in hindsight: a shortcut in code, a postponed refactor, a fragile integration, a design decision that keeps teams moving today but slows them down later. Managing Technical Debt: Reducing Friction in Software Development treats those costs as a management problem that can be understood, measured, and acted on. Written by Philippe Kruchten, Robert Nord, and Ipek Ozkaya, this book belongs to the SEI Series in Software Engineering and connects debt to the daily friction that software teams feel.

From Metaphor to Practice ⚙️

The book moves beyond the familiar debt analogy. It examines how technical debt appears in source code, architecture, and production systems, and why context matters when deciding whether a particular debt is worth fixing. Readers encounter concepts such as principal and interest, potential versus actual debt, and the technical debt timeline. The goal is not to eliminate every shortcut but to make informed choices about which debt to carry and which to repay.

What the Book Explores

• Part I: Exploring the Technical Debt Landscape — introduces friction in software development, defines technical debt, and shows how context shapes debt decisions.
• Part II: Analyzing Technical Debt — covers recognizing debt and understanding its relationship to source code, architecture, and production.
• Part III: Deciding What Technical Debt to Fix — focuses on costing and servicing debt so teams can prioritize repayment work.
• Part IV: Managing Technical Debt Tactically and Strategically — examines causes, credit checks, avoiding unintentional debt, and living with debt over time.

Who This Book Is For 💻

Software developers, architects, technical leads, and engineering managers will find the material relevant because it treats technical debt as part of normal software delivery. It speaks to teams that need to balance short-term delivery pressure with long-term maintainability. The chapters are organized to support both tactical decisions and broader strategic planning.

Practical Ways to Think About Debt

The book does not offer a single formula for every team. Instead, it provides a structured way to discuss debt: what it is, where it lives, what it costs, what causes it, and how to service it. That framework can help teams move from vague complaints about code quality to clearer conversations about trade-offs, priorities, and risk.

About the Authors

Philippe Kruchten, Robert Nord, and Ipek Ozkaya bring together experience in software architecture, software engineering, and technical debt research. Their collaboration reflects the SEI Series’ focus on practical software engineering topics for practitioners and students.

Managing Technical Debt is a considered guide for teams that want to reduce friction and make better decisions about the debt they carry.