Skip to content
Founders’ price Launch pricing for your first twelve months. 40 Playbooks, 40% discount for Founders. View the playbooks →

Technical Debt Quadrant

TTool · Technical Debt Quadrant

By , Editor · · What’s Next

“Martin Fowler's categorisation framework distinguishes between deliberate and inadvertent debt, and between reckless and prudent debt.”

The backlog says "tech debt" in six places. Nobody can explain which items are deliberate choices and which are accidents. The remediation conversation keeps stalling.

Technical Debt Quadrant is Martin Fowler's classification framework. You categorise debt along two axes — deliberate versus inadvertent, and reckless versus prudent — producing four quadrants that demand different responses.

A 2x2 matrix with vertical axis "impact on the work" (high to low) and horizontal axis "cost of living with it" (low to high), splitting debt into four quadrants: fix first, schedule, decide, and tidy in passing.
Method visual — Technical Debt Quadrant

Deliberate-prudent debt is a strategic tool: you shipped now, knowing the consequences, with a plan to address them. Deliberate-reckless debt is a knowing shortcut with no remediation plan. Inadvertent-prudent debt emerges when teams discover a better approach after building — unavoidable learning. Inadvertent-reckless debt results from gaps in skill or oversight.

The framework's power is precision. "We have tech debt" is a conversation-stopper; "we have deliberate-prudent debt from the launch deadline and inadvertent-reckless debt from last year's contractor" is a conversation-starter. It fails when teams use it to excuse all debt as prudent, or when classification replaces action — naming the quadrant without planning the fix.

Your next move: Which 'tech debt' on your team's list is actually deliberate-prudent (a real trade-off) versus inadvertent-reckless (something nobody wants to admit was a mess) — and which conversation are you avoiding by lumping them together?

What it looked like for them

A growing engineering team, mid-2010s. As the team scaled past twenty engineers, one senior architect had become the sole owner of architectural knowledge. Every decision ran through him — not by policy, but because nobody else understood the system well enough to make calls independently.

The team had accumulated a specific kind of technical debt: knowledge debt. It was deliberate (the architect was trusted and effective) and prudent (centralising decisions had prevented mistakes during the early days).

But as the team grew, what had been prudent became reckless — a single point of failure that slowed everything. The technical debt quadrant would have classified this clearly: deliberate-prudent in year one ("we know we're concentrating knowledge, but it's the right trade-off for now") shifting to deliberate-reckless by year three ("we know this is a bottleneck and we're choosing not to fix it").

The quadrant doesn't just name the debt. It tracks how the same debt changes character as circumstances change. What's prudent at one scale becomes reckless at another.

- returns a SafeString and get.js throws on it }}
A move inside a Playbook

“The dashboard says we're fine but I don't believe it.”

Open the Playbook →

Share the Playbooks