Skip to content
Nerdy beta

Technical Investment

Technical debt is a strategic choice, not a dirty word. The question isn't whether you have it; it's whether you're managing it with intention or letting it manage you.

Technical investment is how we talk about the strategic side of technical debt: understanding it, measuring it, and making informed decisions about when to pay it down. The Technical Debt Metaphor gives teams a shared language for trade-offs between speed and sustainability. Technical Debt Quadrants help classify debt by intent and awareness, so you can distinguish deliberate shortcuts from accidental messes. The Discover-Option-Action Cycle provides an outcome-first approach to measuring whether your technical investments are actually paying off. And as AI accelerates how fast code drifts from a team’s understanding of it, Cognitive and Intent Debt surfaces two quieter layers, shared understanding and externalized intent, that managing code quality alone no longer covers.

Resources

Articles

Cognitive and Intent Debt

Margaret-Anne Storey's triple debt model and why AI accelerates the two invisible layers, cognitive debt and intent debt.

Discovery-Option-Action Cycle

An outcome-first model for selecting and validating metrics that gauge progress toward desired results.

Technical Debt Metaphor

Ward Cunningham's original metaphor explaining why shipping imperfect code can be a rational economic decision.

Technical Debt Quadrants

Martin Fowler's two-by-two matrix classifying technical debt by intent (deliberate vs. inadvertent) and discipline (reckless vs. prudent).