Ishikawa diagram

Last updated
Ishikawa diagram
Cause and effect diagram for defect XXX.svg
One of the Seven Basic Tools of Quality
First described by Kaoru Ishikawa
PurposeTo 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]

Contents

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.

Overview

Sample Ishikawa diagram shows the causes contributing to problem. Ishikawa Fishbone Diagram.svg
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 tools of quality 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 causes

An Ishikawa diagram breaking down possible root causes of a blurry photo Blurry photo fishbone diagram.svg
An Ishikawa diagram breaking down possible root causes of a blurry photo

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 considerable 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?” This question mistakenly presumes that problems and symptoms are contrasting categories, like light and heavy, such that something can’t be both. 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]

Typical categories include:

The 5 Ms (used in manufacturing)

Originating with lean manufacturing and the Toyota Production System, the 5 Ms is one of the most common frameworks for root-cause analysis: [10]

These have been expanded by some to include an additional three, and are referred to as the 8 Ms: [11]

The 8 Ps (used in product marketing)

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]

The 4 or 5 Ss (used in service industries)

An alternative used for service industries, uses four categories of possible cause: [12]

See also

Citations

  1. 1 2 3 Project Management Institute 2015, pp. 20–24, §2.4.4.2 Cause-and-Effect Diagrams.
  2. Ishikawa, Kaoru (1968). Guide to Quality Control. Tokyo: JUSE.
  3. Ishikawa, Kaoru (1976). Guide to Quality Control . Asian Productivity Organization. ISBN   92-833-1036-5.
  4. Hankins, Judy (2001). Infusion Therapy in Clinical Practice. p. 42.
  5. Tague, Nancy R. (2004). "Seven Basic Quality Tools". The Quality Toolbox. Milwaukee, Wisconsin: American Society for Quality. p. 15. Retrieved 2010-02-05.
  6. 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. ISBN   978-0857297990. OCLC   769756418.
  7. Smith, Gerald F. "Determining the cause of quality problems: lessons from diagnostic disciplines." Quality Management Journal 5.2 (1998): 24-41.
  8. Schustack, Miriam W. "Thinking about causality." The psychology of human thought (1988): 92-115.
  9. "Fishbone diagram: Solving problems properly". IONOS Startupguide. Retrieved 2021-12-23.
  10. Weeden, Marcia M. (1952). Failure mode and effects analysis (FMEAs) for small business owners and non-engineers : determining and preventing what can go wrong. ISBN   0873899180. OCLC   921141300.
  11. 1 2 Bradley, Edgar (2016-11-03). Reliability engineering : a life cycle approach. ISBN   978-1498765374. OCLC   963184495.
  12. Dudbridge, Michael (2011). Handbook of Lean Manufacturing in the Food Industry. John Wiley & Sons. ISBN   978-1444393118. OCLC   904826764.

Related Research Articles

Six Sigma () is a set of techniques and tools for process improvement. It was introduced by American engineer Bill Smith while working at Motorola in 1986.

Kaizen is a concept referring to business activities that continuously improve all functions and involve all employees from the CEO to the assembly line workers. Kaizen also applies to processes, such as purchasing and logistics, that cross organizational boundaries into the supply chain. It has been applied in healthcare, psychotherapy, life coaching, government, manufacturing, and banking.

In science and engineering, root cause analysis (RCA) is a method of problem solving used for identifying the root causes of faults or problems. It is widely used in IT operations, manufacturing, telecommunications, industrial process control, accident analysis, medicine, healthcare industry, etc. Root cause analysis is a form of inductive and deductive inference.

Kaoru Ishikawa was a Japanese organizational theorist and a professor in the engineering faculty at the University of Tokyo who was noted for his quality management innovations. He is considered a key figure in the development of quality initiatives in Japan, particularly the quality circle. He is best known outside Japan for the Ishikawa or cause and effect diagram, often used in the analysis of industrial processes.

<span class="mw-page-title-main">Flowchart</span> Diagram that represents a workflow or process

A flowchart is a type of diagram that represents a workflow or process. A flowchart can also be defined as a diagrammatic representation of an algorithm, a step-by-step approach to solving a task.

Ideation is the creative process of generating, developing, and communicating new ideas, where an idea is understood as a basic element of thought that can be either visual, concrete, or abstract. Ideation comprises all stages of a thought cycle, from innovation, to development, to actualization. Ideation can be conducted by individuals, organizations, or crowds. As such, it is an essential part of the design process, both in education and practice.

A quality circle or quality control circle is a group of workers who do the same or similar work, who meet regularly to identify, analyze and solve work-related problems. It consists of minimum three and maximum twelve members in number. Normally small in size, the group is usually led by a supervisor or manager and presents its solutions to management; where possible, workers implement the solutions themselves in order to improve the performance of the organization and motivate employees. Quality circles were at their most popular during the 1980s, but continue to exist in the form of Kaizen groups and similar worker participation schemes.

DMAIC or define, measure, analyze, improve and control refers to a data-driven improvement cycle used for improving, optimizing and stabilizing business processes and designs. The DMAIC improvement cycle is the core tool used to drive Six Sigma projects. However, DMAIC is not exclusive to Six Sigma and can be used as the framework for other improvement applications.

<span class="mw-page-title-main">Check sheet</span> Form (document) used to collect data in real time at the location where the data is generated

The check sheet is a form (document) used to collect data in real time at the location where the data is generated. The data it captures can be quantitative or qualitative. When the information is quantitative, the check sheet is sometimes called a tally sheet.

Five whys is an iterative interrogative technique used to explore the cause-and-effect relationships underlying a particular problem. The primary goal of the technique is to determine the root cause of a defect or problem by repeating the question "Why?" five times. The answer to the fifth why should reveal the root cause of the problem.

A quality storyboard is a visual tool used in production and product development to outline the quality and performance standards for a project or product, ensuring that the final product meets or exceeds the specified objectives.

One of the thinking processes in the theory of constraints, a current reality tree (CRT) is a tool to analyze many systems or organizational problems at once. By identifying root causes common to most or all of the problems, a CRT can greatly aid focused improvement of the system. A current reality tree is a directed graph.

The seven management and planning tools have their roots in operations research work done after World War II and the Japanese total quality control (TQC) research.

Eight Disciplines Methodology (8D) is a method or model developed at Ford Motor Company used to approach and to resolve problems, typically employed by quality engineers or other professionals. Focused on product and process improvement, its purpose is to identify, correct, and eliminate recurring problems. It establishes a permanent corrective action based on statistical analysis of the problem and on the origin of the problem by determining the root causes. Although it originally comprised eight stages, or 'disciplines', it was later augmented by an initial planning stage. 8D follows the logic of the PDCA cycle. The disciplines are:

<span class="mw-page-title-main">Accident analysis</span> Process to determine the causes of accidents to prevent recurrence

Accident analysis is a process carried out in order to determine the cause or causes of an accident so as to prevent further accidents of a similar kind. It is part of accident investigation or incident investigation. These analyses may be performed by a range of experts, including forensic scientists, forensic engineers or health and safety advisers. Accident investigators, particularly those in the aircraft industry, are colloquially known as "tin-kickers". Health and safety and patient safety professionals prefer using the term "incident" in place of the term "accident". Its retrospective nature means that accident analysis is primarily an exercise of directed explanation; conducted using the theories or methods the analyst has to hand, which directs the way in which the events, aspects, or features of accident phenomena are highlighted and explained. These analyses are also invaluable in determining ways to prevent future incidents from occurring. They provide good insight by determining root causes, into what failures occurred that lead to the incident.

Corrective and preventive action consists of improvements to an organization's processes taken to eliminate causes of non-conformities or other undesirable situations. It is usually a set of actions, laws or regulations required by an organization to take in manufacturing, documentation, procedures, or systems to rectify and eliminate recurring non-conformance. Non-conformance is identified after systematic evaluation and analysis of the root cause of the non-conformance. Non-conformance may be a market complaint or customer complaint or failure of machinery or a quality management system, or misinterpretation of written instructions to carry out work. The corrective and preventive action is designed by a team that includes quality assurance personnel and personnel involved in the actual observation point of non-conformance. It must be systematically implemented and observed for its ability to eliminate further recurrence of such non-conformation. The Eight disciplines problem solving method, or 8D framework, can be used as an effective method of structuring a CAPA.

<span class="mw-page-title-main">Seven basic tools of quality</span> Fixed set of visual exercises for troubleshooting issues related to quality

The seven basic tools of quality are a fixed set of visual exercises identified as being most helpful in troubleshooting issues related to quality. They are called basic because they are suitable for people with little formal training in statistics and because they can be used to solve the vast majority of quality-related issues.

<span class="mw-page-title-main">Accident</span> Unforeseen event, often with a negative outcome

An accident is an unintended, normally unwanted event that was not directly caused by humans. The term accident implies that nobody should be blamed, but the event may have been caused by unrecognized or unaddressed risks. Most researchers who study unintentional injury avoid using the term accident and focus on factors that increase risk of severe injury and that reduce injury incidence and severity. For example, when a tree falls down during a wind storm, its fall may not have been caused by humans, but the tree's type, size, health, location, or improper maintenance may have contributed to the result. Most car wrecks are not true accidents; however, English speakers started using that word in the mid-20th century as a result of media manipulation by the US automobile industry.

<span class="mw-page-title-main">Issue tree</span>

An issue tree, also called logic tree, is a graphical breakdown of a question that dissects it into its different components vertically and that progresses into details as it reads to the right.

<span class="mw-page-title-main">A3 problem solving</span> Structured problem improvement approach

A3 problem solving is a structured problem-solving and continuous-improvement approach, first employed at Toyota and typically used by lean manufacturing practitioners. It provides a simple and strict procedure that guides problem solving by workers. The approach typically uses a single sheet of ISO A3-size paper, which is the source of its name.

References