Most teams can describe their technical debt but few can say what it costs them this quarter. That gap is the real problem: debt that isn't measured doesn't get prioritized against new feature work, so it accumulates by default.
We ask teams to track two numbers alongside their roadmap: time lost to workarounds in the last month, and the blast radius of the riskiest shortcut still in production. Neither number needs to be precise to be useful.