Let’s flip the table. Instead of considering technical debt like this shapeless burden that just happens to be there, let’s analyse debt’s characteristics and when and how it appears. Then let’s dig into how we can get an accurate view of technical debt at the scale of a complex system operated by a large number of teams. Finally, let’s take a look at the tooling we built at TheFork to enable this, as well as the ways of working we imagined to trigger action following measurement.