diverge · Problem Solving · 30–60 min · 3-12 people · medium energy

Ishikawa Diagram (Fishbone Diagram)

The Ishikawa Diagram, also known as a Fishbone or Cause-and-Effect Diagram, is a visual tool for identifying the root causes of a specific problem. It helps teams systematically explore potential contributing factors and understand complex relationships.

When to use Ishikawa Diagram (Fishbone Diagram)

Use this method when a team is struggling to understand the underlying causes of a persistent problem or when a structured approach is needed to analyze a complex issue.

What it solves

Superficial solutions that don't address the core issues; jumping to conclusions without thorough analysis; lack of shared understanding of the problem's complexity.

How to run Ishikawa Diagram (Fishbone Diagram), step by step

  1. Define the Problem (5 minutes). Clearly state the problem you want to address. Write it at the 'head' of the fishbone.
  2. Identify Contributing Factors (10 minutes). Brainstorm major categories of factors that could be contributing to the problem (e.g., People, Equipment, Methods, Materials, Environment). Draw these as 'bones' branching off the main line.
  3. Explore Root Causes (20 minutes). For each factor, ask 'Why is this happening?' repeatedly (the 'Five Whys' technique) to drill down to potential root causes. Add these as smaller branches off each factor bone.
  4. Analyze the Diagram (25 minutes). Review the completed diagram to identify the most likely root causes. Look for recurring causes or those that appear under multiple factors. Prioritize investigation and action based on impact and feasibility.

Materials needed

  • Whiteboard or large paper
  • Markers or pens
  • Sticky notes (optional)
  • Timer

Facilitator tips

  • Encourage diverse perspectives and challenge assumptions during the brainstorming process.
  • Focus on identifying potential causes, not assigning blame.

Common pitfalls

  • Getting stuck on symptoms instead of root causes. Use the 'Five Whys' technique to dig deeper.
  • Limiting the brainstorming to obvious factors. Encourage creative thinking and exploration of less obvious causes.

Variations

  • Use different categories of factors based on the specific problem (e.g., for a software bug, use categories like Code, Infrastructure, Testing, Design).
  • Conduct a voting process to prioritize the most likely root causes for further investigation.

Running it online or hybrid

Use a shared digital whiteboard like Miro or Mural to allow remote participants to contribute to the diagram in real-time.

What it produces

A visual diagram illustrating the problem and its potential root causes, categorized by contributing factors.

Origin

Based on work by Kaoru Ishikawa — source

Build a session around Ishikawa Diagram (Fishbone Diagram)

METODIC places Ishikawa Diagram (Fishbone Diagram) inside a complete, timed session plan — agenda, worksheets, facilitator guide and slides — matched to your group and goal.

Generate a session with Ishikawa Diagram (Fishbone Diagram) · Try METODIC free