Chapter 29: Root Cause Analysis Methods That Work on a Canadian Shop Floor

Root cause analysis sounds academic. On a factory floor, it's practical detective work. The method you use depends on the problem type and the team's analytical skill level.

The 5-Why method is the most accessible and the one most plants use first. You ask "Why?" five times—not to be annoying, but to move from symptom to system.

*Example: Fastener plating batch fails surface finish inspection.*

• Why? The plating temperature was 2°C below spec.
• Why? The operator didn't adjust it back after lunch.
• Why? The temperature display was hard to read from the work position.
• Why? The gauge face was small and positioned behind the tank, and the lighting was poor.
• Why? The control panel was designed 15 years ago before current production volume; the area layout wasn't updated.

That fifth "why" points to a system issue—panel placement and visibility—not operator discipline. Your corrective action becomes: relocate the digital display and improve task lighting, not "retrain the operator."

The 5-Why method works best for single-factor problems—a single defect, a clear timeline, limited variables. It's also fast. You can run a structured 5-Why session in 30 minutes with three people.

Fishbone diagrams (Ishikawa diagrams) work better when the problem is multifactorial. You list the major process categories down the sides of the spine—Materials, Methods, Machines, Manpower, Measurement, Environment—and brainstorm what in each category might have contributed. Then you trace backward to the most likely root causes.

This method surfaces hidden contributors. A stamping defect might be traced to: low material hardness (Materials), incorrect die offset (Methods), worn die punch (Machines), operator fatigue late in shift (Manpower), and miscalibrated thickness gauge (Measurement). The corrective action isn't single-point; it addresses the conjunction of factors that had to align for the defect to occur.

Fault tree analysis is more formal and works for complex processes or safety-critical defects. You start with the defect at the top and ask: "What combinations of failures could cause this?" You map all possible failure paths as branches. This method is most useful when you're investigating complaints from automotive OEMs or medical device customers who expect documentable rigor.

The common trap across all three methods is corrective actions that address symptoms instead of systems. Here's what it sounds like:

• Symptom-level action: "We retrained the operator on the correct plating temperature."
• System-level action: "We replaced the manual gauge with a digital display with visible min/max setpoint indicators and implemented daily temperature log review with alarm thresholds."

  Or:

• Symptom: "Burrs on stamped parts."
• Symptom-level action: "Told the operator to deburr more carefully."
• System-level action: "Analyzed die wear patterns, increased die maintenance frequency from monthly to twice weekly, and installed a post-stamp automated deburring station for critical features."

The second answer in each pair takes more effort. It also prevents the defect instead of relying on fallible human consistency. On a Canadian shop floor where labour turnover is real and operator experience varies, system-level actions are the only ones that stick.