5 Whys and the fishbone: finding the root cause without blame
In brief
Root-cause analysis questions the system, not the person. The “why?” must end at a method, not at a human being. The two tools, the common mistakes and the rules of blame-free analysis.
20 October 2026 · 4 min read
Sample company · demo dataRoot-cause study
The Lean Enterprise Institute lexicon defines 5 Whys as asking “why?” repeatedly to reach a problem's root cause and tells Taiichi Ohno's machine example: the machine stopped because the fuse blew; because the bearing was not lubricated enough; because the oil pump was not pumping enough; because the pump shaft was worn; because there was no strainer and metal chips got in. At the end of the chain there is no person, only a missing strainer.
If the chain ends at a person, you stopped in the wrong place
The most common mistake in root-cause analysis is cutting the chain at “the operator was not careful”. The accident investigation page of the UK Health and Safety Executive (HSE) also says the key is finding the underlying, latent root causes. “Not careful” is a symptom, not a cause; the next question should be “why did they have to be careful?” The answer usually leads to a design, a standard or a training gap.
Human error is an outcome; the condition that made the error possible is the cause.
The question is “what?” and “why?”, never “who?”.
The analysis is done with the person who experienced the problem; with them, not about them.
Five is a reminder: stop when the answer reaches a system gap, sometimes at three, sometimes at seven.
The fishbone: not locking onto one cause too early
5 Whys moves along a single line; the fishbone (Ishikawa diagram) opens possible causes in groups: people, machine, method, material, measurement, environment. The team writes possible causes under each group; the most likely one is chosen and taken deeper with 5 Whys. The two tools are not rivals but a sequence. Even the “people” bone is not for blame: the causes there describe conditions such as training, fatigue or shift load.
Sample company · demo dataFishbone diagram
No root cause without verification
A cause found is a hypothesis. The Lean Enterprise Institute's definition of problem solving rests on verifiable facts: if the problem does not recur once the cause is removed, it was the root cause. That is why an analysis is followed by a countermeasure, a monitoring period and finally an effectiveness check. Without the check, the analysis is just a presentation.
Who should be in the analysis?
Root-cause analysis is not office work. The operator who experienced the problem, maintenance, quality and, if needed, the supplier should sit at the same table. Without the operator, the answers to “why?” are guesses; with the operator present but afraid to speak, the answers are incomplete. The manager's job, before the first “why?”, is to say this: nobody will be blamed in this meeting, the system will be discussed. If that sentence is not said, the meeting turns into defence within ten minutes.
Common mistakes
Ending the chain at a person: “carelessness”, “inexperience”, “rushed it”.
Treating five questions as the goal: if the answer reached the system at the third question, stop there.
Filling in the fishbone and leaving it: the fishbone is a list of candidates, not a conclusion.
Not verifying the countermeasure: not checking whether the problem recurred after the measure was taken.
Doing the analysis at a desk: a “why” written without going to the place is usually wrong.
How it is done in Gemy
Root-cause work is done inside a CAPA, complaint, OHS incident or Kaizen record; the ready-made CAPA template asks together how the root cause was sought (5 Whys, fishbone), the planned activity, how effectiveness is measured and the monitoring period.
The ready-made CAPA flow has evaluation, activity, verification, a monitoring period (30 days if left blank) and an effectiveness check; durations and steps belong to the company.
In Kobetsu projects, if the 6M fishbone board feature is on, a root-cause board sits on the project page; a countermeasure action is opened from the verified cause with one button.
If the company has switched AI on, a 5 Whys and fishbone draft can be requested on the record screen; it stays a draft until accepted and the decision rests with a person.
An accepted analysis goes into the record report: the root cause and at most five “why?” answers. Draft analyses are not printed.
The system blames nobody, but the team doing the analysis must not blame either. The tool does not change the attitude; the attitude changes the tool.
In short
5 Whys goes deep along a single line, the fishbone opens possible causes in groups; the two are used in sequence. If the chain ends at a person, the analysis stopped early; the right stop is a missing standard, design or training. The analysis is done with the person who experienced the problem and at the place it happened; a cause counts as the root cause only when the countermeasure is taken and the problem does not recur. The manager's first sentence sets the tone of the meeting: nobody will be blamed, the system will be discussed.
Takt time is the customer's pace; Yamazumi stacks each station's load against that pace. Calculating takt, reading the chart, the balancing sequence and how to explain balancing to the operator.
Autonomous maintenance means the person who knows the machine best, the operator, takes over its daily care. The content of the first three steps, the abnormality tag, the CIL standard and the division of work between operator and maintenance.
Kamishibai checks with short cards, at regular intervals, whether a standard is being followed on the floor. The structure of a card, the layers, good and bad question examples and the path of a red card.
7 November 2026 · 5 min
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.