Classify the affected boundary
Code debt often concerns local structure such as duplicated policy or confusing responsibilities. Architecture debt concerns relationships among components, including coupling and data ownership. Test debt limits confidence in changes, while delivery debt makes building, deploying, or recovering the application unnecessarily difficult or dependent on manual knowledge.
Knowledge or documentation debt makes important decisions expensive to recover. Dependency and data constraints can also deserve explicit categories in your register. These labels are a practical working taxonomy, not an exhaustive universal standard. Choose categories that help your team assign owners and identify the right evidence.
Describe the decision context separately
The Technical Debt Quadrant distinguishes deliberate from inadvertent debt and prudent from reckless choices. An intentional shortcut with a known consequence differs from a constraint discovered after learning more about the domain. Neither dimension tells you automatically when the debt should be addressed in today's system.
Illustrative scenario: a team temporarily duplicates an adapter to meet a fixed integration deadline and records a replacement condition. That is different from unnoticed policy duplication discovered months later. Both may create code debt, but the decision history and appropriate prevention work are different.
Use classification to choose the next action
Tag an item with its dominant affected boundary and any relevant secondary categories. A tangled data-access module may involve architecture, tests, and knowledge. Keep one accountable owner and a clear next step rather than creating several disconnected tickets that all describe the same underlying constraint.
Prioritize using actual impact, upcoming changes, and intervention risk instead of category prestige. Architecture debt is not automatically more urgent than a fragile release process. A useful classification helps route investigation and verify improvement; it should not replace the evidence needed to make a product tradeoff.
Working sheet
| Type | Illustrative constraint | Useful first evidence |
|---|---|---|
| Code | Duplicated eligibility policy | Affected modules and inconsistent edits |
| Architecture | Reporting depends on payment internals | Dependency and data ownership map |
| Test | Critical rules lack reliable checks | Unverified behavior and flaky-test history |
| Delivery | Manual release depends on one laptop | Reproduction of build and deployment steps |
| Knowledge | Unexplained retry behavior | Recovered intent and characterization examples |
Use the debt quadrant as a discussion aid
The deliberate or inadvertent and prudent or reckless distinctions describe how a compromise was made. They do not replace evidence of its current impact.
Record what was known when the decision was made, the benefit it bought and the trigger for revisiting it. Avoid using the quadrant to assign blame to earlier maintainers.
Questions about types of technical debt and how to classify them
Are the debt types mutually exclusive?
No. One constraint can span several areas. Use categories to clarify ownership and investigation rather than force an artificial single label.
Is architectural debt the same as deliberate debt?
No. Architectural describes the affected system structure; deliberate describes whether the team knowingly made the tradeoff.
How should I use the working sheet?
Download the CSV and replace the sample rows with evidence from your repository. Record a clear acceptance check and an owner for each item. Keep unresolved assumptions visible rather than treating the example as a completed assessment.
Sources and further reading
Examples are illustrative. They are not customer results, security guarantees, or a substitute for checking the documentation for your installed version.
