SOFTWARE-TESTING-QA5 MIN READ
Use Five Whys Without Blaming The Tester
Facilitate a Five Whys analysis that identifies system causes and concrete prevention actions.
Rina R Engineering lead 1 Defuse blame 2 Find system cause 3 Choose countermeasure Post-incident 20 sec Expired coupon escaped The room wants a simple owner for a messy defect. If the retro stops at blame, the next similar defect remains likely. Framework 90 sec Five Whys Ask why until the process condition is visible.
Read the full lesson
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in