The 5 Whys Method: The Simplest Problem-Solving Tool You're Probably Not Using

You know that feeling when something goes wrong and everyone jumps straight to fixing the symptom? The button's broken, so we fix the button. The page is slow, so we add caching. The customer complained, so we give them a discount. Problem solved, right?

Except the same problem comes back two weeks later, because nobody asked why it happened in the first place.

The 5 Whys method is dead simple: when you hit a problem, ask "why" it's happening. Then take that answer and ask "why" again. Keep going until you reach the actual root cause — usually somewhere around the fifth "why," though sometimes it takes fewer, sometimes more.

It's not a fancy framework. You don't need special software. You need a pen, some paper, and the willingness to keep digging when the first answer feels "good enough."

The Jefferson Memorial story

This is the classic example, and it's a real one.

Park rangers at the Jefferson Memorial in Washington noticed the stone exterior was deteriorating. The obvious fix: repaint or replace the stones. Expensive, time-consuming, and — as it turned out — completely unnecessary.

Instead of jumping to the fix, they started asking why.

Why is the building deteriorating?
Because it gets cleaned with high-pressure sprays too often.

Why does it need to be cleaned so often?
Because pigeons cover it in excrement.

Why are there so many pigeons?
Because there are clusters of spiders everywhere — easy food for the birds.

Why are there so many spiders?
Because insects swarm the building, and spiders follow the food.

Why are there so many insects?
Because the lights used to illuminate the monument at night attract them.

The root cause of deteriorating stonework was the lighting schedule. They changed when the lights turned on, the insects stopped swarming, the spiders left, the pigeons moved on, the building stayed clean, and the stone stopped deteriorating.

All that from asking "why" five times instead of ordering new stone.

Where this is actually most useful

The method really shines in one specific situation: when you're talking to people and trying to understand a problem they're experiencing.

Say you're doing user research or a customer interview. You ask someone about a pain point and they give you an answer. The answer sounds reasonable. But it's not the root — it's the surface. People aren't lying to you. They just don't always know the deeper reason behind their own behavior, or they've never been asked to dig into it.

The 5 Whys gives you a way to go deeper without making it feel like an interrogation. Each "why" peels back a layer. By the third or fourth one, you're usually somewhere interesting — a place the person themselves hadn't fully articulated before.

How to actually do it

Grab a pen and paper. You can do it digitally, but there's something about writing it out by hand that keeps it grounded. Here's the process:

Start with a specific problem statement. Not "things aren't going well" — something concrete. For the Jefferson Memorial, it was "the building is deteriorating." For a product issue, it might be "users abandon the signup flow at step 3."

Write down your first "why" and the answer you get. Then ask "why" based on that answer. Keep going. Write everything down, because the trail of answers might lead somewhere you didn't expect.

A few things to keep in mind:

You might hit the root cause at question three. You might need seven questions. Five is a guideline, not a rule. Stop when you've reached something actionable — a cause you can actually address.

Set a goal before you start. What do you want to understand by the end of this? Write it down so you don't drift.

Note how the problem affects the business and how many users it touches. This context helps you decide later whether the root cause is worth fixing or whether it's a minor issue you can live with.

Don't assume the answers. Even if you think you know, ask anyway. Let the other person answer. Their version of reality might be different from yours, and that difference is valuable information.

The awkward part nobody warns you about

Here's what actually happens when you use this method with real people: it gets uncomfortable. Not for you — for them.

I've gotten these reactions more than once:

"Why do you keep asking? Don't you already know the answer?"

"I just told you the reason. There's no other reason."

And sometimes people just get visibly annoyed. Being asked "why" five times in a row can feel like being questioned by a toddler or cross-examined by a lawyer. Neither is great for building rapport.

The workaround that's worked for me: swap "why" for "how come?" It's softer. It doesn't feel like you're challenging their answer — it feels like you're genuinely curious. Same technique, different packaging, much better response.

You can also mix in variations: "What do you think caused that?" or "What was behind that decision?" The point is to keep going deeper, not to robotically repeat the word "why."

What's good about it

It's simple. No tools, no training, no certification. Pen and paper.

It forces you to understand how things are connected. You start seeing how one small thing causes a chain reaction that leads to the actual problem. That understanding is valuable even if you don't fix anything immediately.

Once you know the root cause, you can make better decisions about solutions — including whether the solution is even worth pursuing. Sometimes the root cause reveals that the problem isn't as bad as the symptom made it look.

And it keeps you in conversation with people. In a world where we default to analytics dashboards and survey data, sitting with someone and asking "why" five times is surprisingly revealing.

When it doesn't work

Not always. Some problems are too complex for a single chain of "why" questions. The root cause might be a combination of five different things, not one thing buried under five layers. For those situations, you need more structured root cause analysis.

And sometimes people genuinely don't know the answer. You can ask "why" all day, but if the person doesn't have visibility into the cause, you're just going in circles.

It's a tool, not a universal solution. But for the kinds of problems startups deal with daily — user behavior you don't understand, bugs that keep coming back, processes that feel broken — it's worth trying before reaching for something heavier.

Give it a shot

Next time something goes wrong and your instinct is to jump straight to fixing it, pause. Grab a piece of paper. Write down the problem. Ask why. Write the answer. Ask why again.

You might be surprised where you end up. And the fix you land on will probably be cheaper, simpler, and more lasting than the one you would have jumped to.

Ask why like a child, 5 whys method

Latest blogs