Five whys

An example of a problem is: bolts are cross-threading in the engine block on the production line. • Why? – The threads aren't cut cleanly. • Why? – The cutting tool on the lathe wasn't changed today. • Why? – The replacement cutting tool bin was empty. • Why? – The bin's contents had fallen and rolled under the shelves. • 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. 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. In this case, the factory may need to add a process for regularly inspecting shelving units for instability, and fixing them when broken. == History ==

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? () • Because he lacks faith. () • Why does he lack it? () • Because he lacked the will to be attentive. () • Why does he lack this? () • Because he did not understand the necessity of the matter, the usefulness of being attentive. () • Why did he not understand? () • Because the causes of understanding were lacking. () 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 the nature of the problem as well as its solution becomes clear." == Techniques ==

Two primary techniques are used to perform a five whys analysis: the fishbone (or Ishikawa) diagram and a tabular format. These tools allow for analysis to be branched in order to provide multiple root causes. == Criticism ==

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. 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: • The arbitrary 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. ==See also==