Last reviewed: June 19, 2026
The 5-Why is the most widely used root cause tool in manufacturing and the most widely misused. When it works, a 5-Why takes 15 to 20 minutes, involves the operator and supervisor who were present, and produces a countermeasure that changes a system rather than a behavior. When it fails, it stops at operator error and produces a retraining that will not hold past the next shift change.
Key takeaways:
Run the 5-Why on the largest single scrap event in the top Pareto category, not on the category average. Averages smooth out the signal.
Run it in front of the machine with the operator and supervisor who saw the problem, within one week of the event.
Stopping at "operator error" is a failed 5-Why, not a completed one. The operator made a choice inside a system that allowed that choice.
A countermeasure that changes a setup sheet, inspection form, or maintenance schedule will sustain. A countermeasure that requires verbal reminders will not.
WHAT 5-WHY ANALYSIS IS AND WHEN TO USE IT
A 5-Why is a structured root cause analysis technique. It starts with a specific defect or failure event, asks why it happened, then asks why that cause occurred, and repeats until the chain reaches a systemic root cause that can be corrected by changing a process, a procedure, or a physical condition. The name comes from the observation that five iterations is usually enough to reach the underlying system failure, though the right answer for a specific problem might be three or seven.
The 5-Why is the right tool for a discrete, specific failure event where the cause is unknown. Use it when a defect is significant enough to investigate, the event is recent enough that details are still recoverable, and the failure has occurred before or is likely to occur again. It is not designed for tracking trends or for problems where statistical process control is more appropriate.
Run the 5-Why on the largest single scrap event in a category, not on the category average. Averages hide the signal. If your scrap Pareto shows burrs on stamped parts as the top defect category, the 5-Why runs on the single largest burr event in the last 30 days, not on a summary of all burr events over three months. Specific events produce specific and actionable causes. Summaries produce generic ones.
A FULLY WORKED 5-WHY EXAMPLE: THE BURR DEFECT
Event: A batch of 40 flanged brackets (Part 7432-A) was rejected at final inspection for burrs on the inner edge of the formed hole. All 40 parts were scrapped. Total scrap cost: $1,760 at standard cost. Die 318, first production run after a scheduled die change.
| STEP | QUESTION | ANSWER |
|---|---|---|
| Why 1 | Why were the parts rejected? | The inner hole edge had burrs that exceeded the dimensional tolerance in the drawing. |
| Why 2 | Why did the forming operation produce burrs on this run? | The punch on Die 318 was worn below the minimum acceptable diameter, producing a ragged cut edge. |
| Why 3 | Why was a worn punch put into production? | The pre-die-change inspection checklist does not include punch diameter verification. Only punch length and die section condition are checked. |
| Why 4 | Why does the inspection checklist not include punch diameter? | The checklist was written at initial die setup four years ago. Punch wear has not been added as an inspection parameter since that time. |
| Why 5 | Why has the checklist not been updated to reflect punch wear as a known failure mode? | There is no formal process for routing scrap investigation findings back to die setup documentation. Tooling notes from defect events are not reviewed by the tooling manager or used to update inspection forms. |
| Root cause | Scrap investigation findings are not systematically routed to die setup documentation, so inspection checklists do not reflect wear patterns learned from production history. | |
| Countermeasure | Add punch diameter verification to the pre-die-change inspection form for Die 318 and all similar progressive dies. Update the tooling review procedure to require that any scrap investigation finding related to die condition be reviewed by the tooling manager and incorporated into the relevant inspection form within 30 days. | |
| Owner | Tooling Manager | |
| Due date | Inspection form: 7 days. Tooling review procedure: 30 days. |
Notice that the countermeasure does not say "remind operators to check punches before production." It changes a document that governs what every operator checks before any die of this type runs. The next shift and the next operator execute the same check automatically because it is now in the procedure, not in a conversation.
THE MISTAKE THAT RUINS MOST 5-WHY ANALYSES
The most common failure in a 5-Why is stopping at "operator error." A completed chain looks like this: the part was defective because the operator set up the die with a worn punch. Why? Because the operator did not check punch diameter. Why? Because the inspection checklist did not require it. The chain did not stop at "the operator did not check." It continued to the missing requirement in the checklist.
Stopping at operator error produces a countermeasure that is a training record, a memo, or a verbal reminder at the shift meeting. None of these change what happens on the next shift. The operator involved in the original event may now remember to check. The next operator who runs the same die does not, and the system provides no check.
An operator always makes a choice inside a system. The system sets up the conditions for that choice: the instructions available, the tools at hand, the inspection steps required, the time pressure on the setup. A 5-Why is not complete until it reaches the system condition that allowed the choice to be made.
Ask at every step: could a different, equally experienced operator have made the same error under the same conditions? If yes, the root cause is the system, not the person.
WHEN TO USE 5-WHY VS A FISHBONE DIAGRAM
A 5-Why and a fishbone (Ishikawa) diagram both identify root causes but they are suited to different problems.
Use the 5-Why when the defect is specific and discrete, the cause is likely traceable to one chain of events, and you need a rapid analysis that can be executed on the floor within a day or two of the event. The 5-Why is the right tool for the press shop on a Tuesday morning.
Use the fishbone diagram when the defect has multiple potential cause categories that need to be mapped before any investigation path is chosen, when a team needs to build a shared view of the problem before drilling down, or when the 5-Why has failed to find the root cause across two or three attempts and the problem appears to be multi-causal. The fishbone is a brainstorming structure; the 5-Why is a drilling structure.
In most plants we have worked with, the 5-Why is used more frequently because the problems worth structured investigation are usually specific events with a traceable chain. The fishbone gets used when the 5-Why has stalled and the team suspects more than one root cause is at work.
A BLANK TEMPLATE YOU CAN USE TODAY
Use this template for any defect investigation. Complete the event description before starting. Run it in front of the machine or workstation where the event occurred, with the operator and supervisor who were present.
Event description: [Part number, quantity, defect description, cost at standard, where in the process the failure was found, date of event]
| WHY | QUESTION | ANSWER |
|---|---|---|
| Why 1 | Why did [the defect] occur? | |
| Why 2 | Why did [answer from Why 1] occur? | |
| Why 3 | Why did [answer from Why 2] occur? | |
| Why 4 | Why did [answer from Why 3] occur? | |
| Why 5 | Why did [answer from Why 4] occur? | |
| Root cause | What systemic condition allowed this failure? | |
| Countermeasure | What process, procedure, or physical change will prevent recurrence? | |
| Owner | ||
| Due date | ||
| Verified closed | 30-day first-pass yield data at or above target; countermeasure documented in standard work |
For a step-by-step guide to identifying which defect categories to investigate and how to prioritize them, the manufacturing scrap reduction guide covers the full Pareto-first sequence from data collection through countermeasure verification.