Glossary/Technical Debt Quadrant
Technical Debt & Code Quality
1 min read
Share:

What is Technical Debt Quadrant?

TL;DR

The Technical Debt Quadrant is a classification framework by Martin Fowler that categorizes technical debt along two axes: deliberate vs.

The Technical Debt Quadrant is a classification framework by Martin Fowler that categorizes technical debt along two axes: deliberate vs. inadvertent, and reckless vs. prudent.

Reckless + Deliberate: "We don't have time for design." The team knowingly takes shortcuts without planning to fix them.

Reckless + Inadvertent: "What's layering?" The team doesn't know enough to realize they're creating problems.

Prudent + Deliberate: "We must ship now and deal with consequences." The team understands the tradeoff and has a plan to address the debt.

Prudent + Inadvertent: "Now we know how we should have done it." The team learns better approaches only after building the first version.

The quadrant helps teams and leaders communicate about debt more precisely. "We have tech debt" is vague. "We have prudent deliberate debt from the Q3 launch that's now costing us 20 hours/sprint" is actionable.

Why It Matters

The quadrant framework enables more nuanced conversations about technical debt with non-technical stakeholders. Not all debt is equal — prudent deliberate debt can be a smart business decision, while reckless inadvertent debt indicates a training and process problem.

Frequently Asked Questions

What is the technical debt quadrant?

A framework by Martin Fowler that classifies technical debt as reckless/prudent and deliberate/inadvertent. It helps teams communicate about different types of debt more precisely.

Is all technical debt bad?

No. Prudent deliberate debt — knowingly taking a shortcut to ship faster with a plan to fix it — can be a smart business decision. The key is that it must be measured, tracked, and repaid on schedule.

Related Terms

Need Expert Help?

Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.

Book Advisory Call →