Five whys

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?". Each answer forms the basis of the next question. The "five" in the name derives from an anecdotal observation on the number of iterations needed to resolve the problem.

Not all problems have a single root cause. If one wishes to uncover multiple root causes, the method must be repeated asking a different sequence of questions each time.

The method provides no hard and fast rules about what lines of questions to explore, or how long to continue the search for additional root causes. Thus, even when the method is closely followed, the outcome still depends upon the knowledge and persistence of the people involved.

Example

An example of a problem is: The vehicle will not start.

  1. Why? – The battery is dead. (First why)
  2. Why? – The alternator is not functioning. (Second why)
  3. Why? – The alternator belt has broken. (Third why)
  4. Why? – The alternator belt was well beyond its useful service life and not replaced. (Fourth why)
  5. Why? – The vehicle was not maintained according to the recommended service schedule. (Fifth why, a root cause)[2]

The questioning for this example could be taken further to a sixth, seventh, or higher level, but five iterations of asking why is generally sufficient to get to a root cause.[3] The key is to encourage the trouble-shooter 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. Note that, in this example, the fifth "why" suggests a broken process or an alterable behavior, which is indicative of reaching the root-cause level.

The last answer points to a process. This is one of the most important aspects in the five why approach – the real root cause should point toward a process that is not working well or does not exist.[4] Untrained facilitators will often observe that answers seem to point towards classical answers such as not enough time, not enough investments, or not enough manpower. These answers may be true, but they are out of our control. Therefore, instead of asking the question why?, ask why did the process fail?

History

The 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 critical 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."[6] The tool has seen widespread use beyond Toyota, and is now used within Kaizen, lean manufacturing and Six Sigma.

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.[7]

Techniques

Two primary techniques are used to perform a five whys analysis:[8]

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

Rules of performing a five whys analysis

In order to carry out a five whys analysis properly, the following advice should be followed:

  1. It is necessary to engage the management in the five whys process in the company. For the analysis itself, consider what is the right working group. Also consider bringing in a facilitator for more difficult topics.
  2. Use paper or whiteboard instead of computers.
  3. Write down the problem and make sure that all people understand it.
  4. Distinguish causes from symptoms.
  5. Pay attention to the logic of cause-and-effect relationship.
  6. Make sure that root causes certainly led to the mistake by reversing the sentences created as a result of the analysis with the use of the expression "and therefore".
  7. Try to make answers more precise.
  8. Look for the cause step by step. Don't jump to conclusions.
  9. Base our statements on facts and knowledge.
  10. Assess the process, not people.
  11. Never leave "human error", "worker's inattention", "blame John", etc. as the root cause.
  12. Foster an atmosphere of trust and sincerity.
  13. Ask the question "Why?" until the root cause is determined, i.e. the cause the elimination of which will prevent the error from occurring again.[10]
  14. When you form the answer to the question "Why?" it should be from the customer's point of view.

Criticism

While the five whys technique can be a powerful tool for engineers or technically savvy individuals to help get to the true causes of problems, it has been criticized by Teruyuki Minoura, former managing director of global purchasing for Toyota, as being too basic a tool to analyze root causes to the depth that is needed to ensure that they are fixed.[11] 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.

These can be significant problems when the method is applied through deduction only. To avoid these issues, it is recommended that the answer to the current "why" question is verified before proceeding to the next question. In addition, performing logical tests for necessity and sufficiency at each level can help avoid the selection of spurious causes and promote the consideration of multiple root causes.[12]

gollark: Excellent, osmarksvoidlinux™ raspberry pi online.
gollark: Sadly it's just `rustup`.
gollark: And give up on web browsing.
gollark: If you care that much, just switch to HellobOiS.
gollark: Hmm. Should I power down the osmarksRPI™ and reset its password for voidical purposes only?

See also

References
  1. Five Whys Technique. adb.org. Asian Development Bank. February 2009. Retrieved September 5, 2019.
  2. Spears, Stephen. The High Velocity Edge. ISBN 978-0071741415. LCCN 2010280780.
  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. "Ask 'why' five times about every matter". Retrieved September 5, 2019.
  6. Ohno, Taiichi (1988). Toyota production system: beyond large-scale production. Portland, OR: Productivity Press. ISBN 0-915299-14-3.
  7. 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.
  8. Bulsuk, Karn. "An Introduction to 5-why". Retrieved September 5, 2019.
  9. Bulsuk, Karn. "5-whys Analysis using an Excel Spreadsheet Table". Retrieved September 5, 2019.
  10. Brożyńska, Martyna; Kowal, Krzysztof; Lis, Anna; Szymczak, Michał (2016). 5xWhys. Method First Handbook. Łódź, Poland: 2K Consulting. p. 34. ISBN 978-83-939309-2-0.
  11. "The "Thinking" Production System: TPS as a winning strategy for developing people in the global manufacturing environment" (PDF). Retrieved September 5, 2019.
  12. Wilson, Bill. "Five-by-Five Whys". Retrieved September 5, 2019.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.