Compound Interest Works Both Ways

Compound Interest Works Both Ways: Technical Debt & the Choices We Make  

We all understand compound interest when it comes to money—small, consistent investments grow exponentially over time. But the same principle works in reverse. In software development, every shortcut you take, every time you skip the craft practices that make code maintainable, you’re taking out a loan against your future velocity. And the interest rate? It’s brutal.

This talk explores why technical debt is invisible until it becomes catastrophic, why organizations celebrate firefighting over fire prevention, and how most teams have normalized perpetual crisis mode. You’ll learn to distinguish genuine emergencies from false urgency, understand why quality practices aren’t a luxury but the most cost-effective investment you can make, and discover how to shift your organization from compound interest working against you to working for you.

Key Topics  

• The Visibility Problem: Why technical debt doesn’t ring alarm bells until it’s too late
• The Prevention Paradox: Why we celebrate the firefighter but ignore the fire prevention engineer
• False Urgency vs. Real Crisis: How to distinguish between genuine emergencies and normalized dysfunction
• Making Trade-offs Explicit: Stop pretending shortcuts are free—every choice has a compounding cost
• Metrics That Matter: The four key metrics that reveal your true technical health
• Cultural Shifts: From “ship fast, fix later” to sustainable velocity
• Real Examples: Teams that transformed from drowning in debt to accelerating with quality

Learning Outcomes  

• Understand how compound interest applies to software development and technical debt
• Identify the warning signs of accumulating technical debt in your organization
• Recognize perverse incentive structures that reward firefighting over prevention
• Learn practical metrics for tracking technical health (cycle time, unplanned work percentage, lead time for changes, change failure rate)
• Discover actionable steps to shift organizational culture toward sustainable quality
• See real examples of teams that paid down technical debt and dramatically improved velocity

Who Should Attend  

This talk is valuable for:

• Engineering Leaders who struggle to justify quality investments to stakeholders
• Individual Contributors who feel pressure to cut corners and want to advocate for better practices
• Product Managers who want to understand why development slows down over time
• Executives who wonder why their teams can’t move as fast as they used to

Presentation Dates  

Resources  

Slide deck  - HTML presentation with speaker notes

Related Content  

Links  

Martin Fowler: Technical Debt 
Ward Cunningham: The WyCash Portfolio Management System  ( origin of “technical debt” metaphor)
Compound Interest  - Wikipedia
Prevention Paradox  - Wikipedia
Perverse Incentive  - Wikipedia

Books  

Accelerate: The Science of Lean Software and DevOps  - Nicole Forsgren, Jez Humble, Gene Kim
The Phoenix Project  - Gene Kim, Kevin Behr, George Spafford
Extreme Programming Explained: Embrace Change  - Kent Beck

Additional Resources  

DORA State of DevOps Reports  - Research on high-performing teams
Technical Debt Quadrant  - Martin Fowler’s framework for categorizing technical debt