Question 1

What is technical debt?

Accepted Answer

Technical debt is a metaphor describing the future cost of additional rework created when a team chooses a faster, easier solution now instead of a more thorough approach that would take longer to build.

Question 2

Who coined the term "technical debt," and when?

Accepted Answer

Ward Cunningham coined the term in 1992 while working on the WyCash portfolio management system, one of the earliest environments experimenting with extreme programming.

Question 3

What did Cunningham actually mean by the metaphor?

Accepted Answer

He meant specifically the natural gap between a team's evolving understanding of a problem and code already written for an earlier, incomplete version of that understanding, paired with a genuine commitment to refactor promptly, not permission to write careless code.

Question 4

What is Martin Fowler's Technical Debt Quadrant?

Accepted Answer

It is a 2009 framework classifying debt along two axes, deliberate versus inadvertent, and reckless versus prudent, producing four distinct categories that distinguish strategic tradeoffs from genuine culture or skills problems.

Question 5

What is the difference between principal and interest in technical debt?

Accepted Answer

Principal is the actual cost of eventually fixing or refactoring the shortcut, while interest is the ongoing, recurring drag on productivity every time the affected code has to be touched again while the debt remains unpaid.

Question 6

Why should product managers care about technical debt?

Accepted Answer

A push for a faster deadline is very often, functionally, a request to accept some form of technical debt, whether or not the product manager frames it that way at the time.

Question 7

Is all technical debt bad?

Accepted Answer

No. Prudent, deliberate debt, taken on consciously with a real repayment plan, can be a genuinely smart, strategic tradeoff, much like a mortgage taken on with clear eyes.

Question 8

What is "technical bankruptcy"?

Accepted Answer

Technical bankruptcy is the point at which accumulated, unpaid technical debt has made a system so expensive and risky to maintain that a full rewrite becomes genuinely cheaper than continuing to service the existing debt.

Question 9

What is a common misuse of the term "technical debt"?

Accepted Answer

A common misuse is using it as a blanket excuse for sloppy, careless work with no genuine deliberate tradeoff or real repayment plan, which directly contradicts Cunningham's original intent.

Question 10

How should product managers help manage technical debt?

Accepted Answer

They should classify debt using a framework like Fowler's quadrant, track it against real productivity and defect data, and ensure any deliberate debt has an actual, specific repayment plan rather than remaining an open-ended liability.

What Is Technical Debt and Why Should PMs Care?

Learn better with active recall quiz

Q1: What is technical debt?

Frequently Asked Questions