Free Tool · No Signup Required

Find the Root Cause
of Any Problem

Ask “Why?” five times to dig beneath symptoms and uncover the real issue. Based on the Toyota Production System — used by Lean & Six Sigma teams worldwide.

Step-by-step guided No data collected Export as PNG

14,200+ analyses completed Works offline 100% private

Step 0 — Start

Describe your problem

Start with a specific, observable symptom. What is happening? When? How often? What is the impact?

Be specificDescribe a measurable fact, not a vague impression.
Don't assign blameFocus on the process, not on individuals.
Don't suggest a solutionDescribe the symptom, not the remedy.
How to write a good problem statement?

A good problem statement is the foundation of the entire analysis. If you define it poorly, the whole causal chain will go in the wrong direction.

Try to include:

  • What exactly is happening (observable symptom)
  • When it started or when it occurs
  • Where — in which process, product, or team
  • How often — one-time, recurring, constant
  • What is the impact — on customers, revenue, team

Good examples:

  • "Since March, customer support response time has increased from 2h to 8h."
  • "In the last quarter, 15% of orders are shipped with a delay exceeding 48h."
  • "Bounce rate on the pricing page jumped to 78% after the latest redesign."

Avoid: "We have a quality problem" (too vague), "John doesn't do his job" (blame), "We need to hire more people" (solution).

Quick feedback

What’s on your mind?

Pick one — takes under 30 seconds. Your message goes straight to the operator’s inbox.

🍪 Why cookies?

Why #1: Because they help us see how people use this tool.

Why #2: So we can make it better for you.

Why #3: And keep it completely free — ads help cover the costs.

No creepy tracking. Just analytics & ads. Learn more