5 Whys Root Cause Analysis
Work a problem down through up to five "why" questions, record the root cause and action items, then download it as a text file or PNG summary.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the 5 Whys tool?
This tool walks you through the 5 Whys technique in order. You write a problem statement, then add up to five "why" steps, each answering why the previous answer happened. Below that you record the root cause you landed on and a list of action items.
Once anything is filled in, an Analysis Summary appears with the number of whys and actions and the root cause highlighted. Download as Text gives you a plain-text report with every step; Download as Image renders the summary card to a PNG. Export JSON and Import JSON move the whole analysis between machines.
The analysis is saved in this browser as you type, so a reload or a closed tab brings it back on the same device. Clear All removes the saved copy. Export the JSON to move it to another device, or download the text report for a ticket. All processing happens in your browser.
- Guided problem statement, up to five why steps, root cause and actions
- Download as a plain-text report or a PNG summary image
- Export and import as JSON
- Sample analysis to start from
- Runs in your browser with no account
Updated
How to use the 5 Whys tool
- Give the analysis a title and write the Problem Statement as an observable fact with a time and a number, for example "14 of 120 orders missed the 3 pm dispatch cutoff on 2 October".
- Click Add Why and answer "Why did this happen?". Click Add Why again for each further step; each new box asks why the previous answer happened. The button stops at five.
- Write the Root Cause Identified once the last answer points to something you can change.
- Type each fix into Action Items and press Enter or the plus button.
- Use Download as Text for a report, Download as Image for a PNG of the summary, or Export JSON to keep an editable copy.
Worked example
Missed same-day dispatch at a warehouse
Input
Problem: 14 of 120 orders missed the 3 pm cutoff on 2 Oct Why 1: Picking finished at 3:40 pm Why 2: Pickers waited 35 min for the wave release Why 3: Wave release is manual and the supervisor was in a meeting Why 4: No one else has permission to release waves Root cause: Wave release depends on a single role with no backup Action: Grant release rights to two shift leads; add a 1:30 pm auto-release
Output
Summary: 4 Whys Completed, 1 Action Items Text file: root-cause-analysis-missed-dispatch-cutoff.txt (title "Missed dispatch cutoff")
The chain stops at a permission setting that can be changed this week, not at "the supervisor was busy". Four whys were enough here. The text file name is built from the title with non-alphanumeric characters turned into hyphens.
Background and insight
The method comes from Toyota. Sakichi Toyoda, the company's founder, is credited with the practice, and Taiichi Ohno made it part of the Toyota Production System. Ohno's own example is a machine that stopped: the fuse blew because of an overload, the overload came from a poorly lubricated bearing, the bearing was dry because the oil pump was not pumping enough, the pump was worn, and it was worn because there was no strainer to keep out metal scrap. Replacing the fuse fixes the symptom; fitting a strainer fixes the cause.
Five is a rule of thumb, not a requirement. Some chains reach a fixable cause in three steps and some need six; the tool caps the list at five because past that point the answers usually drift into "the company culture", which nobody can act on by Monday.
The technique has known weak spots. It follows one causal chain, so problems with several contributing causes (most outages and quality escapes) need several chains or a fishbone diagram. Answers are only as good as the evidence behind them, and a chain that ends at "someone made a mistake" has stopped too early: the useful question is why the process let that mistake through.
Common use cases
Incident post-mortems
Engineering and operations teams trace an outage or a failed release back to a process gap rather than a person.
Customer complaints
Support leads work out why the same complaint keeps arriving instead of answering each ticket separately.
Quality escapes
Manufacturing and QA teams find why a defect reached the customer and which control should have caught it.
Project slippage
Delivery managers find the real reason a milestone moved before the next plan repeats it.
Tips and limitations
- Answer each why with evidence (a log, a timestamp, a document), not a guess. If you are guessing, go and look before writing the next step.
- Stop when the answer is something you can change and the fix would prevent recurrence. Going further usually lands on causes outside your control.
- If one why has two honest answers, run two chains (export, clear, start again) or move to a fishbone diagram.
- Never end on a person. "Alex forgot" becomes "the checklist did not include the step" or "the tool allowed the release without the check".
- Work is kept in this browser only. Export JSON before switching computers or clearing site data.
Sources and further reading
- Toyota Production System: Beyond Large-Scale Production, Productivity Press. Taiichi Ohno's book, with the stopped-machine example of asking why five times
- 5 Whys: Finding the Root Cause, Institute for Healthcare Improvement. A worksheet and guidance for running the 5 Whys in a team
- Cause and Effect Diagram, Institute for Healthcare Improvement. The fishbone diagram to use when a problem has several contributing causes
Frequently asked questions
Who invented the 5 Whys technique?
It comes from Toyota. Sakichi Toyoda is credited with the practice, and Taiichi Ohno built it into the Toyota Production System and described it in his book on the system, using the example of a machine stopped by a blown fuse that traced back to a missing oil strainer.
Do you always have to ask why exactly five times?
No. Five is a guideline. Stop when you reach a cause that you can change and that would prevent the problem from recurring; that might take three steps or six. This tool allows up to five because chains longer than that usually drift into causes nobody can act on.
What is the difference between 5 Whys and a fishbone diagram?
The 5 Whys follows a single cause-and-effect chain downward. A fishbone (Ishikawa) diagram spreads out sideways, listing possible causes by category such as people, process, equipment and materials. Use 5 Whys for problems with one dominant cause and a fishbone when several factors contribute.
Does the 5 Whys tool save my analysis?
Yes, in this browser. Each change is saved to local storage under the key root-cause-analysis, so reloading the page keeps your whys and actions. It is not synced, so use Export JSON for an editable copy on another device, or Download as Text for a report you can attach to a ticket or post-mortem.
Why should a 5 Whys analysis not end with human error?
Because retraining or blaming one person rarely stops the problem coming back. If someone made a mistake, ask why the process allowed it: a missing check, an unclear instruction, a tool that accepted bad input. That answer gives you a fix that works whoever is on shift.
What goes in the Download as Image file?
The image is a PNG of the Analysis Summary card: the count of whys and actions and the root cause, with a small RedBison footer. The individual why steps are only in the text download and the JSON export.
Is there an in-depth guide to the 5 Whys tool?
Yes. “The 5 Whys: Finding Root Causes Without Blaming People” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.