The Problem with “Just Ask Why” (and What to Do Instead)

By
3 Minutes Read

“Have you tried the Five Whys?”

It’s usually the first thing people reach for when something goes wrong.

And to be fair, it’s not a bad instinct.

You’re trying to move past symptoms and get to the real cause. That’s exactly the right goal.

But here’s what I’ve seen over and over again.

Teams use the Five Whys… and still end up fixing the wrong thing.

Not because the tool is broken. But because of how it’s used.

Why the Five Whys Feels Right

It’s simple.

Start with a problem, ask “why” repeatedly, and eventually you land on a root cause.

Example:

  • The machine stopped
  • Why? The motor overheated
  • Why? The bearing failed
  • Why? It wasn’t lubricated
  • Why? Maintenance was missed
  • Why? The schedule wasn’t followed

Clean. Logical. Easy to follow.

But here’s the issue.

Real-world problems don’t behave in straight lines.


Where It Starts to Break Down

In practice, most failures don’t come from one chain of causes.

They come from multiple conditions lining up at the same time.

Let’s take that same example and look a bit closer.

The bearing failed

 

  • Because lubrication was missed
  • AND contamination entered the housing
  • AND the load increased beyond normal conditions

 

Now ask yourself: Which “why” do you pick?

If you follow just one path, you ignore the others.

 

And that’s how you end up with actions like:

  • “Remind maintenance to follow the schedule”

Meanwhile, contamination is still getting in.

Load conditions are still not understood.

The problem comes back.


The Hidden Limitation of the Five Whys

The Five Whys assumes:

  • One cause leads to one effect

But in most industrial environments:

  • Multiple causes combine to create a single outcome

That’s a very different problem to solve.

 

It’s the difference between:

  • Finding a cause
  • Understanding the system of causes

Once you see that, you can’t unsee it.


How to Use the Five Whys Properly

I’m not saying throw it out.

Used well, it’s a great thinking tool.

But it needs a slight shift.

1. Don’t Stop at One Answer

When you ask “why,” allow for more than one answer.

If two things contributed, capture both.

That alone improves the quality of your thinking.

2. Anchor Every Answer in Evidence

This is where most Five Whys exercises quietly fall apart.

People fill in the blanks with what they believe.

Instead, ask:

  • How do we know this is true?
  • What evidence supports it?

If you can’t answer that, it’s a hypothesis, not a cause.

3. Build Out, Not Just Down

Instead of going straight down a single chain, start building sideways.

You’ll end up with something closer to a cause-and-effect map than a list.

That’s where the real insight starts to show up.

4. Pressure Test the Logic

Walk it through step by step.

If someone unfamiliar with the problem can’t follow it, there are gaps.

And those gaps are usually where repeat failures hide.


A Quick Reality Check

If your RCA typically ends with:

  • Human error
  • Training issue
  • Procedure not followed

There’s a good chance the Five Whys didn’t go far enough.

Those are often outcomes, not underlying causes.


What High-Quality RCA Looks Like

When teams move beyond a basic Five Whys approach, a few things change:

  • Conversations shift from opinions to evidence
  • Different perspectives start to align
  • Solutions target conditions, not just people
  • Problems stop repeating

It’s not more complicated. It’s just more structured.


If You’re Using the Five Whys Today, This Is Your Next Step

Most people aren’t doing RCA poorly on purpose.

They’ve just never been shown what “good” looks like beyond a simple tool.

That’s exactly why this guide exists:

“My Boss Told Me to Do an RCA, Now What?”

It takes the thinking behind tools like the Five Whys and builds it into a clear, practical approach you can actually use on real problems.

Inside, you’ll see:

  • How to move from a vague issue to a clear problem statement
  • How to separate evidence from assumption
  • How to map multiple causes, not just one chain
  • How to build solutions that hold up over time

It’s the step most people are missing after learning the Five Whys.

You can download it here.


Final Thought

The Five Whys is a good starting point.

But it’s not the finish line.

If you’ve ever walked away from an RCA thinking, “We did this already… why is it happening again?”

There’s a good chance the problem wasn’t effort. It was structure.

And once you fix that, everything else gets easier.



Visit our website to know more about Sologic.

Picture of Sologic

Sologic

Sologic leads the way in problem-solving across sectors and disciplines — from the shop floor to the boardroom. Through expert-led training, purpose-built software, and strategic guidance, we help teams break through recurring issues and deliver long-term improvements that stick. At the core of our work is a powerful, structured Root Cause Analysis methodology — designed to uncover the true causes of problems and implement solutions that prevent repeat failures. By combining logical analysis with creative thinking, Sologic enables more informed decisions, stronger cross-functional collaboration, and lasting operational gains. Trusted by industry leaders around the world, Sologic RCA underpins critical processes in reliability, safety, risk mitigation, and continuous improvement. From mining and utilities to manufacturing and healthcare, organisations use our tools and expertise to build essential problem-solving skills, streamline investigations, and transform the way teams work together. Sologic doesn’t just help solve problems — we help build a culture that prevents them.

Author