To break down (in successive layers of detail) root causes that potentially contribute to a particular effect
Ishikawa diagrams (also called fishbone diagrams,[1]herringbone diagrams, cause-and-effect diagrams) are causal diagrams created by Kaoru Ishikawa that show the potential causes of a specific event.[2]
Common uses of the Ishikawa diagram are product design and quality defect prevention to identify potential factors causing an overall effect. Each cause or reason for imperfection is a source of variation. Causes are usually grouped into major categories to identify and classify these sources of variation.
Sample Ishikawa diagram shows the causes contributing to problem.
The defect, or the problem to be solved,[1] is shown as the fish's head, facing to the right, with the causes extending to the left as fishbones; the ribs branch off the backbone for major causes, with sub-branches for root-causes, to as many levels as required.[3]
Ishikawa diagrams were popularized in the 1960s by Kaoru Ishikawa,[4] who pioneered quality management processes in the Kawasaki shipyards, and in the process became one of the founding fathers of modern management.
The basic concept was first used in the 1920s, and is considered one of the seven basic toolsofquality control.[5] It is known as a fishbone diagram because of its shape, similar to the side view of a fish skeleton.
Mazda Motors famously used an Ishikawa diagram in the development of the Miata (MX5) sports car.[6]
Root-cause analysis is intended to reveal key relationships among various variables, and the possible causes provide additional insight into process behavior. It shows high-level causes that lead to the problem encountered by providing a snapshot of the current situation.[1]
There can be confusion about the relationships between problems, causes, symptoms and effects. Smith[7] highlights this and the common question “Is that a problem or a symptom?” which mistakenly presumes that problems and symptoms are mutually exclusive categories. A problem is a situation that bears improvement; a symptom is the effect of a cause: a situation can be both a problem and a symptom.
At a practical level, a cause is whatever is responsible for, or explains, an effect - a factor "whose presence makes a critical difference to the occurrence of an outcome".[8]
The causes emerge by analysis, often through brainstorming sessions, and are grouped into categories on the main branches off the fishbone. To help structure the approach, the categories are often selected from one of the common models shown below, but may emerge as something unique to the application in a specific case.
Each potential cause is traced back to find the root cause, often using the 5 Whys technique.[9]
This common model for identifying crucial attributes for planning in product marketing is often also used in root-cause analysis as categories for the Ishikawa diagram:[11]
^Hankins, Judy (2001). Infusion Therapy in Clinical Practice. p. 42.
^Tague, Nancy R. (2004). "Seven Basic Quality Tools". The Quality Toolbox. Milwaukee, Wisconsin: American Society for Quality. p. 15. Retrieved 2010-02-05.
^Frey, Daniel D.; Fukuda, S.; Rock, Georg (2011). Improving complex systems today : proceedings of the 18th ISPE International Conference on Concurrent Engineering. Springer-Verlag London. ISBN978-0857297990. OCLC769756418.
^Smith, Gerald F. "Determining the cause of quality problems: lessons from diagnostic disciplines." Quality Management Journal 5.2 (1998): 24-41.
^Schustack, Miriam W. "Thinking about causality." The psychology of human thought (1988): 92-115.
^Weeden, Marcia M. (1952). Failure mode and effects analysis (FMEAs) for small business owners and non-engineers : determining and preventing what can go wrong. Quality Press. ISBN0873899180. OCLC921141300.
