Fishbone Diagram — Cause and Effect Analysis

The fishbone diagram (also called the Ishikawa diagram or cause-and-effect diagram) is a visual brainstorming tool for identifying all possible causes of a problem. The "head" of the fish is the effect (problem); the "bones" are categories of causes, typically the 6Ms: Man, Machine, Material, Method, Measurement, Mother Nature (Environment).

One-page infographic

Visual summary of Fishbone Diagram — Cause and Effect Analysis · Free PDF

Download PDF

Why companies use it

·Organises brainstorming to ensure no cause category is overlooked
·Creates a visual record of the team's hypothesis space, which can be shared and updated
·Required in many 8D and CAPA templates as the root cause analysis tool
·Helps cross-functional teams see that their area might contribute to a quality problem, breaking defensive thinking

What hiring managers look for

·Fishbone is one of the most commonly used quality tools — engineers should know it instinctively
·They want to see candidates use it as a starting point for investigation, not as a substitute for data
·The ability to facilitate a fishbone session with a cross-functional team is a practical leadership skill
·Following up fishbone causes with 5 Whys to dig to root cause shows proper use of the tool

Typical interview questions

What are the 6M categories in a fishbone diagram?

How do you use a fishbone diagram in conjunction with 5 Whys?

What is the risk of stopping at the fishbone step without further investigation?

Describe a problem-solving situation where you used a fishbone diagram. What did the team identify?

How do you prioritise which branches of the fishbone to investigate first?

Common mistakes

·Treating the fishbone as the answer rather than the question — causes listed on the diagram are hypotheses, not confirmed root causes
·Running the fishbone session without data — causes should be informed by measurement and observation, not just opinions
·Listing too-high-level causes ("machine problem", "operator error") that give no actionable direction for investigation
·Not weighting or prioritising causes after the brainstorm — every potential cause has to be verified, so start with the most likely
·Confusing fishbone (structured brainstorm of potential causes) with 5 Whys (drilling down to the root cause of a confirmed cause)

Real engineering example

During a quality investigation into elevated particle counts in a semiconductor cleanroom, a fishbone session identified 14 potential causes across the 6M categories. Rather than investigating all 14, the team plotted particle count against time and correlated it with shift changeovers — pointing to Man and Method. The 5 Whys from that branch identified that operators were not following the gowning protocol correctly after breaks, introducing particles. A gowning refresher and compliance audit resolved the issue.

Topics covered

fishboneIshikawacause and effectroot cause6Mqualitybrainstorm

Related interview guides

Manufacturing Engineer →Continuous Improvement Engineer →