Some urgent problems arrive once and are solved. Others come back: the same last-minute scramble before month end, the same escalation from the same customer type, the same late approval that triggers a weekend of rework. Teams that respond heroically each time become skilled at firefighting. That skill can hide the fact that the cause remains.
A useful rule: the first occurrence is an incident, the second is a warning, and the third is a system problem. This article describes how to act on that rule.
Why heroics persist
Fire drills reward visible effort. The people who stay late and save the situation earn thanks, and leaders feel relief. Meanwhile, no time is available to examine why it keeps happening, because the next urgent item is already arriving. The organization adapts around the problem and slowly treats it as normal.
Step 1: Name the pattern
List the urgent problems of the past quarter and group them by type. Look for repeats: same trigger, same functions involved, same kind of late fix. Give each pattern a plain name, such as "month-end data scramble" or "contract exceptions at signing." A named pattern is easier to discuss than a series of unrelated emergencies.
Step 2: Reconstruct a timeline
Take one recent example and trace it backward. When did the problem first become knowable? Who knew? What was decided or not decided before it became urgent? A timeline often reveals that the emergency was visible days or weeks earlier, and that an earlier decision or handoff would have prevented it.
Step 3: Ask why more than once
A simple technique from Lean practice is to ask "why" repeatedly until you reach a cause the team can act on. For example: Why was the report late? Because the data arrived late. Why? Because one team sends it after its own review. Why? Because nobody agreed on a due date for it. Now there is something to fix. Stop when you reach a process, decision right, or agreement, not when you reach a person.
Step 4: Identify the type of cause
- Unclear priority. Teams were working on competing goals, and the urgent item lost out until it became critical.
- Unclear decision rights. A decision waited because no one owned it, and the delay created the emergency.
- Weak handoff. Work moved between groups without agreed content or timing.
- No early warning. The first sign of trouble was not visible or not safe to report.
- No review rhythm. Nothing in the calendar asked the question that would have caught it.
Step 5: Design one durable change
Choose a single change that addresses the cause, and give it an owner and a date. Examples: a due date and owner for the late input; a decision owner for contract exceptions; a five-minute check at the start of each week on items that could become urgent. Keep it small so it happens. Check after four weeks whether the pattern has changed.
Protect time for prevention
Prevention work competes with urgent work. Set aside a regular, short slot in the leadership review for recurring problems, and keep it even when the week is full. If it disappears under pressure, the cycle will continue. Leaders show what matters by protecting that time.
Credit prevention as well as rescue
Recognition shapes behavior. If heroic rescue gets the most praise, people may unconsciously allow problems to grow. Make a point of recognizing the person who prevented an emergency by raising an issue early or fixing a process, even though nothing dramatic happened.
A starting exercise
Choose the one fire drill that has cost your team the most over the last quarter. Spend forty-five minutes with the people involved building the timeline and asking why. Leave with one change and one owner. If you want help working through a recurring execution problem with your whole leadership team, the Culture-to-Execution Sprint is built around one live priority that keeps resurfacing.