The 5 Whys is a simple root cause technique in which a team asks why a problem happened, then asks why again for each answer, usually about five times, until it reaches a fixable cause.

The 5 Whys is a problem-solving method that finds the cause of a problem by asking why it happened, then asking why again for each answer. Teams usually need about five rounds to move past the obvious symptom to a cause they can fix, though the exact number varies.
The technique was developed at Toyota and is credited to Sakichi Toyoda, the company's founder. It became a core part of the Toyota Production System and lean manufacturing, and today it is widely used in safety incident investigations, quality problem solving and kaizen events.
Many incident reports stop at the first answer: the worker slipped, the operator forgot, the part broke. Those answers describe what happened but not why, so the same problem returns. The 5 Whys pushes teams past the symptom to a cause in the system that can actually be fixed.
Because it needs no software or specialist training, the 5 Whys can be used by supervisors and crews right after a near miss or minor incident. That makes learning fast and keeps frontline workers involved in finding solutions.
Cleaning the oil fixes today's hazard. Adding the machine to the maintenance system prevents the next leak.
For serious incidents, many organizations use the 5 Whys inside a broader root cause analysis with tools such as fishbone diagrams, causal factor charts or fault tree analysis.
No regulation requires the 5 Whys. OSHA's incident investigation guidance and Process Safety Management rules require employers to identify factors that contributed to incidents, and ISO 45001 requires organizations to determine the causes of incidents and nonconformities. The 5 Whys is one accepted way to do this for simpler events.
A delivery driver strained his back unloading a heavy box. The first answer was that he lifted wrong. The team kept asking why: the box weighed 90 pounds, the hand truck was missing, the hand truck had been broken for two weeks, and there was no process for reporting and replacing broken equipment on trucks.
The company replaced the hand truck, created a defect reporting step in the driver's daily vehicle check and asked suppliers to label boxes over 50 pounds so drivers could plan two-person or assisted lifts.
No. Five is a rule of thumb. Some problems reach a fixable cause in three whys, others need more. Stop when you reach a cause that, if fixed, would prevent the problem from happening again.
It is credited to Sakichi Toyoda, founder of Toyota, and was built into the Toyota Production System.
On its own, usually not. Serious incidents often have many causes, so the 5 Whys is best used alongside other root cause methods.
Stopping at human error, such as the worker was careless. A good analysis asks why the system made the error possible or likely.
The 5 Whys drills down one chain of causes. A fishbone (Ishikawa) diagram maps many possible causes across categories such as people, methods, equipment and environment. They are often used together.
Yes. It is well suited to near misses and minor incidents because it is quick, and it helps teams fix causes before someone gets hurt.
Part of SafetyIQ's EHS glossary: plain-English definitions of workplace health and safety terms.
> Keep learning
> See it in action
Capture hazards, run inspections, track training and close out corrective actions in one platform built for high-risk, field-heavy work.
Book my free demo