01 · 14 articles
5 Whys Analysis
Toyota’s iterative questioning method. Drill from surface symptom to verifiable root cause in five (or however many) steps.
The 5xWhys library
Sixty-six in-depth guides, real-world case studies, and free downloadable templates across seven root-cause methods. Built for anyone who needs to find the real cause of a problem — not the first cause that comes to mind: operations and support leads, project managers, clinicians, consultants, quality engineers, Lean / Six Sigma practitioners and SREs.
Most “blogs” in the quality and reliability space are disconnected posts chasing keywords. This is not that. Every article here belongs to one of seven collections — each built around a single method — so you can read in sequence, compare methods, and move from theory to a working template in three clicks.
The library is maintained by practitioners who have run RCA inside manufacturing cells, software on-call rotations, hospital operating rooms, and regulated supply chains. Every example includes the working numbers: RPN scores, fishbone categories, Pareto percentages, actual corrective actions. Generic examples get cut.
Each collection contains a pillar guide, worked examples, and a free template.
01 · 14 articles
Toyota’s iterative questioning method. Drill from surface symptom to verifiable root cause in five (or however many) steps.
02 · 6 articles
Ishikawa’s cause-and-effect mapping. Map the full causal landscape across 6M, 6P, or custom categories before drilling into one branch.
03 · 6 articles
Failure Mode and Effects Analysis. Proactive risk assessment scoring every failure mode by Severity × Occurrence × Detection (RPN).
04 · 5 articles
The 80/20 rule applied to quality data. Separate the vital few categories from the trivial many before committing improvement effort.
05 · 9 articles
Ford’s Eight Disciplines — the formal corrective-action methodology required across automotive and aerospace supplier quality. Contain, find root cause, fix, prevent.
06 · 5 articles
Toyota’s one-page problem-solving canvas. PDCA in visual form: background, current condition, goal, root cause, countermeasures, plan, and follow-up on a single sheet.
07 · 25 articles
Cross-cutting RCA methodology: how to compare tools, write a problem statement, run PDCA, build a corrective action plan, and choose the right method.
The methods overlap in purpose but differ sharply in timing, scope, and the kind of problem they handle best. Use this as a decision aid before starting an analysis.
| Method | Type | Best for | Output | Typical time |
|---|---|---|---|---|
| 5 Whys | Reactive | Single-incident depth analysis; small team; human-factor or process errors | Linear causal chain to one verifiable root cause | 30–60 min |
| Fishbone | Reactive | Mapping every possible cause category before narrowing down; brainstorming with a cross-functional team | Branching cause map across 6M / 6P categories | 1–2 hours |
| FMEA | Proactive | Pre-launch design or process risk assessment; regulated industries; catching failures before they happen | Ranked RPN worksheet with action plan | 2–20 hours (workshop) |
| Pareto | Data-driven | Prioritization across many defect categories; deciding where to start when everything feels broken | Sorted chart showing the vital few (typically 20%) | 15–45 min |
| Fault Tree | Proactive | Complex systems with multiple contributing causes; safety-critical domains (aerospace, nuclear, medical devices) | Boolean logic tree with probability calculations | 4–40 hours |
| 8D | Workflow | Customer-facing supplier complaints in automotive / aerospace; when formal corrective-action documentation is required | Eight-discipline report (D1–D8) with containment, root cause, and preventive action | 30–60 days |
Most serious investigations use two methods in sequence — typically Fishbone to map the landscape, then 5 Whys on the most likely branch. See the full RCA tools comparison for detailed trade-offs.
The foundational pieces — each one is a long-form, worked-example-heavy guide that stands on its own.