> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/universal/problem-solving/ishikawa-diagram.md).

# Ishikawa Diagram

<figure><img src="/files/HMNRboOBHwCpA73U9BrG" alt=""><figcaption><p>Image by <a href="https://kaizen.com/insights/ishikawa-diagram-root-cause-analysis/">Kaizen Institute</a></p></figcaption></figure>

{% hint style="info" %}
AKA Fishbone Diagram, Cause-and-effect Diagram
{% endhint %}

The Ishikawa Diagram constitutes a graphical tool utilised in quality management and root cause analysis. It was developed by Japanese quality control statistician Kaoru Ishikawa and serves to systematically explore and visualise the many potential factors that contribute to a specific problem or outcome, referred to as the "Effect."

The diagram’s structure resembles the skeleton of a fish, which accounts for its common name. The "Effect," or problem statement, is written at the head of the fish, typically on the right side of the diagram, with a central horizontal line, the "spine," running to the left . Major categories of potential causes branch off from this spine, forming the main "bones."&#x20;

These major cause categories provide a framework for brainstorming, often encompassing standard groupings such as the 6 Ms in manufacturing, which include Manpower (people), Methods (processes), Machines (equipment), Materials, Measurement (inspection), and Mother Nature (environment). For service industries, common alternatives include the 4 Ps, such as Policies, Procedures, People, and Plant/Technology.

The process unfolds as a team brainstorms all conceivable contributors to the problem, placing each factor as a smaller line, or sub-branch, off the relevant major cause category. This systematic visual mapping compels a deep exploration of causality, moving beyond superficial symptoms to uncover underlying issues.&#x20;

By repeatedly asking "Why does this happen," increasingly detailed levels of cause and sub-cause are added to the diagram, ensuring a comprehensive analysis that ideally leads to the root causes of the "Effect," thereby allowing for the development of effective corrective actions. The resulting graphic serves to organise a complex array of ideas, fostering a shared understanding of the problem among all participants.

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=mLvizyDFLQ4>" %}

#### Further Reading

{% embed url="<https://untools.co/ishikawa-diagram/>" %}

{% embed url="<https://asq.org/quality-resources/fishbone>" %}

{% embed url="<https://kaizen.com/insights/ishikawa-diagram-root-cause-analysis/>" %}

{% embed url="<https://safetyculture.com/topics/ishikawa-diagram>" %}

{% embed url="<https://www.investopedia.com/terms/i/ishikawa-diagram.asp>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.designreference.xyz/cognitive-tools/universal/problem-solving/ishikawa-diagram.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.