← Portfolio Hub

5 Whys Root Cause Tool

Define the problem, ask why with evidence at each step, test the logic in reverse, then set actions and check they worked. Supports the Analyse phase of the DMAIC project board.

How to use this tool
  • Define the problem with what, where, when and how big. A vague problem gives a vague root cause.
  • Answer each why from evidence, not opinion. Go and look at the process, then tick how you know.
  • Five is a guide. Stop when you reach a cause in the process or system that you can fix. Add or remove whys as needed.
  • Watch for blame. If the answer is a person, ask why the system allowed it.
  • Test in reverse. Read the chain from the root cause back to the problem. If the root cause were fixed, would the problem have been prevented?
  • Close the loop with containment, corrective and preventive actions, and a measure to verify the fix held.
  • If the problem has several causes, use a fishbone first and run one 5 Whys per branch.

1. Problem statement

2. The whys

3. Root cause and logic check

4. Actions

ActionTypeOwnerDueStatus

5. Verify it worked

Completeness check

5 Whys Root Cause Tool · Continuous Improvement toolkit.
Data saves automatically in this browser only. It will not appear on another device or browser. Use Export backup and Import backup to move an analysis between them. The example is based on a real stoppage on Line 8.

Decision support only. It does not replace a competent person's judgement, a formal assessment or your own legal duties, and nothing here is a certification, audit result or proof of compliance. Provided free and as is, without warranty. If you enter names, your employer is responsible for that data. Use initials or roles, and follow your company's data rules.