# 5 Whys (Root Cause Analysis)

> Source: https://netray.co/glossary/five-whys
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Glossary

## Short answer

The 5 Whys is a root cause analysis technique that asks why a problem happened, then asks why again of each answer, typically about five times, until a cause is reached that can be fixed and prevented from recurring.

## Aliases

- 5 whys
- five whys analysis
- why-why analysis
- 5 why technique

## Category

manufacturing

## Full Definition

The technique was developed at Toyota by Sakichi Toyoda and used by Taiichi Ohno in the Toyota Production System. The number five is a rule of thumb: stop when you reach a cause that is within the organization's control and whose removal prevents recurrence. Sometimes three whys is enough, sometimes more are needed.

A good analysis asks why against facts, not opinions, and checks each answer by going to see. It should reach a system or process cause, not a person. An answer that ends with operator error usually means one more why is needed: why was the error possible, and what in the method, training, tooling or instructions allowed it.

The technique has limits. It follows a single chain, so it can miss multiple contributing causes. For complex problems it is paired with a fishbone diagram, fault tree or FMEA. It is also only as good as the knowledge of the people in the room.

In ERP and QMS practice, the result feeds corrective and preventive action (CAPA). Nonconformance and corrective action records (for example in Infor SyteLine quality modules, SAP QM or NetSuite custom records) hold the problem description, root cause and action. Writing the root cause as a structured field rather than free text makes later trend analysis possible.

## Why It Matters

- Simple, fast and needs no special software or statistics.
- Moves teams from symptoms to fixes that prevent recurrence.
- Provides a documented root cause that auditors expect in corrective actions.
- Structured results enable trending across nonconformances.

## In Practice

A machine stops. Why? A fuse blew. Why? The spindle bearing overloaded. Why? Lubrication was insufficient. Why? The lube pump was not delivering. Why? The pump shaft was worn because the intake had no strainer and debris got in. The fix is adding a strainer and a preventive maintenance task, not just replacing the fuse.

## Faq

### Do you always need exactly five whys?

**Answer:** No. Five is a guideline. Stop when you reach a fixable root cause that prevents recurrence.

### What are the limits of the 5 Whys?

**Answer:** It follows one causal chain, depends on team knowledge and can stop too early. Complex problems need tools such as fishbone diagrams or FMEA alongside it.

### How does it connect to CAPA?

**Answer:** The root cause found feeds the corrective action record, and the preventive action addresses the systemic cause.

### Is operator error a valid root cause?

**Answer:** Rarely. Ask why the error was possible, then fix the method, training, tooling or design that allowed it.

## Search terms

what is 5 whys, 5 whys technique, 5 whys root cause analysis, five whys example, 5 whys template, root cause analysis manufacturing, 5 whys vs fishbone

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json