Guide

How to Create a Fishbone Diagram (Ishikawa) + Template

Updated Feb 16, 2026
5 Min Read
Struggling to find the root cause? Learn how to create a Fishbone Diagram (Ishikawa) using the 6Ms. Download our free template and follow the step-by-step guide.
What is Fishbone Diagram
Last Updated Feb 16, 2026
At a Glance
  • The Fishbone Diagram is a structured root cause analysis tool used to systematically explore all possible causes of a problem rather than jumping to conclusions.
  • The key steps are: Clearly define the problem, identify major cause categories, brainstorm potential causes, and drill down to deeper root causes — building a complete picture of why the issue exists.
  • The Fishbone Diagram is not just a brainstorming exercise; it is a disciplined method that helps teams move beyond symptoms and assumptions to evidence-based causes.
  • Cause clarity is the goal — organising potential causes visually makes gaps, patterns, and weak assumptions obvious, enabling better follow-up analysis and actions.
  • Best results come from cross-functional input and using the Fishbone as a thinking tool, not a final answer — it should feed into data validation, 5 Whys, and corrective action planning.

When a problem seems too difficult to solve, the Fishbone Diagram helps you cut through the noise. Also often refered to as the Ishikawa Diagram or Cause-and-Effect Diagram, this visual framework is more than just a brainstorming tool; it is a systematic way to diagnose the health of your process.

Fishbone diagram Lean Six SIgma Tool Ishikawa Diagrams Root Cause Analysis (RCA) Fish Bone Diagram Ishikawa Diagram Cause and Effect Diagram

While simple lists often focus on symptoms (what happened), the Fishbone Diagram forces your team to dig for root causes (why it happened). By mapping potential factors into categories like the 6Ms (Man, Method, Machine, Material, Measurement, Mother Nature), it ensures no stone is left unturned, providing a comprehensive blueprint for solving even the most stubborn quality issues.

What is a Fishbone Diagram?

At its core, the Fishbone Diagram is a structured brainstorming map. Unlike a standard list, which can feel chaotic or unstructured, this tool forces you to group causes into logical categories. The categories also work as prompts for topics such as method causes or machine causes of the problem.

Key Components

  • The Head (The Effect): This box on the far right contains the specific problem statement. Everything in the diagram points toward this outcome.
  • The Spine (The Central Axis): This is the long horizontal arrow pointing to the head. It acts as the central gathering point for all contributing factors.
  • The Main Bones (Categories): These large branches stem off the spine. They represent the major categories of the process (often the 6Ms in manufacturing or 4Ps in service).
  • The Sub-Bones (Specific Causes): These smaller lines branch off the main bones. This is where the actual insights live—the specific root causes identified by asking “Why?”
From Causes to Risk Prioritisation

The Fishbone Diagram helps identify possible causes, but it does not quantify risk. Teams often follow this step by completing an FMEA template to score each failure mode and decide which risks require immediate action.

Apply the FMEA template
FREE

Join the 28-Day Lean Challenge

Take your skills to the next level. Join 15,000+ practitioners and get exclusive tools delivered to your inbox.

Daily Lessons 5 Bonus Templates PDF Guides
Start the Challenge

No spam. Unsubscribe anytime.

Why Use a Fishbone Diagram?

The Fishbone Diagram is more than just a drawing; it is a framework that changes how your team thinks. Here is why it is an essential tool for effective problem solving:

  1. It Tames the Chaos (Visualization) Brainstorming sessions often produce a messy list of unrelated ideas. The Fishbone Diagram forces you to organize these thoughts instantly. By grouping ideas into categories (like the 6Ms), it transforms a chaotic discussion into a structured, visual map of the problem.
  2. It Removes the “Blame Game” (Collaboration) In many meetings, it’s easy to focus on who caused the problem. The Fishbone structure shifts the focus to what caused the problem. By looking at “Methods,” “Materials,” and “Machines” alongside “People,” it objectively analyzes the process, not the person, fostering a safer and more creative environment.
  3. It Prevents “Band-Aid” Solutions (Root Cause) Teams often rush to fix the immediate symptom (e.g., “Clean up the oil spill”). The Fishbone Diagram slows you down and forces you to ask “Why?” across multiple categories. This discipline ensures you find and fix the root cause (e.g., “Replace the cracked seal”), preventing the problem from ever coming back.
RCA Guide

How to Create a
Fishbone Diagram

Materials You'll Need

  • The Canvas: A large whiteboard, paper, or a digital whiteboard tool (like Miro or Mural). We also have an Excel-based Fishbone Diagram template you can use.
    "Personally, I prefer to have a large piece of paper with the fishbone diagram on and sticky notes. It drives engagement and involvement from the team to read out inputs as they add them to the diagram."
  • Writing Tools: Different colored markers (colors help separate categories).
  • Sticky Notes: These are crucial—they allow you to move causes around if you categorize them wrong initially.
  • The Team: A cross-functional group (e.g., operators, engineers, managers) to ensure diverse perspectives.
1

Identify the Problem

THE HEAD
The first and most crucial step is to clearly identify the problem you are trying to solve. This statement acts as the anchor for the entire session. If the problem is vague, your solutions will be vague.

How to Write a Problem Statement

❌ Bad Examples
  • "Defects are too high." (Vague)
  • "John broke the machine." (Blame)
✅ Good Examples
  • "Cap defects > 5% on Line A." (Specific)
  • "Machine 2 stopped 4h on Tues." (Factual)
PROBLEM

Figure 1: The Head focuses on the specific effect

Pro Tip

Never embed a cause in your problem statement (e.g., 'Machine stopping due to bad sensors'). Just state the factual observation.

2

Draw the Spine & Categories

THE 6MS FRAMEWORK
Draw a long horizontal arrow pointing to the head. This is the "Spine". Next, add diagonal lines branching off the spine. These are your major categories (The 6Ms).

Not in Manufacturing? Try These:

  • Service (4Ps): Places, Procedures, People, Policies.
  • Office (PEM): People, Environment, Methods.
PROBLEM Methods Machines Materials People Measure Env

Figure 2: The 6Ms provide a structured framework

Pro Tip

Don't get stuck debating where a cause belongs. If 'Training' fits under both People and Methods, just pick one and move on.

3

Brainstorm Potential Causes

THE RIBS
Shift to brainstorming. Go through each category one by one and ask: "What specific factors in the [Machine] category could cause [The Problem]?"The goal here is quantity, not quality. Encourage wild ideas.

Facilitation: Silent Brainstorming

1 Give everyone sticky notes and a pen.
2 Set a timer for 5 minutes (Absolute Silence).
3 One cause per note.
PROBLEM Methods Machines Materials People Measure Env Wrong temp Speed low

Figure 3: Populate the diagram with contributors

4

Dig Deeper (The 5 Whys)

SUB-CAUSES
Initial ideas are just symptoms. Drill down using the 5 Whys technique directly on the diagram.

Example Drill Down

Cause Machine overheated.
Why? Coolant lines were clogged.
Why? Filter wasn't replaced on schedule. (Root Cause)
PROBLEM Methods Wrong temp Broken sensor

Figure 4: Branching creates a detailed map

5

Analyze & Prioritize

ROOT CAUSES
You cannot fix everything. Prioritize the top few causes and verify them.

Verification Checklist

  • 1. Go to Gemba: Observe personally.
  • 2. Check Data: Do logs match the theory?
  • 3. Run a Test: Can you toggle the problem on/off?
PROBLEM Broken sensor ROOT CAUSE

Figure 5: Highlight critical factors

Examples and Case Studies: Understanding Fishbone Diagrams in Action

Case Study: Manufacturing Unit with Quality Issues

Imagine you run a manufacturing unit, and you’ve been receiving complaints about the quality of your products. You decide to use a Fishbone Diagram to get to the root of the issue.

Step 1: Identify the Problem
Problem Statement: “High number of defective products in the last quarter.”

Step 2: Main Categories

  • People
  • Process
  • Equipment
  • Environment

Step 3: Brainstorm Causes

  • People: Untrained staff, high employee turnover
  • Process: Inconsistent quality checks, outdated SOPs (Standard Operating Procedures)
  • Equipment: Aged machinery, lack of maintenance
  • Environment: Poor lighting, extreme temperature fluctuations

Step 4: Dig Deeper (5 Whys)

  • Untrained Staff: Why? No formal training program.
  • Aged Machinery: Why? No budget allocated for equipment upgrades.

Step 5: Analyze and Take Action

After analyzing the Fishbone Diagram, you realize that untrained staff and aged machinery are your primary culprits. Your next steps could involve investing in staff training programs and allocating budget for machinery upgrades.

By following these steps, you can develop targeted strategies to improve product quality significantly.

Common Mistakes and Tips: How to Make the Most of Your Fishbone Diagram

1. Overlooking Minor Causes

While it’s easy to focus on the most glaring issues, minor causes can accumulate and have a significant impact.

Tip: Don’t disregard a cause just because it seems minor. Sometimes, fixing smaller issues can lead to big improvements.

2. Ignoring Data

It’s tempting to rely solely on brainstorming and intuition, but data should be your guiding star.

Tip: Use metrics and KPIs to support or refute the causes you’ve identified. This adds credibility to your findings and helps you prioritize effectively.

3. Stopping at Symptoms

Identifying symptoms is just the first step; your ultimate goal should be to uncover the root causes.

Tip: Use techniques like the “5 Whys” to dig deeper into each cause and ensure you’re addressing the root of the issue, not just its manifestations.

Want exclusive templates, tools and guides?

Join our email list below and for the next 28 days, we will send you exclusive tools, templates and guides unavailable on the website. We developed a short and simple 28-day program designed to develop your ability to implement Lean and Six Sigma methods daily.

Conclusion

Fishbone Diagrams are a fantastic asset in the toolbox of anyone interested in continuous improvement. Whether you’re a seasoned professional or just getting started, this simple yet powerful tool can help you dissect complex problems and develop targeted solutions.

They encourage you to look beyond the obvious and delve into the intricacies that contribute to each problem. So go ahead, grab that pen and paper (or a whiteboard, if you’re feeling fancy), and start your journey towards effective problem-solving.

References

A: The Fishbone Diagram was originally developed by Dr. Kaoru Ishikawa, a Japanese quality control statistician, in the 1960s. It’s also sometimes referred to as the Ishikawa Diagram in his honor.

A: Absolutely! While Fishbone Diagrams are popular in manufacturing and quality management, their application is not limited to these areas. They can be used in healthcare, software development, event planning, and even for personal problem-solving.

A: The number of main categories can vary depending on the complexity of the problem. However, it’s generally advisable to have between 4-6 main categories for easier analysis and readability.

A: Yes, there are several software tools available for creating Fishbone Diagrams, such as Microsoft Visio, Lucidchart, and various other project management software options. However, a simple pen and paper or a whiteboard can be just as effective for smaller teams or simpler problems.

A: After creating your Fishbone Diagram, you should analyze it with your team to identify the most likely root causes of the problem. Using data to support your conclusions can be very helpful. You may also employ techniques like the Pareto Analysis to prioritize causes based on their impact.

Daniel Croft-Bednarski

Continuous Improvement Manager
#1 Free Resource Library

Daniel Croft-Bednarski is a Continuous Improvement Manager with a passion for Lean Six Sigma and continuous improvement. With years of experience in developing operational excellence, Daniel specializes in simplifying complex concepts and engaging teams to drive impactful changes.

10+ Years Experience
50+ Projects Led
LSS Black Belt