Framing debt costs more than technical debt

Technical debt has its vocabulary, its measurement tools, its remediation sprints. Framing debt has almost none of this, and it causes the most damage.

What framing debt is

These are the questions that were not asked at launch because they seemed secondary, or because nobody had the authority to answer them. They always resurface, almost always at the worst possible moment.

Why it costs more

• It is discovered in production, never in a framing workshop
• It usually involves multiple stakeholders, meaning more decision cycles
• It calls into question choices already delivered, not just choices yet to be made

How to limit it

I systematically dedicate framing time to uncomfortable questions - the ones nobody raises spontaneously because the answer might be unwelcome. This time has an immediate, visible cost. Framing debt, on the other hand, has a deferred and invisible cost until the day it explodes.

A team that delivers fast on a shaky framing is not saving time, it is borrowing it at a rate it does not yet know.