Use this page after a problem has been clearly defined.
Ask why repeatedly until you reach a likely root cause.
DO NOT use this page before defining the problem.
Use Gap Analysis first.
Dashboard
Investigation Mode — Select One
Mode A — Standalone
Start directly from a problem statement. Use when you have a visible problem and want to find the root cause by asking Why five times.
Mode B — Fishbone Follow-Up
Start from a cause already identified in a Fishbone Analysis. Use when you know the likely cause category and want to dig deeper.
Fishbone & 5 Whys — Tool Doctrine
🐟 Fishbone Engine (separate tool)
Wide Investigation
"What could be causing this?"
Explores many possible causes across multiple categories. Use when the source of the problem is not yet known and broad mapping is needed.
🔎 5 Whys Engine — This Tool
Deep Investigation
"Why is this specific cause happening?"
Drills into one specific cause by asking Why five times. Use when you have a cause to investigate in depth and need to find the systemic root.
Mode A — Standalone
Use when no Fishbone analysis exists
Problem Statement
↓
Why 1
↓
Why 2
↓
Why 3
↓
Why 4
↓
Why 5
↓
Likely Root Cause
Mode B — Fishbone Follow-Up
Use after a Fishbone analysis identifies a cause to investigate
Problem Statement
↓
Selected Fishbone Cause
↓
Why 1
↓
Why 2
↓
Why 3
↓
Why 4
↓
Why 5
↓
Likely Root Cause
Fishbone and 5 Whys are complementary tools.
Fishbone helps managers identify possible causes.
5 Whys helps managers investigate one cause in greater depth.
Use Fishbone when many possible causes exist.
Use 5 Whys when you want to drill down into one specific cause.
Fishbone helps managers identify possible causes.
5 Whys helps managers investigate one cause in greater depth.
Use Fishbone when many possible causes exist.
Use 5 Whys when you want to drill down into one specific cause.
Investigation Status
A
Mode
0/5
Whys Answered
—
Root Cause
—
Action Status
How to Use This Engine
1.Select a mode (Standalone or Fishbone Follow-Up).
2.Define the problem in Problem Definition.
3.Ask Why five times in the 5 Whys Investigation. Stop when you reach a process, system, or structural failure.
4.Record the Likely Root Cause in Root Cause Summary.
5.Assign a Corrective Action and Owner in Action Planning.
6.Export or print the investigation from Save & Export.
Problem Definition
Mode A — Standalone Investigation. Enter the visible problem you want to investigate. The 5 Whys will help you find the root cause.
Examples:
5 Whys Investigation
Progress
0 of 5 answered
Stop when you reach a process, system, or structural failure.
Problem Statement
—
▼
Why does this happen?
WHY 1
▼
Why does this happen?
WHY 2
▼
Why does this happen?
WHY 3
▼
Why does this happen?
WHY 4
▼
Why does this happen?
WHY 5
▼
Likely root cause
Likely Root Cause
Root Cause Summary
Problem Statement
—
Likely Root Cause
Not yet defined. Complete the investigation and record the root cause.
Likely Root Cause is a conclusion to be verified, not a proven fact.
A completed 5 Whys does not automatically prove the root cause. Managers should verify findings before implementing corrective actions.
A completed 5 Whys does not automatically prove the root cause. Managers should verify findings before implementing corrective actions.
Action Planning
Root Cause
—
Investigation Notes
Use this space to record observations made during the investigation, what was verified, who was consulted, and any outstanding questions.
Save & Export
A
Mode
0
Whys Answered
—
Root Cause
—
Action Status
Investigation is saved automatically to your browser's local storage.