What is a fishbone diagram?

    Short answer

    A fishbone diagram, also called an Ishikawa or cause-and-effect diagram, is a visual tool that maps all the possible causes of a problem, grouped into categories. The problem sits at the "head" and causes branch off a central "spine" like fish bones. Teams use it to brainstorm broadly before testing which causes are real.

    Last updated · TeamAssurance

    Where it comes from

    The diagram is named after Kaoru Ishikawa, who popularised it in Japanese quality circles. It remains one of the basic quality tools because it makes a team's thinking visible and stops the group jumping to the first, most obvious cause.

    Common categories

    In manufacturing, the 6Ms are the usual starting point:

    • Man (people): skills, training, fatigue, staffing.
    • Machine: equipment condition, settings, tooling.
    • Method: procedures, standard work, sequence.
    • Material: raw materials, components, supplier variation.
    • Measurement: gauges, calibration, inspection method.
    • Mother Nature (environment): temperature, humidity, lighting, layout.

    Service and healthcare teams often adapt these, for example using policies, procedures, people and place. Choose categories that fit the problem rather than forcing all six.

    How to build one

    1. Write a specific problem statement in the head of the fish.
    2. Draw the spine and add the category bones.
    3. Brainstorm possible causes under each category with people who know the process.
    4. Ask why for each cause to add sub-branches.
    5. Mark the causes the team thinks are most likely.
    6. Test those causes with data or observation at gemba before acting.

    Common mistakes

    • Treating every cause on the diagram as proven. The fishbone generates hypotheses; it does not confirm them.
    • Writing vague causes such as "training" instead of specific ones like "new starters not trained on changeover".
    • Building it alone at a desk rather than with the team at the process.
    • Starting with a vague problem statement, which produces a sprawling diagram.

    Example

    A food plant sees inconsistent seal strength on pouches. The team's fishbone lists sealing jaw temperature drift (machine), film thickness variation between suppliers (material), an outdated set-up sheet (method) and a pull tester overdue for calibration (measurement). Data from the line shows seal failures track jaw temperature, so the team focuses its 5 whys and countermeasures there.

    How TeamAssurance helps

    TeamAssurance's root cause analysis method supports investigating problems with fishbone diagrams, fault tree analysis and other structured approaches, tracked via tiered daily management. AI agents can draft a first fishbone of potential causes organised by category, then work through it with the team to challenge causes, add evidence and narrow in on the likely root cause.

    Frequently asked questions

    What are the 6Ms of a fishbone diagram?

    Man (people), Machine, Method, Material, Measurement and Mother Nature (environment). Some teams add Management or Money as extra categories.

    Is a fishbone diagram the same as an Ishikawa diagram?

    Yes. Fishbone, Ishikawa and cause-and-effect diagram are three names for the same tool.

    When should you use a fishbone instead of the 5 whys?

    Use a fishbone when a problem may have many possible causes and you need to explore broadly. Use the 5 whys to drill into a likely cause once it has been identified.