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.

karozi Updated 2 repo stars

File contents

karozi/awesome-product-management-skills commit 59f4a112d4

Frequently asked questions

npx get-skill add karozi/five-whys