Sometimes the real problem isn't the problem you think you're solving. The 5 Whys method is a root cause analysis technique that helps you peel back the layers of an issue, like an onion, until you reach what's actually causing it. It's a tool every problem solver, designer, or team lead should have in their kitchen.

Where does the 5 Whys technique come from?

The method has older roots than most people realize. Back in the 1930s, Sakichi Toyoda, the founder of Toyota, noticed something frustrating: teams kept patching the symptoms of problems, but the problems kept coming back. So he designed a simple framework to dig deeper instead of settling for surface fixes.

The idea is straightforward. You take your current problem, grab your metaphorical knife, and ask why five times in a row. Each answer becomes the starting point for the next question.

What is the 5 Whys method? It's a root cause analysis technique created by Sakichi Toyoda where you ask "why" five consecutive times to move past symptoms and uncover the real source of a problem.

How do I apply the 5 Whys to a real problem?

Let's walk through an example so you can see how the layers come apart. Imagine your current problem is this: the design project wasn't delivered on time. Sounds like a punctuality issue, right? Watch what happens when you start cutting.

• First why: Why wasn't it delivered on time? Because the design team didn't hand in the final files on time.
• Second why: Why didn't they hand them in? Because some team members didn't fully understand the client's specifications.
• Third why: Why didn't they understand? Because the initial briefing meeting moved too fast, packed too much information, and left no reference document.
• Fourth why: Why was the briefing like that? Because the manager assumed everyone on the team had equal experience with this type of project and skipped a formal summary.
• Fifth why: Why was that assumption made? Because there's no onboarding or documentation process for this type of project.

And there it is. The real issue wasn't the design team being late. It was the absence of a standardized process for these projects. Completely different problem, completely different solution.

Why does asking why five times actually work?

The power of this method is that it stops you from jumping to conclusions, and even worse, jumping to solutions that are just temporary patches. If you had stopped at the first why, you might have scolded the design team for missing a deadline. The deadline would be missed again next month.

By forcing yourself to keep digging, you separate symptoms from root causes. That distinction is what turns a quick fix into a structural improvement.

Do I always need exactly five whys? No. Some problems are solved in three whys, others need seven. Five is a guideline, not a rule. The goal is to reach the root cause, however many questions that takes.

What if my problem has more than one cause?

Not every problem comes from a single source. Sometimes you're dealing with systems, multiple overlapping causes, or chains that branch out. In those cases, you may need to run the 5 Whys on each branch separately, or think in terms of interconnected systems instead of a single line of questions.

The method is a thinking tool, not a rigid formula. Use it to slow down your reasoning, not to box it in.

When should I use the 5 Whys? Use it whenever a problem keeps coming back, when the obvious solution feels like a patch, or when you suspect the symptom you're treating isn't the real issue.

Your turn: run the 5 Whys on your own problem

Here's the challenge. Take the problem exactly as you've written it right now. Then run it through the 5 Whys exercise, one question at a time, without skipping ahead to solutions.

When you finish, ask yourself:

1. Did your problem stay the same?
2. Did it shift into something related but deeper?
3. Did it turn out to be a completely different problem?

Drop a comment with your original problem and what it became after the five whys. I want to see how many onions we peel together.