Most fishbone diagrams produce a wall of brainstorm output and no actionable finding. The problem isn't the tool — it's how teams use it. The fishbone is a structured hypothesis framework, not a whiteboard free-for-all.
The Ishikawa diagram — named after Kaoru Ishikawa, who developed it at Kawasaki in the 1960s — is a cause-and-effect analysis tool. It structures potential causes of a problem into categories, with the goal of generating a complete picture before narrowing to the most likely root cause.
The key word is "before." The fishbone is not meant to identify the root cause on its own. It is meant to surface every plausible category of cause so that the team does not miss something obvious by focusing too early. The 5 Why analysis then drills into the most credible branch.
For manufacturing environments, the standard framework is 6M. Each category prompts a different line of investigation:
Start with a precisely defined problem statement. "High defect rate" is not a problem statement. "Weld joint rejection rate at Station 4 is 3.2% against a target of 0.5%, occurring on the day shift between 10:00 and 14:00 since March 11" is a problem statement. The more specific the effect, the more specific the causes will be.
Fill every category before evaluating any. The discipline of the tool is in completing the full picture before narrowing. Teams that short-circuit to their favourite explanation skip the category that contains the actual cause. Go around the full 6M before anyone argues for a specific branch.
Use evidence to score each branch. After brainstorming, ask for each potential cause: do we have data that supports or contradicts this? A cause with supporting evidence gets prioritised. A cause that is plausible but unverified gets flagged for investigation. A cause contradicted by existing data gets removed.
Transition to 5 Why on the highest-priority branch. The fishbone finds the most credible direction. The 5 Why goes to the bottom of it. They are sequential tools — the fishbone is not complete until it feeds a deeper analysis.
Problem: Dimension out of tolerance on machined bore — 4.2% rejection rate, target 0.5%.
After evidence review: the gauge calibration lapse and the warm-up procedure discrepancy both had supporting data. The team ran a 5 Why on each. The warm-up discrepancy traced to a standard work update in January that was not propagated to the SOP — a change management failure, not an operator failure. That's the root cause.
VeSiMy's Fishbone tool supports 6M Manufacturing, 8P Service, 4S, and Custom frameworks. Causes are added by category, and the AI can generate initial cause suggestions based on the problem statement and your process context. When the analysis is complete, it feeds directly into the 5 Why tool on the same step — the problem statement carries over and the team doesn't re-enter context. The combined analysis exports as an ISO 9001:2015 §10.2.1 compliant root cause report.
Connected to 5 Why and your VSM. AI-assisted cause generation. ISO export when you need it.
Start free →