# Ishikawa diagram (Mermaid)

A fishbone diagram groups possible causes into categories so a root cause session stays balanced rather than following whoever spoke first. Drawn as a flowchart it stays editable in text.

---

## What this example shows

* Categories as the first level, causes beneath them.
* One effect at the right-hand end, which everything points at.
* A layout that stays readable as causes are added.

---

## A worked example

Open it, edit it, or copy the source below.

![Ishikawa diagram (Mermaid)](https://help.gocapable.com/images/att1414463714.svg)

The source, which you can paste into a new diagram and edit:

```
ishikawa-beta
    Blurry Photo
    Process
        Out of focus
        Shutter speed too slow
        Protective film not removed
        Beautification filter applied
    User
        Shaky hands
    Equipment
        LENS
            Inappropriate lens
            Damaged lens
            Dirty lens
        SENSOR
            Damaged sensor
            Dirty sensor
    Environment
        Subject moved too quickly
        Too dark
```

---

## Making it your own

* Agree the categories before you start, or everything lands in the first branch drawn.
* Keep asking why within a branch; the first cause listed is rarely the root.
* Causes are not actions. Turn the diagram into actions separately, afterwards.

---

## Related

[Venn diagram (Mermaid)Overlaps, expressed as regions.](https://help.gocapable.com/diagrams/venn-diagram-mermaid.html)

[Event modelling (Mermaid)Commands, events and read models on a timeline.](https://help.gocapable.com/diagrams/event-modelling-mermaid.html)

[Mermaid examplesBack to the rest of these examples.](https://help.gocapable.com/diagrams/mermaid-examples.html)

---

_Copy it. Change one line. See what happens._