The Operations Bridge

5 Whys gets taught in every lean training deck, and it’s a genuinely useful tool. It’s also badly misused more often than it’s used well, and the misuse gives root cause analysis a bad name.

The Problem With Five, Specifically

Five isn’t a magic number. Sometimes the root cause is three whys deep, and stretching to five manufactures a cause that isn’t real. Sometimes it’s eight whys deep, and stopping at five hands you a symptom dressed up as a root cause. Teams that treat five as a hard rule end up with tidy-looking documents and untidy repeat failures.

The “Person” Trap

A 5 Whys chain that ends at “the operator made a mistake” hasn’t found a root cause. It’s found a place to stop looking. People rarely fail for no reason — they fail because a process let them, or made the mistake easy to make. If your chain lands on a person, ask one more why: what about the process allowed that mistake to happen and go uncaught?

Adding a Second Lens

The single biggest improvement I’ve made to root cause work wasn’t a new technique — it was pairing 5 Whys with a fishbone diagram before locking in an answer. The fishbone forces you to scan multiple categories (people, methods, machines, materials, measurement, environment) instead of following one linear chain of questions that can tunnel toward whatever cause is easiest to find.

Use 5 Whys to go deep once you know the direction. Use a fishbone first to make sure you’re looking in the right direction at all.

The Real Test of a Root Cause

You haven’t found the root cause until you can answer: if we fix only this, and nothing else, does the problem stop recurring? If you’re not confident in that answer, you haven’t reached the root — you’ve reached the point where the team got tired of asking why.