Jump to content

Five whys

From Wikipedia, the free encyclopedia
(Redirected from Five Whys)
Not to be confused with Five Ws.

Five whys (or 5 whys) is an iterative interrogative technique used to explore the cause-and-effect relationships underlying a particular problem.[1] The primary goal of the technique is to determine the root cause of a defect or problem by repeating the question "why?" five times, each time directing the current "why" to the answer of the previous "why". The method asserts that the answer to the fifth "why" asked in this manner should reveal the root cause of the problem.[2]

The technique was described by Taiichi Ohno at Toyota Motor Corporation. Others at Toyota and elsewhere have criticized the five whys technique for being too basic and having an artificially shallow depth as a root cause analysis tool (see § Criticism).

Example

[edit]

An example of a problem is: bolts are cross-threading in the engine block on the production line.

  1. Why? – The threads aren't cut cleanly.
  2. Why? – The cutting tool on the lathe wasn't changed today.
  3. Why? – The replacement cutting tool bin was empty.
  4. Why? – The bin's contents had fallen and rolled under the shelves.
  5. Why? – One of the feet on the shelves has rusted and failed, making the shelves unstable, and when it was jostled, many parts fell on the floor, including the lost cutting tools.

In this example, five iterations of asking why is sufficient to get to a root cause that can be addressed.[3] The key idea of the method is to encourage the troubleshooter to avoid assumptions and logic traps and instead trace the chain of causality in direct increments from the effect through any layers of abstraction to a root cause that still has some connection to the original problem. In this example, the fifth "why" suggests a broken shelf foot, which can be immediately replaced to prevent the reoccurrence of the sequence of events that resulted in cross-threading bolts.

The nature of the answer to the fifth why in the example is also an important aspect of the five why approach, because solving the immediate problem may not solve the problem in the long run; the shelf foot may fail again. The real root cause points toward a process that is not working well or does not exist.[4] In this case, the factory may need to add a process for regularly inspecting shelving units for instability, and fixing them when broken.

History

[edit]

In history, there are early examples of repeated questions to gain knowledge, such as in Plato's Meno. Aristotle developed a different approach with the four causes to develop four fundamental types of answer to the question ‘why?’. Gottfried Wilhelm Leibniz used iterative why questions in his letter to Magnus von Wedderkop in 1671, in which he applied elements of argumentation that he later used to solve the question of theodicy:

  • Consider Pilate, who is damned. Why? (Cur Pilatus damnatus est?)
    • Because he lacks faith. (Quia fidem non habuit.)
  • Why does he lack it? (Cur fidem non habuit?)
    • Because he lacked the will to be attentive. (Quia voluntatem attentandi non habuit.)
  • Why does he lack this? (Cur voluntatem attentandi non habuit?)
    • Because he did not understand the necessity of the matter, the usefulness of being attentive. (Quia utilitatem non intellexit.)
  • Why did he not understand? (Cur non intellexit?)
    • Beause the causes of understanding were lacking. (Quia causae intellegendi defuerunt.)

The modern technique was originally developed by Sakichi Toyoda and was used within the Toyota Motor Corporation during the evolution of its manufacturing methodologies. It is a major component of problem-solving training, delivered as part of the induction into the Toyota Production System. The architect of the Toyota Production System, Taiichi Ohno, described the five whys method as "the basis of Toyota's scientific approach by repeating why five times[5] the nature of the problem as well as its solution becomes clear."[2] The tool has seen use beyond Toyota, and is now used within Kaizen, lean manufacturing, lean construction and Six Sigma. The five whys were initially developed to understand why new product features or manufacturing techniques were needed, and was not developed for root cause analysis.

In other companies, it appears in other forms. Under Ricardo Semler, Semco practices "three whys" and broadens the practice to cover goal setting and decision-making.[6]

Techniques

[edit]

Two primary techniques are used to perform a five whys analysis:[7] the fishbone (or Ishikawa) diagram and a tabular format.

These tools allow for analysis to be branched in order to provide multiple root causes.[8]

Criticism

[edit]

The five whys technique has been criticized as a poor tool for root cause analysis. Teruyuki Minoura, former managing director of global purchasing for Toyota, criticized it as being too basic a tool to analyze root causes at the depth necessary to ensure an issue is fixed.[9] Reasons for this criticism include:

  • Tendency for investigators to stop at symptoms rather than going on to lower-level root causes.
  • Inability to go beyond the investigator's current knowledge – the investigator cannot find causes that they do not already know.
  • Lack of support to help the investigator provide the right answer to "why" questions.
  • Results are not repeatable – different people using five whys come up with different causes for the same problem.
  • Tendency to isolate a single root cause, whereas each question could elicit many different root causes.

Medical professor Alan J. Card also criticized the five whys as a poor root cause analysis tool and suggested that it be abandoned because of the following reasons:[10]

  • The artificial depth of the fifth why is unlikely to correlate with the root cause.
  • The five whys is based on a misguided reuse of a strategy to understand why new features should be added to products, not a root cause analysis.

To avoid these issues, Card suggested instead using other root cause analysis tools such as fishbone or lovebug diagrams.[10]

See also

[edit]

References

[edit]
  1. ^ Olivier D., Serrat (February 2009). The Five Whys Technique. Asian Development Bank. Retrieved September 5, 2019.
  2. ^ a b Ohno, Taiichi (1988). Toyota production system: beyond large-scale production. Portland, OR: Productivity Press. ISBN 0-915299-14-3.
  3. ^ Serrat, Olivier (2017). "The Five Whys Technique". Knowledge Solutions. pp. 307–310. doi:10.1007/978-981-10-0983-9_32. ISBN 978-981-10-0982-2.
  4. ^ Fantin, Ivan (2014). Applied Problem Solving. Method, Applications, Root Causes, Countermeasures, Poka-Yoke and A3. ISBN 978-1499122282.
  5. ^ Ohno, Taiichi (March 2006). ""Ask 'why' five times about every matter."". Archived from the original on Nov 27, 2022. Retrieved September 5, 2019.
  6. ^ Semler, Ricardo (2004). The Seven-Day Weekend. Penguin. ISBN 9781101216200. Ask why. Ask it all the time, ask it any day, and always ask it three times in a row.
  7. ^ Bulsuk, Karn (April 2, 2009). "An Introduction to 5-why". Retrieved September 5, 2019.
  8. ^ Bulsuk, Karn (July 7, 2009). "5-whys Analysis using an Excel Spreadsheet Table". Retrieved September 5, 2019.
  9. ^ "The "Thinking" Production System: TPS as a winning strategy for developing people in the global manufacturing environment" (PDF). Public Affairs Division, Toyota Motor Corporation. October 8, 2003. Archived from the original (PDF) on November 21, 2020. Retrieved September 5, 2019.
  10. ^ a b Card, Alan J. (August 2017). "The problem with '5 whys'". BMJ Quality & Safety. 26 (8): 671–677. doi:10.1136/bmjqs-2016-005849. PMID 27590189. S2CID 42544432.
[edit]
Retrieved from "http://en.wiki.x.io/w/index.php?title=Five_whys&oldid=1257406624"