Talking to non-engineers about technical debt

Say 'technical debt' to a non-engineer and you often get a polite nod, because it sounds like a vague excuse for slow progress. It isn't. It's a real, measurable tax on every future change, and it deserves a clearer name.

The metaphor that lands

We describe it as interest: every shortcut you take out now, you pay back later with interest, in the form of slower features and surprising bugs. That framing turns an abstract worry into a budgeting conversation.

• Show the cost in time, not in jargon. 'This will take a week instead of a day' lands.
• Separate 'ugly but fine' from 'fragile and risky' so effort goes where it matters.
• Agree on a small, regular allowance for paying it down, like maintenance on a building.

Once stakeholders see debt as a predictable cost instead of a mystery, the conversations get a lot more productive.