Every operations leader knows the pattern. A stockout happens, so someone expedites. A delivery is missed, so someone escalates. A month-end number disappoints, so someone builds a recovery plan. The fire gets fought, the quarter gets saved — and three months later the same fire starts again, in the same place, for the same reason.
The instinct is to treat these as operational problems: execution failures, people problems, bad luck. Occasionally they are. But the pattern we see most often across engagements is different: the problem that keeps recurring is almost never operational. It is structural — built into how the work is designed, not how it is executed.
The industry has a name for this — most businesses just don't use it
Quality management has formalised this distinction for decades. ISO 9001 explicitly separates correction — fixing the immediate nonconformity — from corrective action — eliminating the cause so it cannot recur. The standard requires both. Most businesses, in practice, only ever do the first.
The same thinking underpins the Toyota Production System's "5 Whys," root cause analysis in Lean and Six Sigma, and the corrective-action disciplines in every serious quality framework: the visible failure is treated as a symptom until proven otherwise. These are not consulting inventions. They are established industry standards — and the gap between businesses that apply them and businesses that firefight is one of the most reliable performance dividers we encounter.
The tell is repetition. An execution failure happens once. A structural failure happens on schedule. And if you replaced every person involved and the problem would still occur, then the people were never the cause — no amount of performance management will fix it.
Why the symptom keeps winning
Three reasons, mostly. Symptoms are visible — they appear on reports — while the design flaw that produced them appears nowhere. Treating symptoms feels like action: expediting and escalation are energetic and observable, while redesigning a planning process is quiet work that produces nothing dramatic until the fires simply stop. And in most organisations, nobody owns the structure: every function owns its own execution, but the design of how functions connect sits in the gaps between departments, where accountability is thinnest.
Five steps to move from correction to corrective action
1. Log problems by cause, not by incident. Most businesses track incidents (the stockout, the late delivery). Track the underlying cause instead, and recurrence becomes visible within one quarter — the same three or four causes usually account for the majority of incidents.
2. Apply structured root cause analysis — and stop at the design level. Use 5 Whys or a fishbone, but with one discipline: keep asking until the answer is about how the work is designed, not who was involved. "The planner missed it" is not a root cause. "The planning process has no mechanism for handling this demand pattern" is.
3. Assign ownership of cross-functional processes. Every end-to-end flow — order to delivery, plan to produce — needs a named owner whose accountability spans the departmental boundaries where structural flaws live. If nobody owns the seam, the seam stays broken.
4. Verify effectiveness, formally. ISO's corrective-action logic includes a step most businesses skip: after the fix, verify the cause is actually gone. Set a review date. If the problem recurs, the root cause analysis was wrong — go deeper.
5. Build a cadence that keeps structural attention alive. This is where most improvement quietly dies. Structural work competes with daily urgency and loses — unless a standing review rhythm exists that regularly asks: what recurred this quarter, and what does that tell us about design?
Sustaining it — the part that usually fails
The often-quoted research finding that the majority of change programmes fail to sustain their gains is contested in its precision but not in its direction: improvement erodes when the attention that created it moves on. The fifth step above is the defence — and it is precisely what our Kindred Programme is built to institutionalise: quarterly strategic reviews that surface recurring patterns before they become expensive, an accountability structure that keeps corrective action honest, and a standing advisory relationship so the structural questions keep being asked after the project energy fades.
The businesses that break the firefighting cycle are not the ones with the best firefighters. They are the ones that build the discipline of asking, every quarter, why the building keeps catching.