In this episode of Definitely Maybe Agile, Peter Maddison and Dave Sharrock tackle "longstanding risks" – those temporary solutions that somehow become permanent fixtures in our systems. From memory-leaking services to utility companies skipping maintenance, they explore how small shortcuts create massive long-term costs.
Key Topics:
Why quick fixes become permanent problems
The hidden costs of technical debt
How to document temporary solutions properly
Building resilient systems vs. preventing all failures
Real-world examples of maintenance shortcuts gone wrong
Timestamps:
0:00 Introduction to Longstanding Risks
3:01 The Memory Leak Example
5:46 Time Trade-offs and Documentation
8:20 Understanding Consequences of Quick Fixes
11:40 Recommendations for Better Risk Management
14:30 Shifting Mindsets About System Failures
16:43 Episode Closing
This Week's Takeaways:
Document your band-aids with clear reasoning and next steps
Protect team capacity to enable thoughtful decision-making
Focus on system resilience rather than trying to prevent every failure
Perfect for engineering leaders, DevOps teams, and anyone managing complex technical systems. Subscribe for more insights on scaling agile practices and building maintainable systems.