Article · 9 min read

How to break the cycle of firefighting

LeadDev Free Intermediate

Buffer time only works if the fires eventually get smaller, and this piece is about exactly that: how to stop reactive work from permanently crowding out the important-but-not-urgent work that would prevent the next fire. It uses the iceberg model (events, patterns, structures, mental models) to push you past patching today's crisis toward the leverage points, tiered support, error budgets, incident retros, that quietly reduce how often you burn. It is the counterweight to just leaving slack: the slack absorbs this week's chaos, this frames the quadrant-2 work you pull into that slack on the calm weeks so next month has fewer emergencies.

  • Firefighting is a symptom of structure, not bad luck: fix the recurring pattern, not just today's incident
  • Find leverage points (error budgets, tiered support, streamlined approvals) where a small change prevents many future fires
  • Protect proactive quadrant-2 work by scheduling it before it becomes urgent, or urgent work will always win the day
Open on leaddev.com ↗

The question it answers

  1. How do I plan my week when a customer emergency or a burning production bug can blow up any day?

Read with it

  1. This is the rare piece that gives you the actual number instead of vibes: plan a sprint to about 80% and hold 20% back as an... Boldstart Ventures Article · 10 min read How engineering teams handle unplanned work Anna Debenham
  2. Trenchard has watched a lot of founders run their calendars, and his core move is the one that makes buffer-based planning... First Round Review Article · 15 min read 70% of Time Could Be Used Better: How the Best CEOs Get the Most Out of Every Day Bill Trenchard
eChai Partner Brands The partnership →