Editing Ishikawa diagram

{{short description|Causal diagrams created by Kaoru Ishikawa}}
{{Infobox quality tool
| image =     Cause and effect diagram for defect XXX.svg
| category =  One of the [[Seven Basic Tools of Quality]]
| describer = [[Kaoru Ishikawa]]
| purpose =   To break down (in successive layers of detail) root causes that potentially contribute to a particular effect
}}
'''Ishikawa diagrams''' (also called '''fishbone diagrams''',{{sfn | Project Management Institute | 2015 | loc=§2.4.4.2 Cause-and-Effect Diagrams | pp=20-24}} '''herringbone diagrams''', '''cause-and-effect diagrams''') are [[causal diagram]]s created by [[Kaoru Ishikawa]] that show the potential [[cause]]s of a specific event.<ref>{{cite book | last = Ishikawa |first = Kaoru | title= Guide to Quality Control | year = 1968 | publisher = JUSE | location = Tokyo
}}</ref>

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==
[[File:Ishikawa Fishbone Diagram.svg|alt=|left|thumb|Sample Ishikawa diagram shows the causes contributing to problem.]]
The ''defect'', or the problem to be solved,{{sfn | Project Management Institute | 2015 | loc=§2.4.4.2 Cause-and-Effect Diagrams | pp=20-24}} 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.<ref>{{cite book|title=Guide to Quality Control|url=https://archive.org/details/guidetoqualityco00ishi|url-access=registration|last=Ishikawa|first=Kaoru|publisher=Asian Productivity Organization|year=1976|isbn=92-833-1036-5}}</ref>

Ishikawa diagrams were popularized in the 1960s by [[Kaoru Ishikawa]],<ref>{{cite book |year=2001 |title=Infusion Therapy in Clinical Practice |first=Judy |last=Hankins |pages=42}}</ref> who pioneered quality management processes in the [[Kawasaki Heavy Industries|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|seven basic tools]] of [[quality control]].<ref>{{cite web|url=https://asq.org/quality-resources/seven-basic-quality-tools|title=Seven Basic Quality Tools|last=Tague|first=Nancy R.|year=2004|work=The Quality Toolbox|publisher=American Society for Quality|location=Milwaukee, Wisconsin|page=15|access-date=2010-02-05}}</ref> It is known as a fishbone diagram because of its shape, similar to the side view of a fish skeleton.

[[Mazda|Mazda Motors]] famously used an Ishikawa diagram in the development of the [[Mazda MX-5 Miata|Miata]] ([[Mazda MX-5|MX5]]) sports car.<ref>{{Cite book|title=Improving complex systems today : proceedings of the 18th ISPE International Conference on Concurrent Engineering|last1=Frey|first1=Daniel D.|last2=Fukuda, S.|first3=Georg|last3=Rock|date=2011|publisher=Springer-Verlag London|isbn=978-0857297990|oclc=769756418}}</ref>

== Advantages of the Ishikawa Diagram ==

# '''Visual and easy to understand'''   Its fishbone-like structure allows for a clear and organized graphical representation of the causes of a problem. This makes it easy to understand even for people without technical experience.
# '''Encourages teamwork'''   It is an ideal tool for group brainstorming sessions. It allows team members to contribute different perspectives, enriching the analysis and improving the identification of causes.
# '''Organizes causes in a logical way'''   It groups causes into categories (such as the 5Ms or 4Ss), allowing the problem to be analyzed from different angles. This structure helps quickly identify critical areas within the process.

== Root causes ==
[[File:blurry_photo_fishbone_diagram.svg|thumb|250px|An Ishikawa diagram breaking down possible root causes of a blurry photo]]
{{More citations needed section|date=June 2023}}
[[Root cause analysis|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.{{sfn | Project Management Institute | 2015 | loc=§2.4.4.2 Cause-and-Effect Diagrams | pp=20-24}}

There can be confusion about the relationships between problems, causes, symptoms and effects. Smith<ref name="Smith">Smith, Gerald F. "Determining the cause of quality problems: lessons from diagnostic disciplines." Quality Management Journal 5.2 (1998): 24-41.</ref> 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".<ref name=" Schustack ">Schustack, Miriam W. "Thinking about causality." The psychology of human thought (1988): 92-115.</ref>

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.<ref>{{Cite web|title=Fishbone diagram: Solving problems properly|url=https://www.ionos.ca/startupguide/productivity/fishbone-diagram/|access-date=2021-12-23|website=IONOS Startupguide|language=en}}</ref>

Typical categories include:

===The 5 Ms (used in manufacturing)===
{{See also|5M model}}Originating with lean manufacturing and the [[Toyota Production System]], the 5 Ms is one of the most common frameworks for root-cause analysis:<ref>{{Cite book|title=Failure mode and effects analysis (FMEAs) for small business owners and non-engineers : determining and preventing what can go wrong|last=Weeden|first=Marcia M.|year=1952|publisher=Quality Press |isbn=0873899180|oclc=921141300}}</ref>
*Manpower / Mindpower (physical or knowledge work, includes: [[kaizen]]s, suggestions)
*Machine (equipment, technology)
*Material (includes raw material, consumables, and information)
*Method (process)
*Measurement / medium (inspection, environment)
These have been expanded by some to include an additional three, and are referred to as the 8 Ms:<ref name=":0">{{Cite book|title=Reliability engineering : a life cycle approach|last=Bradley|first=Edgar|isbn=978-1498765374|oclc=963184495|date = 2016-11-03|publisher=CRC Press }}</ref>
*Mission / mother nature (purpose, environment)
*Management / money power (leadership)
*Maintenance

===The 8 Ps (used in product marketing)===
{{See also|Marketing mix}}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:<ref name=":0" />
*Product (or service)
*Price
*Place
*Promotion
*People (personnel)
*Process
*Physical evidence (proof)
*Performance

===The 4 or 5 Ss (used in service industries)===
An alternative used for service industries, uses four categories of possible cause:<ref>{{Cite book|title=Handbook of Lean Manufacturing in the Food Industry|last=Dudbridge|first=Michael|date=2011|publisher=John Wiley & Sons|isbn=978-1444393118|oclc=904826764}}</ref> 
*Surroundings: Refers to the environment in which the process occurs.
*Suppliers: Refers to external parties that provide inputs—raw materials, components, or services.
*Systems: Refers to the procedures, processes, and technologies used to perform the work.
*Skill: Refers to the human factor, particularly the knowledge and abilities of employees.
*Safety: Refers to physical and psychological well-being in the workplace.

==Use in specific industries==
The Ishikawa diagram has been widely adopted across various industries as an effective tool for root cause analysis in quality, efficiency, and safety-related issues. Its versatility allows it to be applied in both manufacturing and service contexts.

In the manufacturing industry, particularly in the automotive and electronics sectors, the diagram is frequently used in continuous improvement initiatives such as Six Sigma and Lean Manufacturing. Quality teams use it to identify causes related to materials, methods, machinery, manpower, environment, and measurement, facilitating informed decision-making to reduce defects and optimize processes.

In the food industry, the Ishikawa diagram is applied to analyze issues related to food safety, temperature control, cross-contamination, and regulatory compliance. Its use enables companies to identify improvement opportunities in production, packaging, and distribution stages.

In the pharmaceutical sector, it is a key tool in process validation, quality control, and compliance with Good Manufacturing Practices (GMP). It helps visualize factors affecting product quality from formulation to storage.

It has also been successfully implemented in sectors such as aerospace, pulp and paper, construction, education, and healthcare, where it supports structured problem-solving and promotes continuous improvement and a culture of quality.

== See also ==
{{Portal|Philosophy|Psychology}}
* [[Seven basic tools of quality]]
* [[Five whys]]
* [[Issue map]]
* [[Issue tree]]
* [[Resource management]]

== Citations ==
{{Reflist|30em}}

== References ==
{{Commons category|Ishikawa diagrams}}
* Ishikawa, Kaoru (1990); (Translator: J. H. Loftus); ''Introduction to Quality Control''; 448 p; {{ISBN|4-906224-61-X}} {{OCLC|61341428}}
* Dale, Barrie G. et al. (2007); ''Managing Quality 5th ed''; {{ISBN|978-1-4051-4279-3}} {{OCLC|288977828}}
* {{cite book | last= Project Management Institute | title=Business Analysis for Practitioners | publisher=Project Management Inst | date=2015-01-01 | isbn=978-1-62825-069-5}}

{{Quality Tools}}
{{Authority control}}

{{DEFAULTSORT:Ishikawa diagram}}
[[Category:Causal diagrams]]
[[Category:Knowledge representation]]
[[Category:Quality control tools]]
[[Category:Japanese inventions]]