Chapter 11: Step 3 — Root Cause Analysis (The Make-or-Break Step)

You've contained the problem and assigned a priority. Now comes the work that separates mediocre quality systems from good ones: understanding *why* the nonconformance occurred, and equally important, why you didn't catch it.

The Four Methods

We'll cover five specific root cause analysis methods in detail in Chapter 4. For now, understand that you must use *a method*—not guessing. The most common are:

• 5-Why: Asking "why" five times in succession to peel back layers of causation. Simple, fast, works for obvious problems.
• Fishbone (Ishikawa): Visual cause-and-effect diagram organizing potential causes into categories: People, Process, Materials, Equipment, Environment, Measurement.
• Fault Tree Analysis: Boolean logic diagram tracing a problem backward through component failures and system interactions.
• Is/Is Not: Comparing what happened against what should have happened, using data to narrow possibilities.

Don't overthink this. A 5-Why analysis on a whiteboard takes 30 minutes and solves most problems. A full Fishbone diagram takes a team meeting of 90 minutes. Use the method that matches your nonconformance complexity.

The Critical Concept: The Escape Point

Here's what auditors look for: not just why the defect happened, but why your system didn't catch it.

In ISO 9001 terms, this is verification and validation failure. In IATF 16949 (if you supply automotive OEMs), it's mandatory. In medical device supply under ISO 13485, it's regulatory.

Let's say you find that a dimension drifted out of spec due to tool wear. The root cause is "tool replacement interval set too long." But the escape point is "100% final inspection was not in place for this dimension on the 2026-01-14 run—operator was training new staff and checking only sample."

Your corrective action must address both:

1. Restore proper tool change interval
2. Reinstate 100% inspection until tool stability is verified

If you only fix the tool interval and don't address why inspection failed, you haven't solved the problem. The next nonconformance will escape your process the same way.