Skip to content
Let ideas be heard and improvements last.
Gemy

Root cause analysis: when 5 Whys is not enough and when FMEA is needed

In brief

5 Whys follows a single chain of a problem that has already happened; FMEA looks for failures that have not yet happened at the start of a design or process. When to use which, and where the two meet.

7 November 2026 · 5 min read

Sample company · demo dataRoot-cause analysis (5 Whys): questions, answers and the root cause found
Root-cause study

The Lean Enterprise Institute lexicon defines 5 Whys as asking “why?” when a problem appears until you get past the visible symptom to the root cause, and notes that five is a rough guide rather than a rule. IEC 60812 is the international standard that defines failure modes and effects analysis (FMEA) and its criticality variant (FMECA) as a method for planning, performing, documenting and maintaining the analysis for hardware, software, processes involving people and their interfaces. The two tools do not answer the same question: 5 Whys asks “why did this happen?”, FMEA asks “what could happen and how bad would it be?”

When is 5 Whys enough?

  • The problem has happened and its symptom is clear: the machine stopped, the part came out defective, the delivery was late.
  • The causes proceed as a chain: each answer gives rise to the next question.
  • It can be asked with the person who experienced the problem, at the place it happened.
  • The chain ends at a missing standard, design or training, not at a name.

If these four conditions hold, 5 Whys is both fast and sufficient. Most everyday floor problems fall within this scope.

When is 5 Whys not enough?

  • The problem has several independent causes: a single chain picks one cause and hides the others. The possible causes should first be opened in groups with a fishbone, then the causes narrowed by evidence deepened with 5 Whys.
  • The cause advances without evidence: if every “why?” answer is a guess, the chain is not sound. No move to the next question without a measurement, photo or record.
  • The chain stops at a person: “because the operator was not careful” is not a root cause but a stopping point. The question continues: why could carelessness turn into a defect?
  • The problem has not happened yet: 5 Whys looks backwards. With a new machine, a new process or a change there is no past; a forward-looking tool is needed.

When is FMEA needed?

FMEA writes down in advance, for every step of a process or design, what could go wrong, its effect, its cause and the existing control; it scores each line by severity, occurrence and detection and plans countermeasures for high-scoring lines. Its place is clear: when a new product or process is commissioned, when a significant change is made, in processes with a safety impact and wherever the customer or the sector requires it. FMEA is not a one-off document; it is re-scored as countermeasures are taken and updated as the process changes. An FMEA written once and put in a cupboard is just a sheet of paper shown to the auditor.

Where the two meet

The root cause of a problem found with 5 Whys should be recorded as a line in the FMEA: this failure mode occurred, our control did not catch it, its score should rise and a new control should be added. The reverse also holds: when a high-scoring FMEA line occurs, 5 Whys asks why the control did not work. The two tools feed each other; one teaches the past, the other plans the future.

A shared mistake: looking for the culprit

In both tools the biggest trap is ending the analysis at a person. When the 5 Whys chain stops at a name, or “operator error” is written as the cause on an FMEA line, the countermeasure becomes training or a warning and the problem recurs. The right stopping point is a feature of the process: a missing standard, a misleading design, an insufficient control, a gap in the training plan. The system blames nobody; nor should the team doing the analysis.

Sample company · demo dataFMEA study: row counts by priority, study details and the table tab
FMEA study

How it is done in Gemy

  • 5 Whys and fishbone work is done inside the CAPA, 8D, customer complaint and OHS incident records; the ready-made CAPA form asks together how the root cause was sought, the root cause, the planned activity, the effectiveness measure and the monitoring period. Each root cause gets an action with an owner and due date; in the ready CAPA type the person who opened the record checks effectiveness.
  • FMEA is a separate study: severity, occurrence and detection are scored on the line and the RPN formula is shown; lines are edited in the Excel view, countermeasures are tracked as actions and a flow can be set up for FMEA approval.
  • If the 6M fishbone board is on in a Kobetsu project, an action is opened from a verified cause with one button.
  • If the company has switched AI on, a 5 Whys and fishbone draft can be requested in the record; the draft stays a draft until a person accepts it and the decision rests with the person. Gemy does not link 5 Whys and FMEA automatically; updating the FMEA line from a CAPA is the team's job.

In short

5 Whys follows a single chain of a problem that has happened; with many causes a fishbone comes first, and without evidence a measurement comes first. FMEA scores failures that have not yet happened at the start of a design or process and plans countermeasures; it is essential for new processes, significant changes and places with a safety impact. The two tools feed each other: a failure that occurred updates the FMEA line, and when a high-scoring line occurs 5 Whys questions the control. In both, the analysis ends at a feature of the process, not at a person.

Sources

You may copy and share this article with attribution (Gemy, https://www.gemydigital.com/en/blog/kok-neden-analizi-5-neden-ne-zaman-yetmez-fmea-ne-zaman).

Related posts

Cookies

Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.

Cookie policyPrivacy notice