The 5 Whys: Finding Root Cause, Not Symptoms

When a project goes wrong, everyone arrives with a theory, and most of those theories point at symptoms rather than causes. The 5 Whys is a simple discipline for cutting through that noise: state the problem, then ask "why?" five times in a row, letting each answer become the subject of the next question. A missed launch traced back through five layers might move from "found the bug late" all the way down to "no one owned the timeline," which is a very different problem to solve. Fixing the surface symptom changes nothing, while fixing the root cause is what keeps the failure from repeating.

The method works best when each layer stays visible, so the team can see the chain of reasoning instead of holding it in their heads. That's where a set of write-on blocks turns the exercise into something the whole room can follow.

How Switch-Its run the 5 Whys

Switch-Its magnetic dry-erase blocks let a team write the problem at the top, then build a descending column of "why?" blocks with each answer captured on its own block beside the question. Because the blocks are rewritable and rearrange instantly, the chain can be revised on the fly as the team tests whether each answer really leads to the next.

Name the problem

Start with the problem at the top, here a missed launch, then line up five "why?" blocks beneath it. The structure commits the team to digging five layers deep before settling on an answer.

Answer each why

Work down the chain one layer at a time. Found the bug late leads to tested too late, which leads to no mid-cycle checks, with each answer feeding the next question.

Reach the root cause

The final why lands on the real source: no one owned it. With the root cause named, the team can attach a fix that targets the cause, like assigning a coordinator.

Laying the whole chain out in front of the team keeps the analysis honest, because a weak link is obvious the moment a "why?" doesn't actually explain the layer above it. Working all the way to the root cause and pairing it with a concrete fix is what separates chasing symptoms from genuine problem-solving, and the same five-block structure can be reset for the next retrospective in seconds.