Explain like I'm five · SW Eng

What is Technical Debt?

Technical debt, told as a story about a publishing house piling up the things it kept postponing under deadline pressure.

let's just ship it like this and fix it later!the deadline's right here, so the flawed manuscript goes through as-is

With the deadline right here, the editor says 'ship it now'.The deadline's right here, so the flawed manuscript goes through as-is.

postponed fixes piled up — more to fix nowpublishing was fast back then, but every fix is slower now

Postponed fixes have piled up — there's more and more to fix.Publishing was fast back then, but every fix is slower now.

LEDGER: postponed worktechnical debt = a debt piled up to move fast now, to be repaid laterleave it unpaid, and it grows like interest (rising cost to fix)

Technical debt is a debt piled up to move fast now, repaid later.Leave the debt unpaid, and the cost to fix grows like interest.

Debt taken on knowinglychosen on purpose, when it's urgent
Debt piled up unnoticedfrom a mistake or not knowing better
Left unpaid, it grows like interestthe cost to fix just keeps rising
Record it, repay it on purposewith a real plan to pay it off
HOW THE DEBT PILES UPdeliberate — knowingly chosen, for speedinadvertent — a mistake, unnoticedWHEN TO REPAYpostponing costs little right nowlater the fix cost grows like interestdeliberate or not, write it in the ledger and repay it on purpose

Debt can be taken on knowingly, or pile up without anyone noticing.Deliberate or not, the debt needs to be recorded and repaid on purpose.

chasing zero debt can easily cost you the deadlinewrite it down, repay it on purposethe point isn't erasing debt — it's recording and repaying it on purpose

The debt doesn't need to hit zero.The point isn't erasing debt — it's recording and repaying it on purpose.

In one breath

Technical debt is the 'debt' of work postponed to move fast now. Left unpaid, the cost to fix it keeps growing like interest.

Technical debt is a metaphor for the future cost incurred when a faster, lower-quality approach is chosen over a better design now. It splits into deliberate debt (knowingly taken on) and inadvertent debt (accumulated without realizing it); left unpaid, the cost to fix it compounds like interest. The goal isn't zero debt — it's tracking it in a backlog and repaying it deliberately.

When grown-ups say it

Technical Debt
A debt that must be repaid later. Left unpaid, it grows like interest.
Deliberate Debt
Debt knowingly taken on, for speed. Not bad in itself — recording it is what matters.
Inadvertent Debt
Debt that piles up from an unnoticed mistake. Often discovered only much later.
Refactoring
The classic way to repay this debt. Keeping the plot the same while reworking the structure. → same plot, retouched sentences
Code Smell
The whiff of sentences gone tangled. A sign the debt is piling up.
WBS
The task tree a schedule is built from. Too tight a WBS schedule, and technical debt piles up. → laying out the book as a tree
IS Audit/PMO
The outside checker watching whether debt has piled up too far. Watching schedule and quality can reveal debt building up. → the checker who watches the whole publishing run
Unit Test
The proofing that checks the plot held while the debt is repaid. Without tests, repaying debt safely is hard.
Next story
Different Editing Rules for Each Book →
Want another term as a picture book? Request →