Technical Debt

The implied cost of additional rework caused by choosing an easy (limited) solution now instead of using a better approach that would take longer. Like financial debt, technical debt incurs 'interest'—the ongoing cost of working around, maintaining, and eventually fixing shortcuts. Some technical debt is strategic (shipping fast to test demand); some is accidental (not knowing better). The danger is that it compounds silently until it paralyzes development.

When to use it

When deciding between 'ship it fast' and 'build it right.' When development velocity is declining despite team growth (debt is accumulating). When planning refactoring or modernization efforts.

How it can help

Provides the framework for managing the speed-quality trade-off in any technical or creative work. Helps leaders make informed decisions about when shortcuts are worth it and when they're creating compounding future costs.