Five Whys, One Real Cause: A Story About Not Stopping Too Soon
The names below are invented, but the pattern is one any improvement practitioner will recognize. A regional services office kept missing a reporting deadline. It had happened three months running, and each time the response was the same: someone worked late, the report went out, and everyone moved on. The fourth time, the operations lead decided to stop treating the symptom and run a 5 Whys instead. The 5 Whys is one of the simplest tools in Lean — you ask "why" repeatedly until you reach a cause you can actually act on — and its simplicity is exactly where teams go wrong.
Walking down the chain
Done honestly, the conversation looked like this:
Why was the report late? Because the data arrived from the field offices on the last day.
Why did it arrive on the last day? Because the field offices submit only when reminded, and the reminder went out late.
Why did the reminder go out late? Because the person who sends it was covering two roles after a colleague's departure.
Why was one person covering two roles? Because the vacancy had been open for months during a hiring freeze that began in the 2020 downturn.
Why hadn't the process adapted to the gap? Because no one owned the reminder step; it had always just happened, so its fragility was invisible until the person doing it was stretched.
Where most teams stop too early
Notice how tempting it was to stop at the first or second why. "The data arrived late" invites a fix — chase the field offices harder — that treats the symptom and guarantees the problem returns. Even "the reminder went out late" points only at a person, which slides toward blame rather than cause. The Lean discipline is to keep asking until you reach something about the process or the system, not the individual. The real cause here was not a tardy employee; it was an unowned, undocumented step that worked only as long as one stretched person remembered it.
A word of caution that experienced practitioners insist on: "five" is a guideline, not a rule. Sometimes the real cause appears at the third why; sometimes you need seven. And a single problem can have more than one branch — late data and an unclear deadline might both contribute, each deserving its own chain. The number is far less important than the honesty. If your answer to a why is a name, you have probably not gone deep enough.
The fix, and why it held
The office did not hire its way out, which the freeze would not have allowed anyway. It assigned clear ownership of the reminder step, documented it as a standard with a date, and added a simple automated trigger so the step no longer depended on one person's memory. The deadline stopped being missed. Because the team had fixed the cause rather than the symptom, the solution survived the next staff change too — which is the entire point of root-cause analysis.
If recurring problems in your organization keep getting patched rather than solved, XNM's strategic advisory can help you get to the root cause and build fixes that actually hold.