nw-five-whys-methodology

Featured

Toyota 5 Whys methodology with multi-causal branching, evidence requirements, and validation techniques

AI & Automation 636 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

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

Skill Content

# Five Whys Methodology ## Philosophical Foundation Taiichi Ohno: "By repeating why five times, the nature of the problem as well as its solution becomes clear." Core tenets: scientific evidence-based investigation | address fundamental causes not symptoms | solve to prevent recurrence | use findings for Kaizen ## Multi-Causal Investigation Complex problems have multiple root causes. Investigate comprehensively: - **Parallel**: investigate all symptoms/conditions simultaneously - **Branch**: follow each cause through all five WHY levels - **Cross-cause**: ensure multiple causes don't contradict - **Comprehensive**: address all root causes, not just primary ## WHY Level Definitions ### WHY 1: Symptom Investigation What is immediately observable? Investigate all symptoms. Each branch continues independently. Document verifiable evidence per symptom. ``` WHY 1A: Path not found [Evidence: file exists but wrong context -- Windows vs WSL paths] WHY 1B: Permission denied [Evidence: user context mismatch between host and container] WHY 1C: Timing issues [Evidence: race conditions with file system operations] ``` ### WHY 2: Context Analysis Why does this condition exist? Follow each WHY 1 through context. Check if factors connect multiple causes. Examine system/environment/operational context. ### WHY 3: System Analysis Why do conditions persist? How system enables multiple failure modes. How causes interact systemically. Analyze design/architecture decisions. ### WHY 4: De...

Details

Author
nWave-ai
Repository
nWave-ai/nWave
Created
9 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

five-whys

Use for the 5 Whys, or when the user wants the root cause of a failure: "why did this happen?", "this keeps breaking", "write the postmortem", "find the real cause". Asks why repeatedly with evidence at each step, then sets countermeasures. Skip for one-off typos or when the cause is already proven.

25 Updated today
ysskrishna
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 2 months ago
karozi
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 months ago
JasminK11