Review Debt

An umbrella term for a present tradeoff or deferred obligation that creates future cost, constraint, or risk; explicitly not financial debt.

In this glossary, debt means taking a benefit or postponing work now while carrying an obligation into the future. The obligation may appear later as added work, reduced options, higher cost, or greater risk. Debt is the family label for the related terms below, not a claim that they form a universal taxonomy.

The debt framing helps a team make a delayed obligation visible before it becomes an unexplained failure or recurring burden. A tradeoff can be reasonable when the obligation, owner, consequence, and exit condition are understood. Hidden debt is harder to manage because the people paying its cost may not know which earlier choice created it.

A team launches a service with a three-step manual workaround to meet a deadline. The workaround is documented, assigned an owner, and scheduled for replacement. The immediate benefit is real, but the future reconciliation work is debt until the workaround is removed.

Debt is not automatically a mistake, defect, delay, or moral failure. It can be a deliberate tradeoff. It becomes dangerous when the future obligation is invisible, unowned, misunderstood, or allowed to compound. In this glossary, Debt also does not mean a financial loan or balance.

Take the benefit now; carry the obligation forward.

* [[technical-debt|Technical Debt]] * [[semantic-debt|Semantic Debt]] * [[process-debt|Process Debt]] * [[resilience-debt|Resilience Debt]] * [[comprehension-debt|Comprehension Debt]] * [[rework-loop|Rework Loop]] * [[workaround-dependency|Workaround Dependency]]

* [Software Engineering Institute, “Managing Technical Debt in Complex Software Systems”](https://www.sei.cmu.edu/library/managing-technical-debt-in-complex-software-systems/) — supports the underlying tradeoff pattern that a short-term expedient approach can make later work cost more. It does not define the broader Debt family or taxonomy used in this glossary.

* Compare the family members: [[technical-debt|Technical Debt]], [[semantic-debt|Semantic Debt]], [[process-debt|Process Debt]], [[resilience-debt|Resilience Debt]], and [[comprehension-debt|Comprehension Debt]]. * Use [[rework-loop|Rework Loop]] and [[workaround-dependency|Workaround Dependency]] to inspect two ways an obligation can surface in operations.