Technical debt
metaphor coined by Ward Cunningham (1992) for the implied cost of future rework caused by choosing an expedient solution in software development instead of a better approach
Technical debt (also known as design debt or code debt) is a qualitative description of the cost to maintain a system that is attributable to choosing an expedient solution for its development. While an expedited solution can accelerate development in the short term, the resulting low quality may increase future costs if left unresolved. The term is often used in the context of information technology and especially software development.
Technical debt is similar to yet differs significantly from monetary debt. Incurring either generally makes future goals more challenging to attain. But unlike monetary debt, technical debt is often incurred without intention. The choice to minimize development time and cost, an ever-present aspect of business, is the primary factor. Technical debt is generally only assessed retroactively (after a development effort).
Properly managing technical debt is essential for maintaining software quality and long-term sustainability. In some cases, taking on technical debt is a strategic choice to meet immediate goals, such as delivering a proof of concept or a quick release.
Begin with the source’s own compact description: “Technical debt” is metaphor coined by Ward Cunningham (1992) for the implied cost of future rework caused by choosing an expedient solution in software development instead of a better approach. The dossier treats that line as a proposition to test through Technical, debt and metaphor, not as a finished interpretation.
Why this record matters
The phrase “metaphor coined by Ward Cunningham (1992) for the implied cost of future rework caused by choosing an expedient solution in software development instead of a better approach” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Sep 19, 2026. The linked authority identifier is Q1532172. None of the 0 selected statements returned an explicit reference.
Scientific names, classifications and consensus can change while older terminology persists in catalogues and historical literature. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Technical debt”, its source revision and the description used here.
- Expand the search: follow Technical debt primary sources, Technical debt archive and Technical research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Technical debt”?
- Is the terminology current, historical or disputed?
- Which observation, specimen, dataset or publication supports the account?
Search terms from this dossier
This entry incorporates text from “Technical debt” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.