liveBook · Manning

Technical debt

As explained in Software Architecture Decision-Making

Technical debt is the future cost or limitation created by expedient technical choices or by allowing design constraints to accumulate.

Technical debt is a future obligation created when a technical choice leaves rework, operational burden, added risk, reduced flexibility, or loss of clarity to be handled later. It is not every shortcut or imperfect design: a choice becomes debt when its avoidable future cost exceeds what the situation required. section 2.1

Debt can be a deliberate form of leverage. A team may accept a limited compromise to meet a real deadline or deliver a more important capability, provided the compromise is visible, understood, owned, and revisited. The relevant comparison is not an ideal architecture that was never feasible, but an approach good enough for the actual context. section 2.1 section 1.3

Assess a shortcut by making its trade-offs explicit:

  • Identify the constraint it serves rather than treating convenience as justification. section 2.1
  • Consider consequence: high-impact areas include security, money, compliance, data integrity, and recovery. section 2.1
  • Keep it explainable to people who did not make the decision, and record its risk, owner, and revisit point. section 2.1
  • Prefer debt that is limited and reversible; avoid debt that spreads, hides, or makes the system hard to understand, operate, or recover. section 2.1

A time-to-market compromise

For a one-off change, manual testing may be sufficient when extensive test automation would delay critical functionality. Likewise, a synchronous API can be preferable to an event-driven design when it meets the immediate need much faster. Either choice warrants later attention only when it creates a future obligation beyond what the delivery context demanded. section 2.1

Technical debt becomes harmful when it is unmanaged rather than merely present. Earlier decisions can stop fitting as requirements, team capability, business priorities, and operating conditions change. Keep assumptions and consequences under review, but do not redesign in response to every signal: adaptation requires restraint as well as vigilance. section 1.3 section 1.6

Figure 1.1 Architecture as a feedback loop. Intent is shaped by forces, translated into decisions, and tested through consequences, feedback, and adaptation.

Use the feedback loop to locate debt: decisions made under constraints produce consequences that should trigger feedback and, when justified, adaptation. section 1.1

How Software Architecture Decision-Making covers it

How deep it goes
Defines debt, supplies an assessment rubric, and explains ongoing review without prescribing repayment techniques.
Examples
Uses manual testing for a one-off change and a synchronous API instead of event-driven architecture under deadline pressure.
What it assumes
Introduces technical debt from zero through delivery constraints, trade-offs, and future obligations.
What you can do after
Evaluate/understand whether a shortcut is justified, reversible, owned, and proportionate to its future risk.
How it connects
Connects technical debt with architectural decisions, time-to-market, non-functional requirements, operational maturity, and feedback loops.

Also explained in

Compare how 16 books explain technical debt →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Architecture Decision-Making. The section links point to the parts of the book it draws on.