You've found a problem. Orders are late. Defects are up. Customers are complaining. Now what?
Most teams make the same mistake: they fix the symptom instead of the disease. Bandaids pile up. The problem returns. Everyone's frustrated.
The 5-Why technique cuts through this. It's simple, fast, and devastatingly effective.
How It Works
Start with your problem statement. Then ask "Why?" five times — each answer becoming the subject of the next question.
Example: Orders are shipping late
-
Why are orders shipping late?
→ Because the warehouse can't pack them fast enough. -
Why can't the warehouse pack fast enough?
→ Because they're waiting for inventory from receiving. -
Why is receiving slow?
→ Because trucks arrive at the same time and create a bottleneck. -
Why do trucks arrive at the same time?
→ Because all suppliers were given the same 9 AM delivery window. -
Why were they given the same window?
→ Because nobody ever reviewed the delivery schedule after we added new suppliers.
Root cause found: An outdated delivery schedule, not "lazy warehouse workers" or "we need more packers."
The Rules That Make It Work
Rule 1: Stay factual.
Don't jump to blame. "Because Bob is lazy" isn't a root cause — it's an accusation. Ask "Why is the task taking longer than expected?" instead.
Rule 2: Keep asking until you hit something you can control.
"Because that's how we've always done it" isn't an endpoint — it's the beginning of the real investigation.
Rule 3: Five is a guideline, not a law.
Sometimes you need three whys. Sometimes you need seven. Stop when you've reached something actionable.
Rule 4: Involve the people who do the work.
They know where the bodies are buried. Managers often have theories; workers have facts.
Common Traps to Avoid
❌ Stopping too early. "Because we don't have enough people" is rarely the root cause. Why don't you have enough people? Why does that task require so many people?
❌ Branching without exploring. Sometimes there are multiple contributing causes. Explore each branch, but don't get lost. Focus on the biggest impact first.
❌ Accepting the first answer. Challenge each response. Is that actually true? How do we know? What data supports it?
From Root Cause to Solution
Finding the root cause is step one. Step two is testing your fix before rolling it out.
This is where most teams stumble again — they implement a solution based on intuition, only to discover it created new problems.
Smart teams test their solutions in a simulation first:
- What happens if we stagger delivery windows?
- How does that affect warehouse staffing?
- Will we need to adjust packing schedules?
Run the scenario. See the results. Then make the change.
Today's Action: Take a recurring problem your team faces. Gather 2-3 people who deal with it daily. Spend 15 minutes asking "why" until you hit something you can actually fix. Write down what you discover — it's often not what you expected.
Once you've identified the root cause, don't guess at solutions. ProcessModel lets you test changes virtually before implementing them — so you fix problems once, not twice.