Five Whys - Revision history

Dirkjan at 19:53, 27 August 2020

2020-08-27T19:53:12Z

Dirkjan: Replaced content with "Five Whys Category:mbi Category:Term Category:The Lean Startup"

2020-08-27T19:18:06Z

Replaced content with "Five Whys Category:mbi Category:Term Category:The Lean Startup"

Dirkjan: Created page with "The Five Why technique dives into the heart of a problem by discovering root causes and explore possible fixes by asking 'why' 5 times in a row. Example from Eric Ries: Let'..."

2020-08-25T07:56:59Z

Created page with "The Five Why technique dives into the heart of a problem by discovering root causes and explore possible fixes by asking 'why' 5 times in a row. Example from Eric Ries: Let'..."

New page

The Five Why technique dives into the heart of a problem by discovering root causes and explore possible fixes by asking 'why' 5 times in a row.

Example from Eric Ries:

Let's say you notice that your website is down. Obviously, your first priority is to get it back up. But as soon as the crisis is past, you have the discipline to have a post-mortem in which you start asking why:
* why was the website down? The CPU utilization on all our front-end servers went to 100%
* why did the CPU usage spike? A new bit of code contained an infinite loop!
* why did that code get written? So-and-so made a mistake
* why did his mistake get checked in? He didn't write a unit test for the feature
* why didn't he write a unit test? He's a new employee, and he was not properly trained in TDD

See: http://www.startuplessonslearned.com/2009/07/how-to-conduct-five-whys-root-cause.html

[[Category:mbi]]

[[Category:Term]]

[[Category:The Lean Startup]]

← Older revision		Revision as of 19:18, 27 August 2020
Line 1:		Line 1:
−	~~The~~ Five ~~Why technique dives into the heart of a problem by discovering root causes and explore possible fixes by asking 'why' 5 times in a row.~~	+	Five Whys
−
−	~~Example from Eric Ries:~~
−
−	Let's say you notice that your website is down. Obviously, your first priority is to get it back up. But as soon as the crisis is past, you have the discipline to have a post-mortem in which you start asking why:
−	* why was the website down? The CPU utilization on all our front-end servers went to 100%
−	* why did the CPU usage spike? A new bit of code contained an infinite loop!
−	* why did that code get written? So-and-so made a mistake
−	* why did his mistake get checked in? He didn't write a unit test for the feature
−	* why didn't he write a unit test? He's a new employee, and he was not properly trained in TDD
−
−	~~See: http://www.startuplessonslearned.com/2009/07/how-to-conduct-five-whys-root-cause.html~~
−
	[[Category:mbi]]		[[Category:mbi]]

← Older revision		Revision as of 19:53, 27 August 2020
Line 1:		Line 1:
−	Five ~~Whys~~	+	The Five Why technique dives into the heart of a problem by discovering root causes and explore possible fixes by asking 'why' 5 times in a row.
		+
		+	Example from Eric Ries:
		+
		+	Let's say you notice that your website is down. Obviously, your first priority is to get it back up. But as soon as the crisis is past, you have the discipline to have a post-mortem in which you start asking why:
		+	* why was the website down? The CPU utilization on all our front-end servers went to 100%
		+	* why did the CPU usage spike? A new bit of code contained an infinite loop!
		+	* why did that code get written? So-and-so made a mistake
		+	* why did his mistake get checked in? He didn't write a unit test for the feature
		+	* why didn't he write a unit test? He's a new employee, and he was not properly trained in TDD
		+
		+	See: http://www.startuplessonslearned.com/2009/07/how-to-conduct-five-whys-root-cause.html
		+
	[[Category:mbi]]		[[Category:mbi]]