5why-root-cause

Solid

Drill into root cause with a 5-Why why chain, why analysis, or structured root cause investigation. Builds a Why chain from symptom to systemic root cause, validates each step with evidence, and detects circular reasoning. Use for 8D D4, CAPA, FMEA cause analysis, or any quality investigation requiring confirmed root cause identification.

AI & Automation 28 stars 12 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
49
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 5-Why Root Cause Analysis ## Goal Identify and validate a systemic root cause through a structured, evidence-based Why chain that can be directly linked to a corrective action. ## Required Execution Checklist - [ ] Problem defined with measurable data (value vs. specification) - [ ] Linear Why chain built — one cause path at a time, no branching - [ ] Each Why supported by objective evidence (not opinion or "probably") - [ ] Logical consistency verified — reversal check passed - [ ] Systemic root cause identified (not "human error" or symptom) - [ ] Root cause validated: reproducibility test + elimination test - [ ] Output enables definition of corrective action (PCA or CAPA) --- ## When to use Use 5-Why for any quality problem with a single, linear cause chain. Works best for process failures, equipment failures, and procedural non-compliances. For complex problems with multiple contributing causes, use [Fishbone](../fishbone-analysis/) first to identify candidate root causes, then use 5-Why to drill into each. If multiple potential cause paths exist — do not combine them into one chain. **Run separate 5-Why chains for each path** and determine which is confirmed by evidence. ## Prerequisites - Problem is clearly defined (use [Is/Is-Not](../is-is-not-scoping/) to scope if needed) - The investigation team has access to the process, machine, or system where the defect occurred - Physical evidence or production records are available ## Use within 8D — Occurrence an...

Details

Author
RBraga01
Repository
RBraga01/Quality-Engineering-Skills
Created
3 months ago
Last Updated
2 days ago
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

5-why

Performs 5-Why root-cause analysis (RCA) from the Toyota Production System, tracing a problem through five why-questions in dialog until the actual cause — not the symptom — is found. Use when the user says root cause, RCA, postmortem, incident, retrospective, recurring bug, "why does this keep happening", 5 whys or 5w, or reports a defect or failure that keeps coming back. Also handles the what-for variant for sharpening goals or OKRs. Not for complex social systems with circular causality (team dynamics, feedback loops) — label results as hypotheses there.

1 Updated 2 weeks ago
JasminK11
AI & Automation Listed

five-whys

Run root-cause analysis the Toyota way: ask why five times to reach the system failure behind a product or process incident, then invest a proportional fix at each level. Blocks blame answers and stops teams from fixing symptoms. Use after any incident, outage, missed release, quality regression, or repeated process failure, when writing a postmortem, or when the user says five whys, root cause, why did this happen, postmortem, or blameless analysis. Not for strategic decisions, metric analysis, or interpersonal conflict — those are not causal chains.

2 Updated 6 days ago
karozi
AI & Automation Listed

thinking-five-whys-plus

Enhanced root cause analysis with explicit bias guards and stopping criteria. Use for incident post-mortems, bug investigations, and process failures where standard 5 Whys might mislead.

2 Updated today
babypochi06