Difference between revisions of "Five whys"

From Pearl Language
Jump to navigation Jump to search
(Sources += The IT Risk Manager » Chris Matts » Ten Ways of “Five Whys”)
(→‎Sources: += InfoQ » Savita Pahuja » Limitations of Five Whys Technique in Agile Retrospective)
 
Line 17: Line 17:
*[http://blogs.hbr.org/cs/2012/09/the_power_of_defining_the_prob.html HBR » The Power of Defining the Problem]
*[http://blogs.hbr.org/cs/2012/09/the_power_of_defining_the_prob.html HBR » The Power of Defining the Problem]
*{{web|url=http://theitriskmanager.wordpress.com/2013/12/30/ten-ways-of-five-whys/|site=The IT Risk Manager|person=Chris Matts|title=Ten Ways of “Five Whys”}}
*{{web|url=http://theitriskmanager.wordpress.com/2013/12/30/ten-ways-of-five-whys/|site=The IT Risk Manager|person=Chris Matts|title=Ten Ways of “Five Whys”}}
*[http://www.infoq.com/news/2015/02/five-why InfoQ » Savita Pahuja » Limitations of Five Whys Technique in Agile Retrospective]
{{Source}}
{{Source}}

Latest revision as of 09:14, 1 March 2015

…any undertaking, entrepreneurial effort, or other collective initiative facing a tough impediment.

✣  ✣  ✣

Get to the root cause and fix it.


Therefore:

Ask “Why” five times and design a few experiments

✣  ✣  ✣

Also, see stretch and squeeze.


✣  ✣  ✣

Sources