problem solving fishbone method

• Guide: Fishbone Diagram

Daniel Croft

Daniel Croft is an experienced continuous improvement manager with a Lean Six Sigma Black Belt and a Bachelor's degree in Business Management. With more than ten years of experience applying his skills across various industries, Daniel specializes in optimizing processes and improving efficiency. His approach combines practical experience with a deep understanding of business fundamentals to drive meaningful change.

• Last Updated: October 19, 2023
• Learn Lean Sigma

The Fishbone Diagram, also known by various other names such as Ishikawa Diagram, Cause and Effect Diagram or 6Ms, is a visual tool used in problem-solving and root cause analysis . Originating from the quality management sector, it is used as a systematic approach to identify, explore, and display possible causes of a specific problem.

Table of Contents

What is a fishbone diagram.

The Fishbone Diagram is a graphical tool used for identifying and organizing possible causes of a specific problem or outcome. The diagram resembles the skeletal structure of a fish, hence its name. At the “head” of the fish is the problem you’re trying to solve, and the “bones” branching off the spine are the multiple potential causes contributing to that problem.

The benefit of a Fishbone Diagram lies in its simplicity. It gives you a structured way to brainstorm and categorize the various factors affecting a specific issue. The diagram can get as detailed as you need it to be, allowing for sub-causes to branch off the main causes, offering even deeper insights.

The Components of a Fishbone Diagram

Head : The fish’s head represents the problem or effect you’re analyzing.

Spine : The long, horizontal line connecting to the head serves as the timeline or sequence of the problem.

Bones : These are the categories of potential causes. They branch off the spine, leading towards the head.

Sub-Bones : These are the more specific factors or sub-causes that stem from the main categories.

Why Use a Fishbone Diagram?

The Fishbone Diagram is a flexible tool that can be used for a range of applications. Here’s why it’s so useful:

1. Easy Visualization:

One of the primary advantages of using a Fishbone Diagram is its ability to simplify complex problems. With all potential causes visually represented in one place, it becomes easier to analyze and discuss the issues.

2. Team Collaboration:

The Fishbone Diagram is excellent for brainstorming sessions. It encourages team members to think critically and contributes to a shared understanding of the problem. It’s collaborative by design, allowing for the collective intelligence of the group to shine.

3. Root Cause Analysis:

Identifying symptoms of a problem is one thing; uncovering the root cause is another. The Fishbone Diagram excels at this by forcing you to dig deep into various contributing factors. By isolating these causes, you’re better positioned to find a lasting solution.

By using a Fishbone Diagram, you’re not just addressing a problem with a short-term fix; you’re conducting a thorough investigation to eliminate issues from the root up.

How to Create a Fishbone Diagram: A Detailed Guide

Creating a Fishbone Diagram might seem like a daunting task, but it’s actually a straightforward process. Here, we’ll break down each step in detail to ensure you can construct a Fishbone Diagram that serves its purpose effectively.

Materials You’ll Need:

• A whiteboard or large sheet of paper
• Markers or pens
• Sticky notes (optional)
• A team of people for brainstorming

Step 1: Identify the Problem

The first and most crucial step is to clearly identify the problem you’re trying to solve. This statement should be specific and concise. Write this problem statement at the far right side of your whiteboard or paper, as it will serve as the “head” of your fishbone diagram.

• Use data to define the problem whenever possible.
• Make sure the problem is mutually understood and agreed upon by all team members.

Step 2: Determine the Main Categories

Now, draw a horizontal line from the problem statement towards the left side of the board. This is the “spine” of your fish. Next, you’ll identify the major categories of causes that could be contributing to the problem. These categories will serve as the main “bones” branching off from the spine.

Common categories often include:

• Measurement
• Environment
• The categories can be industry-specific or general, depending on the problem you’re analyzing.
• Aim for 4-6 main categories for better manageability.

Step 3: Brainstorm Causes

Once you’ve determined the main categories, it’s time to brainstorm potential causes for each category. These causes will be the smaller “bones” that branch off from the main bones. If you’re working with a team, this is an excellent time for a brainstorming session.

• Use sticky notes to write down ideas so you can easily move them around.
• Encourage every team member to contribute; sometimes the most unexpected insights come from diverse perspectives.

The output of the root cause analysis at this point may look something like the below example. With the lack of preventative maintenance being explored with the 5Whys analysis.

Step 4: Dig Deeper with Sub-Causes

Sometimes, the primary causes can be broken down into smaller, more specific sub-causes. This is where the “ 5 Whys ” technique can be beneficial. For each primary cause, ask “Why?” up to five times to dig deeper into the root of the issue.

• Not all primary causes will need sub-causes; use your discretion.
• Keep the diagram organized to ensure readability.

Step 5: Analyze and Take Action

After all the causes and sub-causes have been identified, it’s time to analyze the Fishbone Diagram as a team. Highlight or circle the causes that seem most likely to be contributing to the problem. These are the areas that will need immediate attention and action.

• Use data or evidence to support your conclusions.
• Create an action plan assigning responsibility for each highlighted cause.

And there you have it! You’ve successfully created a Fishbone Diagram that will help you get to the root of your problem.

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 : 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.

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.

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.

• Ilie, G. and Ciocoiu, C.N., 2010. Application of fishbone diagram to determine the risk of an event with multiple causes.   Management research and practice ,  2 (1), pp.1-20.
• Coccia, M., 2018. The Fishbone diagram to identify, systematize and analyze the sources of general purpose Technologies.   Journal of Social and Administrative Sciences ,  4 (4), pp.291-303.

Q: What is the origin of the Fishbone Diagram?

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.

Q: Can Fishbone Diagrams be used for non-manufacturing problems?

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.

Q: How many main categories should my Fishbone Diagram have?

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.

Q: Can I use software to create a Fishbone Diagram?

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.

Q: How do I know which causes to prioritize after creating a Fishbone Diagram?

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 is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

Free Lean Six Sigma Templates

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

Other Guides

• Submission Guidelines

fishbone 2021 header

Learning Objectives

After completing the lesson you will be able to:

1)  Define  root cause analysis (RCA)

2)  Demonstrate RCA using a Fishbone Diagram 

Case Study: “Why don’t we get paged sooner?”

At an HCI Clinic, providers are often delayed in how soon they see a patient during a new visit appointment. Typical delays (wait time) from check-in to provider page was 20 minutes. This 20-minute delay presented a cascade of problems for patients and care teams. For patients, it limited face-to-face time with a provider. For residents, the lack of time hindered care - building rapport with patients, potentially missing important details that help inform the care plan. The delay also caused resident job dissatisfaction. To identify all the moving parts in this complex (yet seemingly simple) problem, the team turned to the fishbone diagram as a useful tool to investigate the multiple causes of delay.

Health care’s problem solving toolkit

health care, we rely on evidence-based methods for solving problems. Root Cause Analysis (RCA) is a collective term that describes a wide range of approaches used to investigate a problem and its causes.

When we talk about a problem we often refer to its impact. We know how it impacts us personally, our system, patients, and/or customers. But our experience of the problem—it’s impact—doesn’t really tell us why it’s happening—the cause. If we don’t know the cause, we won’t be able to prevent it from happening again. Investigating a problem and its causes can result in long-term solutions, which is an essential part of our patient safety journey .

Fishbone Diagram

Fishbone thumb.

Download the Fishbone Diagram Quick Tips here .

Download a U of U Health PowerPoint Fishbone Diagram template here .

An easy to use tool for conducting a root cause analysis

What it is: The fishbone diagram Also referred to as “Ishikawa cause and effect” after Japanese founder and quality control expert Kaoru Ishikawa. is a tool to organize ideas and theories about what causes a problem or an event.

How it works: Teams work together to brainstorm and identify potential causes and group them into several categories to help highlight potential issues. Frequently used categories include people (or patients/providers/stakeholders), culture, method (or process), technology, equipment, supplies, etc. (customize categories as needed).

Follow Four Steps to Fishbone:

Fishbone steps4 01.

Three Tips for facilitating a fishbone

A successful fishbone diagram is led by a facilitator—one individual on the team who’s job is to remain impartial to the discussion, write down the identified causes on the fishbone diagram, and let the participant discussion flow freely.

Here are the top three tips for leading a successful fishbone:

#1: Help the team focus on identifying causes, not solutions.  It’s common for people to brainstorm solutions (how to fix), rather than causes (what to fix). Simply acknowledge any comments by writing them to the side (don’t disregard any comments, it’s demoralizing) and help everyone remember the difference between the two. For example, if the problem is delays at patient check-in, “add front desk personnel” offers a solution (how to fix). Whereas “front desk is short-staffed” focuses on a potential cause (what to fix).

#2: The cause is more important than the category.  People often get confused or stuck on what category a cause should go into. As a facilitator, remind the participants that listing the cause is more important than where it goes. For example, “front desk is short-staffed” could be placed under the category of People, but also Culture.

Sometimes a main category can become too big. A common one is to start with the “People” category, but by the time 10 causes are identified under that category, you may choose to split it, for example as: “Nurses” and “Doctors.”

#3: Keep brainstorming until the ideas run out.  People are often unsure of how many causes to identify. As long as the discussion keeps going, people are still brainstorming. When the silence starts to creep in, you have your first clue that perhaps you have enough to get started. 

As facilitator, you will write the statements as they come out during the discussion. If you have to paraphrase what was said (because of space requirements, complexity, etc.) confirm with the group that what you wrote was what was said.

See it applied

Returning to our introduction case study, the Oncology residents first mapped the process to identify where it was breaking down. They then brainstormed as a team and came up with the following categories and causes.

HCI Huntsman Clinic Check in to Provider Page Process Fishbone Diagram

fishbone full

Oncology team: Lindsay Burt, MD; Chris Baker, MD; Chris Weil, MD; Josh Gruhl, MD; Matthew arsons, MD; Ryan Hutten, MD; Ryan Kraus, MD; Timothy Griffith MD

Solving the age-old problems of health care doesn’t require more solutions. It requires better understanding of problems. The oncology residents found the fishbone a useful tool to illustrate how many variables contribute to a seemingly simple question: “why don’t we get paged sooner?” By breaking the problem into a series of categorized causes, the team identified overlap between workflows. Using this information, the team is now prioritizing causes from high-to-low effort to begin making improvements.

*Originally published Janurary 2021

Why do some organizations thrive during a crisis while others flounder? Iona Thraen, director of patient safety, joined forces with her ARUP Laboratory colleagues to learn how the world-renowned national reference lab adapted to the pandemic. Leaders created a culture of safety by putting innovation, learning, and patient-centered care at the heart of all their efforts.

Finding evidence to change the status quo isn’t easy; thinking about evidence in terms of how it persuades—whether subjective or objective—can make it easier. Plastic surgery resident Dino Maglić and his colleagues followed their guts and saved money by improving the laceration trays used to treat patients in the emergency department.

Every summer, senior value engineer Cindy Spangler stocks our offices with an abundance of tomatoes, zucchini, and squash. We asked her to share how improvement thinking influences her gardening. Turns out, there are parallels–learn from others, stick to your scope, and learn from the mistakes.

Subscribe to our newsletter

Receive the latest insights in health care equity, improvement, leadership, resilience, and more..

Contact the Accelerate Team

50 North Medical Drive   |   Salt Lake City, Utah 84132   |   801-587-2157

• Get started Get started for free

Figma design

Design and prototype in one place

Collaborate with a digital whiteboard

Translate designs into code

Get the desktop, mobile, and font installer apps

See the latest features and releases

• Prototyping
• Design systems
• Wireframing
• Online whiteboard
• Team meetings
• Strategic planning
• Brainstorming
• Diagramming
• Product development
• Web development
• Design handoff
• Product managers

Organizations

Config 2024

Register to attend in person or online — June 26–27

Creator fund

Build and sell what you love

User groups

Join a local Friends of Figma group

Learn best practices at virtual events

Customer stories

Read about leading product teams

Stories about bringing new ideas to life

Get started

• Developer docs
• Best practices
• Reports & insights
• Resource library
• Help center

What is a fishbone diagram—and what can it do for you?

Any bump in the design process can be a learning opportunity. Maybe an unexpected setback is delaying product development, or you're worried your next release may not get rave customer reviews. Whatever issue you’re facing, the fishbone diagram is a simple and effective brainstorming tool that can help you solve problems—and keep them from cropping up in the first place.

Read on to learn more about:

• What a fishbone diagram is
• How a fishbone diagram can help you solve problems
• 5 steps to create a fishbone diagram—and FigJam tools that make it easy

Create your fishbone diagram with FigJam

Get started with FigJam's free fishbone diagram template today.

What’s a fishbone diagram?

A fishbone diagram is also known as the cause-and-effect diagram, because it highlights the causes of a current or potential problem, or any other deviation from your team’s standard workflow.  Companies use fishbone diagrams to help streamline processes, boost customer satisfaction, and drive better business outcomes.

The diagram actually looks like a fish skeleton. A horizontal arrow represents the fish spine and points to the problem (or effect), which is the head of the fish. Shorter arrows act as the fish ribs, branching out to expose the problem’s causes.

How the fishbone method solves problems

The fishbone method of analysis helps teams go deep with their problem-solving, uncovering key factors teams can target and troubleshoot. When used effectively, a fishbone diagram can help you 1 :

• Easily identify and categorize the causes —big and small—of a particular problem in a highly visual way.
• Develop actionable solutions more quickly by providing a structured yet flexible approach to address problems.
• Promote a more effective work environment by fostering better collaboration and communication across teams.
• Continuously improve your product or process by documenting root causes to avoid repeating the same mistakes in the future.

5 steps to create a fishbone diagram

Build your own fishbone diagram in five steps 2 :

Step 1: Define the problem.

Create a clear, concise problem statement. This should address a known issue or one you’re trying to prevent, such as “customer satisfaction rate for our app has fallen 20%.” Use FigJam’s online whiteboard to brainstorm and agree on a problem statement. Or try FigJam’s fishbone diagram template .

Step 2: Label potential issues.

You can use the six labels in the classic fishbone diagram (see sidebar), or create your own set of categories to suit the product and problem facing your team. For example, Mazda chose styling, touch, cornering, driving, listening, and braking as key issues to address in developing the MX5 Miata sports car.

Step 3: Brainstorm all possible causes.

Ask why this problem occurred, and organize possible causes by category. For example, under the people category, you might list causes for a drop in customer satisfaction as staff burnout, lack of training, or employee turnover. Some causes may fit under more than one category.

Step 4: Add more detail to your fishbone analysis.

Keep asking why to further identify sub-causes that contribute to the problem. FigJam’s 5 whys template will help you dig deeper.

Step 5: Review each cause and develop action items.

Work with your team to create a list of action items that will help solve the problem. Invite your team to check the finished diagram, making sure no detail has been overlooked (see sidebar).

Creative examples of fishbone diagrams

Popularized in Japan’s manufacturing industry in the 1960s, the fishbone or Ishikawa diagram is now industry-standard in multiple fields. From healthcare and higher education to retail and high tech, fishbone diagrams  help teams improve and innovate.

For inspiration, consider these creative examples from a range of industries:

• Product defects fishbone diagram , Journal of Minerals and Materials Characterization and Engineering
• Carver County Public Health fishbone diagram , Minnesota Department of Health
• Cause and effect of blurry photos , Michigan State University Extension
• Bad coffee fishbone diagram , Kaizen Consulting Group

The classic 6-rib fishbone diagram

A typical fishbone diagram includes six ribs , each labeled with a potential issue to address. This could include:

• People. Evaluate everyone involved in the process, including their skill level, training, and performance.
• Machines. Examine equipment and any maintenance or upgrades required to solve a problem.
• Materials. Assess the raw and finished materials used. Do they meet expectations?
• Environment. Consider external factors such as bad weather or safety issues that can affect the development cycle.
• Method. Audit your team’s process—the number of steps, their complexity, and any potential bottlenecks.
• Measurement. Review the way your process is measured, controlled, and monitored.

Fishbone analysis pitfalls to avoid

The simplicity of a fishbone diagram makes it easy to use and understand, but it can also make it harder to prioritize tasks. Of all the causes identified in a fishbone diagram, a problem’s main causes aren’t necessarily ranked ahead of minor ones. It’s up to you and your team to prioritize issues that will have the most impact versus those that won’t.

Fishbone diagrams can sometimes reflect human biases, so you'll need to work to maintain objectivity. Gather input from key players across your company to ensure your fishbone analysis is valid and complete.

Bone up on your fishbone diagrams with FigJam

Problem-solving is a team sport. Work together to zero in on root causes using FigJam’s online collaborative whiteboard , then organize them with FigJam’s ready-made fishbone diagram template . If you’d rather make one from scratch, use FigJam’s free diagramming tools to:

• Produce an easy-to-understand visual that clearly shows cause-and-effect relationships.
• Collaborate in real time with key stakeholders to make sure the causes included are accurate and actionable.
• Construct a polished diagram that supports your brand and is presentation-ready.

Want to see an example of a fishbone diagram created in FigJam? Check out these inspiring fishbone diagrams shared by the Figma community .

Now you’ve got what you need to solve problems—and prevent them, too.

Go to next section

[1] https://6sigma.com/benefits-of-using-the-fishbone-diagram/

[2] https://www.ahrq.gov/sites/default/files/wysiwyg/ncepcr/resources/job-aid-5-whys.pdf

Keep reading

How to create a swimlane diagram

Swimlane diagrams give flowcharts an extra-informative superpower.

How to create a flow chart

Having a flow chart can help visually represent actions or people in a complex situation.

What is a UML diagram

UML diagrams can help you plan complex systems and processes.

What is a Fishbone diagram?

Table of Contents

Fishbone diagrams explained.

A fishbone diagram (also known as an Ishikawa fishbone diagram) is an effective problem-solving tool. Instead of focusing on a quick fix, creating a fishbone diagram helps to identify the root cause of a problem and find a long-term solution.

As a type of cause and effect diagram , the “fishbone” name comes from the diagram’s resemblance to a fish skeleton. A fishbone diagram consists of three main categories:

There’s a fish head at the head of the diagram, where you’ll outline the problem you’re trying to solve. The rest of the diagram branches out from here.

The spine stems from the head of the diagram (the problem statement), providing the outline of the fish. At the end of each spinal bone is a category that needs to be considered as part of the problem-solving process.

Branching out from each spinal bone, you’ll see a smaller rib bone. This is where the possible causes will sit to help you pinpoint the potential cause of the problem.

Benefits of fishbone diagrams

Fishbone diagrams are useful tools for improving existing processes and pinpointing causes of issues. Take a look at some benefits of performing a fishbone diagram root cause analysis:

Easily find the root cause of a problem

A fishbone diagram is a visual tool that adds structure and clarity to problem-solving. It indicates the problem and its possible causes in a single location, making it easier for teams to conduct a root cause analysis .

Prevent further problems

By finding the root cause of the problem, you fix the problem at its source and mitigate future issues. As a result, you’re far more likely to prevent the same (or similar) problems from cropping up in the future.

Collaborate with your team

A fishbone diagram is a great way to work with your team to brainstorm solutions . It’s a collaborative diagram, encouraging teams to review all the available information and discuss the best course of action.

If you’re part of a remote or hybrid team, an online platform like Miro allows you to collaborate with your team, no matter where they work. Simply share the diagram and hop on a video chat, and you can perform your root cause analysis virtually.

Example of a fishbone diagram

To see a fishbone diagram in action, look at this CEDAC Template from NEXT LEVEL Partners.

CEDAC is an acronym for Cause and Effect Diagram with the Addition of Cards. The diagram contains issues on the left-hand side of the ribs and solutions on the right-hand side.

Its inventor, Ryuji Fukuda, created CEDAC so that teams can delve deeper into their problem-solving analyses. By adding cards to the diagram, teams have a way of questioning existing information and suggesting new ideas. As a result, they’ll gain a deeper understanding of their problems and how to solve them.

Here are some of the common areas where the CEDAC model can be helpful:

Product development

Visualize issues with product development using the CEDAC diagram. Collaborate with the product team to identify the cause of the problem and use cards to identify the best possible solution.

Software features

Effectively allocate resources based on team structures and capabilities. Understand the most critical problems to solve and how they map together.

Product design

Define failures or problems with your product design, and identify effective solutions. Using the diagram’s cards, product designers can generate new and creative solutions to improve the design.

Internal processes

Pinpoint bottlenecks and figure out how to streamline and improve your business processes. Encourage team members to join in the discussion and make suggestions for improving the process going forward.

When to use a fishbone diagram

Take a look at some of the different instances when using a fishbone diagram can be useful for you and your team.

1. To analyze a problem statement

If you have a clear problem statement for your business, a fishbone diagram is a great way to analyze it in detail. You can see the problem’s culprit and decide how to fix the issue.

2. To brainstorm the causes of the problem

Also known as root cause analysis, a fishbone diagram allows you to discuss the potential causes of a problem. It’s the perfect opportunity to host a brainstorming session to identify pressing concerns and work through possible solutions.

3. To analyze a new product design

Use a fishbone diagram to map your new product design and visualize any potential hurdles before they come your way. As a result, you can put preventative measures in place before going live.

4. To improve your processes

If you’re struggling to streamline your processes and inefficiencies, a fishbone diagram can help. Use a fishbone diagram to pinpoint the troublesome areas of your process and find the cause of a problem. From there, you can determine exactly how to fix it.

5. For quality improvement

Use a fishbone diagram to visualize how and where you can improve to offer your customers a higher-quality experience. For example, you might want to improve the quality of your customer service. In this case, you can use the diagram to find areas for improvement in your existing processes.

How to make a fishbone diagram

Follow these simple steps to create an effective fishbone diagram:

1. Select the Fishbone Diagram Template

While you can always build your own diagram from scratch, you can also get a headstart by selecting this Fishbone Diagram Template . It’s free and easy to use, so you can start mapping your diagram immediately.

2. Outline your problem statement

When your diagram is ready to use, start by defining the problem. Otherwise known as a problem statement, this will sit at the head of the diagram. This must be as clear and concise as possible to find the right solution.

For example, in the diagram below, the main problem is that “40% of users cancel the subscription in the first month.” This statement clearly describes the problem and offers a solid starting point for finding a solution. Now, let’s consider how this would work if the statement were written differently — for example, “to increase customer retention.”

This statement is pretty vague, and there’s a lot of room for interpretation. Instead of focusing specifically on how to keep existing customers after the first month, teams might explore other avenues that won’t necessarily solve the actual problem.

The problem statement doesn’t have to be long and detailed. In fact, you should keep it short — ideally, no longer than a sentence. That way, it’ll be easy for your team to see the problem and won’t overcrowd the diagram. But the problem statement should always be clear and concise, leaving no room for interpretation.

If you’re new to problem statements or want a framework to guide you, look at Prime Motive’s Problem Framing Workshop Template .

3. Pinpoint your root causes

With your problem statement in place, you can now branch out and start to pinpoint the possible causes of the problem.

The specific causes will depend on what your problem statement is. For example, if your problem statement is related to product design, your root causes could include the following:

These are just a few examples. In your diagram, you might find that you have more or fewer root causes. With an intuitive platform like Miro, it’s easy to add or remove boxes based on how many you need.

When adding causes to your diagram, those with the biggest impact should be closest to the problem. The farther away a cause is from the head of the diagram, the less influence it has on the problem.

4. Identify individual causes

You can now identify the individual elements that contribute to the overall cause. These are the bones of the fish.

Let’s use an example to demonstrate how this works. Imagine that one of your root causes is “Equipment.” Here are some of the individual causes that might sit under this area:

You are using outdated and inefficient equipment

It’s expensive to replace existing equipment

There aren’t enough employees who know how to use the equipment

All of these elements could contribute to the problem you’re facing, but it’s up to you and your team to pinpoint the key elements at the root of the problem. Review all this information with your team, and you’ll be able to see which problem is most likely to have a long-term solution.

If you’re unsure how to identify the individual causes, look at the 5 Whys framework . It’s a simple brainstorming tool that helps teams explore the reasons behind a potential problem.

5. Create a plan of action

After working with your team to find the root cause of the problem, you can create an action plan for improvements. This involves mapping out the steps you need to take to solve your problem and how you’ll measure success (we suggest using the SMART Goals framework for this).

During this stage, be sure to focus on how to make lasting improvements. Don’t lose sight of the bigger picture in favor of a quick fix. The purpose of the fishbone diagram is to implement a long-lasting solution to your problem, so keep this in mind when creating your plan of action for the future.

Fishbone diagram categories: the 6Ms of production

The fishbone diagram is used across various industries, but the original diagram was created to improve the manufacturing process. The six methods (6Ms) of production come from this original diagram, and engineers and designers would use this structure to cover all their bases.

The 6Ms of production are as follows:

1. Manpower

The functional activity involved in designing and delivering a product.

The production process and any other processes that contribute to the delivery of the final product.

Any systems, tools, or equipment used in manufacturing.

4. Material

The raw materials and components needed to create the end product.

5. Milieu (or Mother Nature)

Any environmental factors, such as weather, floods, or fire. Although most milieu factors can’t be controlled, there are some instances where businesses can put preventative measures in place to mitigate problems.

6. Measurement

The physical measurements (volume, distance, temperature, and so on) of a product, machine, or workspace.

The 6Ms are only relevant if you’re using the fishbone diagram to improve a manufacturing or production process. If you’re using the diagram for any other purpose, there’s no need to follow this structure.

Discover more

How to build a fishbone diagram

What is a cause and effect diagram

What is root cause analysis?

What is the 5 Whys Framework?

5 Whys: Examples, explanations, and how to find the causes of problems

Get on board in seconds

Join thousands of teams using Miro to do their best work yet.

How to Use Fishbone Diagram for Problem Solving

Fishbone diagram is a problem-solving tool, used in literal terms like a fishbone. It is also known as a cause and effect diagram. The mechanism is to specifically identify the cause and effect of any business or project problem.

A fishbone diagram can help define potential reasons for an issue. This article will dive into understanding the core principles of the fishbone diagram problem solving as a tool.

In 1943 at Tokyo University, Kaoru Ishikawa created the "Fishbone Diagram." Fishbone diagrams can also be called diagrams of "cause and effect." The fishbone diagram problem solving tool is a perfect tool to dig through an issue when we try to assess the root cause and find a solution effectively.

It offers a mechanism for explicitly identifying the "effect" and then brings you to think about the potential triggers, based on typical manufacturing problems. The fishbone diagram problem solving is a basic model that makes it easy to grasp swift and efficient root causes to implement corrective behavior.

It reflects the question or impact at the fish's head or mouth. Possible contributing factors under separate causal groups are identified on the smaller "bones." A fishbone diagram can help define potential reasons for an issue that would otherwise not be discussed by encouraging the team to look through the definitions and discuss alternate reasons.

Source: EdrawMind

1.1 Why Use Fishbone Diagram for Problem Solving

The fishbone diagram makes you consider more when solving specific problems. During a brainstorming activity, various groups inspire thoughts from different areas.

The fishbone diagram brings order to the process of cause and effect . It's easy for participants to understand the main problems or issues and focus on the question across different potential triggers.

The fishbone diagram helps distinguish the causes and reasons for a problem and lets people intuitively figure out the solutions.

1.2 The Usage of Fishbone Diagram

The fishbone diagram problem solving method can be used when trying to fix problems or discover the root cause of an issue or problem, which helps you to see below the surface, and dive deeper into the real problem.

Here are several typical fishbone diagram problem solving applications:

• Manufacturing: ,nbsp;Uncover the root cause of a manufacturing problem by brainstorming and rating the likelihood and effect of all factors affecting the manufacturing cycle;
• Marketing or Product Marketing: ,nbsp;Identify the possible factors that may impede your company's popularity in the marketplace by investigating all the places that affect your product acceptance;
• Service: ,nbsp;Uncover the root cause of a business issue by brainstorming, and rate the probability and effect of all factors impacting the service delivery process.

There are 7 steps lead you to use fishbone diagram for problem solving:

• Explain the agenda behind the diagram

Let your team members know that the diagram can help you see different fields or possible areas that might lead to a solution to your current business problem.

• Draw diagrams

Draw the pattern or shape on your whiteboard, or use a software diagramming tool to ease accessibility. If you need remote attendants to do this exercise, you can quickly build it in EdrawMind and display your computer.

• Determine a simple statement on an issue

Write down statements at the top of your page or above where you will build the diagram., which means everyone has the same idea of the issue you are concerned with.

• Select what categories to use

Categories are discussed in more detail below. For example, you can add Policies, Methods, Personnel, and Software categories.

• Identify potential causes within each category of your problem

Team members may trigger brainstorming or contribute factors that fall into this category. You can either go by category or only come up with ideas and determine which type they fit.

• Go a step deeper to define sub-causes for any cause in the category

If you decide whether something can or will break down to smaller points, build divisions from the critical point.

Team members study the diagram to determine the most relevant focus points. If you are trying to take this a step forward and fix the root cause, it helps define where you're trying to benefit your initiative. You can't solve all the root factors at once, and some can get more significant payoff than others. Check the diagram for an evaluation of where the concentration of the team is best.

• Record results

You bring the work in. Capture, and log your work. You will need to return to it later, so you don't want to miss the importance of the exercise that you got.

There are several tips that should be considered when using the fishbone diagram for solving problems:

• Using the fishbone diagram tool to keep the team focused not on signs, but the problem's causes;
• Make sure you leave ample room in the diagram between the main groups to add minor specific pointers later;
• Try making team members write every cause on sticky notes while you're brainstorming causes, moving around the community asking each person about a particular reason. Continue to go through the loops, have more pointers before all suggestions have been eliminated;
• Encourage each person to join in the brainstorming exercise and voice their own opinions;
• Remember that the strategy of "five-whys" is often used in combination with the fishbone diagram.

While it takes time to create a fishbone diagram , it will help you and your team define the real causes and encourage you to strengthen the process and make permanent improvements.

Regardless, whether you are using the graphical or indented fishbone hierarchy, this process optimization method will significantly help you understand the factors involved in a process. The root causes of the event are the underlying process and system issues, which allowed the contribution. Hence fishbone diagram , the problem-solving tool, is extremely crucial when discussing strategies to deal with problems.

EdrawMind is an easy-to-use, flexible mind mapping tool designed to help you generate modern, fresh visuals and mind maps. By combining the bullet points into a mind map on a project, EdrawMind lets you organize the thoughts or concepts and create essential strategies.

How to Motivate Yourself to Study

Meeting Management: How to Run a Meeting

How to Create a Fishbone Diagram on PowerPoint

How to Make Good Use of Mind Map for Students

Complete Beginner's Guide to Project Planning

How to Be Productive at Home: 7 Work-from-Home Tips

The Fishbone Analysis Tool (Ishikawa Diagram): A Simple Intro

The fishbone analysis tool is a visual method used to help capture and understand various things including the root causes to a problem. Completed diagrams look like a fish skeleton. Summary by The World of Work Project

Fishbone Analysis

Fishbone analysis diagrams are also known as Ishikawa diagrams. They are a visual tool that helps individuals and teams captured and understand the root causes to a specific problem.

The problem statement that is being considered is captured in the fish’s head. The specific root-causes that contribute to the problem are captured along the fish’s fins (or rib bones). The major causes of the problem are captured at the ends of the fins.

This approach produces comprehensive visualizations of problems which help with the solution process. When designing solutions, it’s important to ensure that any proposed solution addresses the major root causes that have been identified.

Using it in Practice

Fishbone analysis is often part of a more comprehensive approach to team problem solving and is often combined with silent brainstorming .

The standard approach that we would use around a fishbone analysis forms part of a facilitated team problem solving approach, using the A3 Thinking method . This is normally completed using post-it notes initially, and is only captured in fishbone diagram at a later stage. The process is as follows:

• Firstly, have a team silently brainstorm the root causes of a chosen problem statement using the 5 whys approach to ensure depth.
• Secondly, have the team group their individual root causes into themes.
• Thirdly, have the team review the grouped thematic areas and, if happy with them, name them. These names then become the major-causes to the identified problem.
• Fourthly, review the root-causes and major causes, checking them for completeness against an appropriate list of potential major-causes.
• Finally, progress to the solution design phase.

Major-causes: 3 Common Groups

It’s important to understand the common major-causes which can affect a specific type of problem. With these in mind it’s possible to check the completeness of the root-causes you’ve identified.

For example, if you know that a common major-cause is “people capability” and you’ve identified no root-causes of this nature, you can go back and spend further time identifying appropriate root-causes to your problem.

By doing this you can ensure that you’ve identified all of the appropriate root causes, and are thus in a position to identify a better solution to your problem.

Below, we consider three groups of major-causes that you may wish to use to check your root-causes for completeness. Each group is useful in different circumstances. More groups are available, and you can always create your own group which is appropriate for your specific circumstances.

The PPPS Major-causes

PPPC stands for people, process, platform and culture. These are an excellent set of common major-causes to consider for any problem in an office or a professional-services working environment. Most problems in this environment have root causes within all four of these major-causes.

The 5 Ms Major-causes

The 5 Ms are: machine, method, material, man and measurement. These major causes are useful for consideration in the manufacturing sector where you would expect to potentially find root-causes in relation to all of them.

The 5 Ps Major-causes

The 5 Ps are: product, price, promotion, place, people. These are simply the 5 Ps of marketing (which we’ve yet to write about), converted into potential major-causes. These are appropriate major-causes to consider in relation to a product marketing problem.

Want to be a better manager?

Every year we run an open cohort of our Connected Management programme for those working in small organisations or organisations that are not able to fund personal and professional development. The 10 session programme is £1100 per person with discounts of up to 40% for self-funders and non-profits.

In 2024, we have a cohort on Wednesday 3.30pm UK time and Thursdays 9am UK time from April 17/18. It comprises 10 online live workshops with two great facilitators and access to a bank of support materials. Learn more about the programme by clicking below.

Learning More

Thinking about what we do from different perspectives and with others is very helpful for decision making. Tools like the reframing matrix process or hackathons can help us do this.

Part of the reason we’re not great at problem solving is that we all have thinking habits and cognitive biases that restrict our creativity. In particular, these decision making biases often lead us towards bad (or irrational) decisions. And sometimes we make decisions just because ISLAGIATT …

Similarly, Drilling into issues with the 5 Whys helps us understand root causes more and creating an ease/benefit matrix helps us decide what to focus on in the first place. When we are actually working on things like this in groups it’s useful to use techniques like silent brainstorming to get the best results.

To learn more about creativity, innovation and problem solving, you might enjoy the third of our three podcasts specifically on these topics. It focuses mainly on cognitive processes:

The World of Work Project View

Fishbone analysis is a helpful tool. It’s a useful way to visualize, share, track and analyze root causes to a specific problem. The approach of comparing root causes to a list of common major-causes for that kind of problem is also very helpful.

In our view though, the real magic comes from getting the right people in the room and leading an effective root-cause ideation / brainstorming activity. In many ways this is more important than how you visualize the root-causes that you capture.

Our Podcast . 

Our Podcast is a great way to learn more about hundreds of fascinating topics from around the world of work.

In this instance, most of our content has come from our working experience. The original source of this model though is by Kaoru Ishikawa and you can read more in his book: “Introduction to Quality Control” .

The World of Work Project: The Fishbone Analysis Tool (Ishikawa Diagram): A Simple Intro

We’re a small organization who know we make mistakes and want to improve them. Please contact us with any feedback you have on this post. We’ll usually reply within 72 hours. 

Share This Story, Choose Your Platform!

Related posts.

Predictive Analytics In The World Of Work

The Foursquare Ethical Decision Model: A Simple Summary

The ISLAGIATT Decision Making Process

The Reframing Matrix Process: A Simple Way To Improve Creativity

Bounded Rationality: A Simple Summary

Dual Process Theory: A Simple Summary

Privacy overview.

In this online seminar, we explore two key factors that shape our performance and experience at work: Trust and Social Threats. We'll explain what they are, discuss how to build trust, share the domains of social threat and share hints and tips for managing both in the workplace.

In this online seminar, we explore the thorny issue of managing the demands on our time. In many workplaces it feels like there's a potentially infinite amount of work. To succeed, we need to learn to prioritize, say no when appropriate and manage our own boundaries. This seminar will explore these challenges and share insights on how we can all improve.

In 2012 Google decided to analyse their teams to discover what makes an effective team, why some teams are so successful, and some less so. What did they discover? Amongst other things, that Psychological Safety is a key differentiator for high performing teams. In this seminar we explain what Psychological Safety is, why it matters and how to increase it in your teams.

Subscribe For Latest Updates

Nice to see you again :)

If you'd like to learn more about us and what we do, you can join thousands of members of the World of Work community around the globe in receiving our occasional newsletter, the WOW Mail. In it, we'll let you know what we're up to and share hints and tips. 

After submitting this form, you'll receive an email asking you to confirm your registration. Click the button in that email to finalize your subscription. Your email provider might filter it into your junk folder, so please check there if you don't see it your main folder!

I agree to receive your newsletters and accept the data privacy statement.

We use Sendinblue as our marketing platform. By Clicking below to submit this form, you acknowledge that the information you provided will be transferred to Sendinblue for processing in accordance with their terms of use

In this online seminar, our special guest, Dr. Charlotte Rae (Sussex: Psychology, Neuroscience) shares her findings on the impact of moving to a four-day week on our performance, wellbeing and biology, and tips on how to implement a four day week well in your organization.

Part of our popular lunchtime seminar programme

How it works

For Business

Join Mind Tools

Article • 7 min read

Cause and Effect Analysis

Identifying the likely causes of problems.

By the Mind Tools Content Team

(Also known as Cause and Effect Diagrams, Fishbone Diagrams, Ishikawa Diagrams, Herringbone Diagrams, and Fishikawa Diagrams.)

When you have a serious problem, it's important to explore all of the things that could cause it, before you start to think about a solution.

That way you can solve the problem completely, first time round, rather than just addressing part of it and having the problem run on and on.

Cause and Effect Analysis gives you a useful way of doing this. This diagram-based technique, which combines Brainstorming with a type of Mind Map , pushes you to consider all possible causes of a problem, rather than just the ones that are most obvious.

Click here to view a transcript of this video.

About the Tool

Cause and Effect Analysis was devised by professor Kaoru Ishikawa, a pioneer of quality management, in the 1960s. The technique was then published in his 1990 book, " Introduction to Quality Control ." [1]

The diagrams that you create with are known as Ishikawa Diagrams or Fishbone Diagrams (because a completed diagram can look like the skeleton of a fish).

Although it was originally developed as a quality control tool, you can use the technique just as well in other ways. For instance, you can use it to:

• Discover the root cause of a problem.
• Uncover bottlenecks in your processes.
• Identify where and why a process isn't working.

How to Use the Tool

Follow these steps to solve a problem with Cause and Effect Analysis:

Step 1: Identify the Problem

First, write down the exact problem you face. Where appropriate, identify who is involved, what the problem is, and when and where it occurs.

Then, write the problem in a box on the left-hand side of a large sheet of paper, and draw a line across the paper horizontally from the box. This arrangement, looking like the head and spine of a fish, gives you space to develop ideas.

In this simple example, a manager is having problems with an uncooperative branch office.

Figure 1 – Cause and Effect Analysis Example Step 1

(Click image to view full size.)

Some people prefer to write the problem on the right-hand side of the piece of paper, and develop ideas in the space to the left. Use whichever approach you feel most comfortable with.

It's important to define your problem correctly. CATWOE can help you do this – this asks you to look at the problem from the perspective of Customers, Actors in the process, the Transformation process, the overall World view, the process Owner, and Environmental constraints.

By considering all of these, you can develop a comprehensive understanding of the problem.

Step 2: Work Out the Major Factors Involved

Next, identify the factors that may be part of the problem. These may be systems, equipment, materials, external forces, people involved with the problem, and so on.

Try to draw out as many of these as possible. As a starting point, you can use models such as the McKinsey 7S Framework (which offers you Strategy, Structure, Systems, Shared values, Skills, Style and Staff as factors that you can consider) or the 4Ps of Marketing (which offers Product, Place, Price, and Promotion as possible factors).

Brainstorm any other factors that may affect the situation.

Then draw a line off the "spine" of the diagram for each factor, and label each line.

The manager identifies the following factors, and adds these to his diagram:

Figure 2 – Cause and Effect Analysis Example Step 2

Step 3: Identify Possible Causes

Now, for each of the factors you considered in step 2, brainstorm possible causes of the problem that may be related to the factor.

Show these possible causes as shorter lines coming off the "bones" of the diagram. Where a cause is large or complex, then it may be best to break it down into sub-causes. Show these as lines coming off each cause line.

For each of the factors he identified in step 2, the manager brainstorms possible causes of the problem, and adds these to his diagram, as shown in figure 3.

Figure 3 – Cause and Effect Analysis Example Step 3

Step 4: Analyze Your Diagram

By this stage you should have a diagram showing all of the possible causes of the problem that you can think of.

Depending on the complexity and importance of the problem, you can now investigate the most likely causes further. This may involve setting up investigations, carrying out surveys, and so on. These will be designed to test which of these possible causes is actually contributing to the problem.

The manager has now finished his analysis. If he hadn't looked at the problem this way, he might have dealt with it by assuming that people in the branch office were "being difficult."

Instead he thinks that the best approach is to arrange a meeting with the Branch Manager. This would allow him to brief the manager fully on the new strategy, and talk through any problems that she may be experiencing.

A useful way to use this technique with a team is to write all of the possible causes of the problem down on sticky notes. You can then group similar ones together on the diagram.

This approach is sometimes called CEDAC (Cause and Effect Diagram with Additional Cards) and was developed by Dr. Ryuji Fukuda, a Japanese expert on continuous improvement.

Professor Kaoru Ishikawa created Cause and Effect Analysis in the 1960s. The technique uses a diagram-based approach for thinking through all of the possible causes of a problem. This helps you to carry out a thorough analysis of the situation.

There are four steps to using the tool.

• Identify the problem.
• Work out the major factors involved.
• Identify possible causes.
• Analyze your diagram.

You'll find this method is particularly useful when you're trying to solve complicated problems.

[1] Ishikawa, K (1990).  'Introduction to Quality Control ,' Tokyo: 3A Corporation.

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

Solving problems with cause and effect analysis.

How to Use Cause and Effect Diagrams

Problem Solving

Add comment

Comments (0)

Be the first to comment!

Get 30% off your first year of Mind Tools

Great teams begin with empowered leaders. Our tools and resources offer the support to let you flourish into leadership. Join today!

Sign-up to our newsletter

Subscribing to the Mind Tools newsletter will keep you up-to-date with our latest updates and newest resources.

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Most Popular

Latest Updates

Tips for Dealing with Customers Effectively

Pain Points Podcast - Procrastination

Mind Tools Store

About Mind Tools Content

Discover something new today

Pain points podcast - starting a new job.

How to Hit the Ground Running!

Ten Dos and Don'ts of Career Conversations

How to talk to team members about their career aspirations.

How Emotionally Intelligent Are You?

Boosting Your People Skills

Self-Assessment

What's Your Leadership Style?

Learn About the Strengths and Weaknesses of the Way You Like to Lead

Recommended for you

Menlo innovations infographic.

Infographic Transcript

Infographic

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Team Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Decision Making

Member Podcast

• Memberships

Fishbone Diagram by Kaoru Ishikawa explained

Fishbone Diagram: this article explains the Fishbone Diagram or Ishikawa Diagram by Kaoru Ishikawa in a practical way. After reading you will understand the basics of this powerful problem solving tool and Cause and Effect Analysis . This article also contains a downloadable and editable Fishbone Diagram template. Enjoy reading!

What is a Fishbone Diagram / Ishikawa Diagram?

Problems are the consequence of one or more root causes. By finding and removing the root causes, problems can be solved. Brainstorming sessions could identify possible root causes, but this is not a systematic manner.

By using a this diagram, it is possible to perform an extensive cause and effect diagram analysis and identify the root causes of problems. A frequently used alternative to this diagram is mind mapping.

This root cause analysis method was developed by Kaoru Ishikawa , a Japanese scientist, who discovered through his work at Kawasaki Heavy Industries , that a large number of contributing factors could influence a work process. Therefore, it is advised to use this method with the people who have the most knowledge about the work process. Include people like team members and managers.

To obtain insight into these factors, he designed a simple graphical tool, in which the potential root causes are represented in an orderly fashion.

As this root cause analysis model resembles a fishbone, the Ishikawa diagram is, also called the Cause and Effect Analysis . Actually, the diagram was intended for production processes and its accompanying quality control. Today, the Ishikawa diagram is also used in other sectors.

Create a Fishbone Diagram

Figure 1 – an example of a Fishbone Diagram

This concerns all causes that are created by human actions; is there good communication, do people understand their assignments, are the employees sufficiently involved, experienced and trained, etc.?

This concerns causes related to the functioning of machines, tools, installations and computers; have the correct machines been used, are the machines safe enough, do the machines meet the requirements, are they reliable, etc.?

There may be problems with the materials, raw materials and consumables and semi-finished products; what is the quality, how much do we need, are the materials resistant to external influences, how long will they last, etc.?

This category investigates whether possible causes can be found in the work method; are the work processes adequate; how are the cooperative arrangements organized, how do employees and departments communicate with each other, etc.?

Details of the Fishbone Diagram

The Fishbone Diagram takes shape by following a number of steps. It starts with a large piece of paper on which a fishbone is drawn.

From there the following steps come up for discussion:

• The problem, in which the analysis is to be performed, is written at the top of the paper.
• Each participant mentions one possible cause for the problem and states in which category the problem belongs. No comments may be made on each other’s causes. All the listed causes are included in the Fishbone Diagram.
• The participants also mention possible secondary causes. These secondary causes are entered as branches in the Fishbone Diagram.
• This process is continued until no more possible causes are mentioned.
• The diagram is critically studied by all participants. They will see whether the possible causes have been entered in the right category and / or whether certain causes are related or derived from other causes.
• There is a vote on the most likely causes. The causes with the most votes will be turned into a “top 3” of possible causes. These three causes are circled. The causes without a vote are deleted.
• The priority order is determined from the “top 3” causes. The possible cause with the highest priority will be investigated further and then dealt with. After this the second and third causes will be addressed.

The diagram is an excellent root cause analysis and problem solving tool that can be used in any sector. As sectors can differ tremendously from one another it is possible to extend or change the root cause categories.

A technical company many want to add an IT category to the category “machine”. An advertising agency can insert a “creativity” category. As long as the root causes of problems are identified, the fishbone diagram has achieved its objective.

Useful tips for success

• Make sure that there is consensus in the group about both the need and the characteristics of the cause statement before beginning the process of building the Fishbone Diagram.
• If appropriate, you can “graft” branches that do not contain a lot of information on to other branches. Likewise, you can split branches that have too much information into two or more branches as you go.
• Make parsimonious use of words while populating the Ishikawa diagram. Only use as many words as necessary to describe the cause or effect.

Fishbone Diagram template

Start with the cause and effect analysis and identify the causes of problems with this ready to use Fishbone Diagram template.

Download the Fishbone Diagram template

It’s Your Turn

What do you think? How do you apply the Fishbone Diagram? Do you recognize the practical explanation mentioned above or do you have additional information which you would like to share? What are your success factors for a set up?

Share your experience and knowledge in the comments box below.

More information

• Behnam, B., & Alvelos, H. (2011). Exploring the Potential of Quality Tools in Tire Retreading Industry: a Case Study . International Journal of Engineering Science and Technology (IJEST), 3(6), 5337- 5345.
• Ilie, G., & Ciocoiu, C. N. (2010). Application of Fishbone Diagram to Determine the Risk of an Event with Multiple Causes . Management Research and Practice, 2(1).
• Gupta, K., Sleezer, C.M. & Russ‐Eft, D.F. (2007). A Practical Guide to Needs Assessment . Pfeiffer.
• Ishikawa K. & Loftus, J.H. (1990). Introduction to quality control . Tokyo, Japan: 3A Corporation; 1990.

How to cite this article: Mulder, P. (2013). Fishbone Diagram (Ishikawa) . Retrieved [insert date] from Toolshero: https://www.toolshero.com/problem-solving/fishbone-diagram-ishikawa/

Published on: 07/19/2013 | Last update: 04/03/2023

Add a link to this page on your website: <a href=”https://www.toolshero.com/problem-solving/fishbone-diagram-ishikawa/”>Toolshero: Fishbone Diagram (Ishikawa)</a>

Did you find this article interesting?

Your rating is more than welcome or share this article via Social media!

Average rating 4 / 5. Vote count: 8

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Patty Mulder

Patty Mulder is an Dutch expert on Management Skills, Personal Effectiveness and Business Communication. She is also a Content writer, Business Coach and Company Trainer and lives in the Netherlands (Europe). Note: all her articles are written in Dutch and we translated her articles to English!

Related ARTICLES

DMADV Process: the Basics and Steps

Charles Kepner biography and books

Eight Dimensions of Quality by David Garvin

Agile Crystal Method explained

Philip Crosby biography, quotes and books

Zero Defects philosophy by Philip Crosby

Also interesting.

Soft Systems Methodology (SSM) by Peter Checkland

Action Plan explained plus template

Business Model You by Timothy Clark: a Summary

Leave a reply cancel reply.

You must be logged in to post a comment.

BOOST YOUR SKILLS

Toolshero supports people worldwide ( 10+ million visitors from 100+ countries ) to empower themselves through an easily accessible and high-quality learning platform for personal and professional development.

By making access to scientific knowledge simple and affordable, self-development becomes attainable for everyone, including you! Join our learning platform and boost your skills with Toolshero.

POPULAR TOPICS

• Change Management
• Marketing Theories
• Problem Solving Theories
• Psychology Theories

ABOUT TOOLSHERO

• Free Toolshero e-book
• Memberships & Pricing

MindManager

Guide to understanding fishbone diagrams

What is a fishbone diagram?

A fishbone diagram is a visualization tool used in business to identify and investigate the many possible causes of a particular event, issue, or outcome. Fishbone diagrams are also known as cause and effect diagrams or Ishikawa diagrams , the latter named for the diagram's original creator, Japanese organizational theorist Kaoru Ishikawa.

Fishbone diagrams are a valuable tool for root cause analysis (RCA), as they provide a systematic framework for exploring all possible causes of a problem, not just the most obvious ones.

Fishbone diagram elements

As the name implies, fishbone diagrams are shaped like fish—or, rather, fish skeletons. The parts of the fish represent certain parts of the cause-and-effect scenario you're exploring.

• Head: The head of the fish is where you record the problem or outcome you're analyzing.
• Backbone: The straight line of the backbone simply provides a way to connect all the other bones to the head or main problem.
• Bones: The bones represent all the various causes that could be leading to the main problem. In most fishbone diagrams, there are a few main categories of causes with specific details branching off each.

Types of fishbone diagrams

There are a few main types of fishbone diagrams, each with unique features and ideal use cases. Review the different types, and choose which one is the best fit for your needs.

The simple fishbone

The most commonly used fishbone diagram is the simple fishbone. This type of diagram does not have predefined categories, so you are free to use whatever categories or labels make the most sense for your scenario. Simple fishbone diagrams can be used in any industry or function.

The 4S fishbone

On a 4S fishbone diagram, the four "bones" branching off from the spine are systems, surroundings, skills, and suppliers. The 4S fishbone is popular in the service industry and can be used to solve problems like poor customer feedback or high customer churn.

The 8P fishbone

The 8P method is a problem-solving method that classifies possible causes of a problem into eight groups: physical evidence, personnel, place, product (service), price, promotion, process, and productivity/quality. The 8P fishbone is commonly used to solve problems within the service industry, manufacturing, and administrative functions.

The man machines materials fishbone

The man machines materials fishbone is another fishbone diagram with predefined categories. This type of diagram is mostly used in manufacturing. It was developed to help people focus on various causes rather than automatically blaming an issue on human error.

Examples of when to use a fishbone diagram

Fishbone diagrams are a useful tool for problem-solving , especially for tricky problems and ones that could stem from various causes.

If you're still wondering when to use a fishbone diagram to support your problem-solving activities, read these fishbone diagram examples.

Product development

In product development projects, fishbone diagrams are useful for exploring market opportunities and identifying issues with current market offerings. To ensure your new products are truly filling a gap in the market, use a fishbone diagram to thoroughly explore your target customers' problems and the causes of those problems.

Troubleshooting processes

When a process or workflow isn't producing the desired outcomes, fishbone diagrams can help you diagnose the issues. When you do a deep dive into potential causes, it becomes easier to find the right solutions.

Root cause analysis

Fishbone diagrams provide a visual framework for root cause analysis and exploration. RCA methodology involves deeply investigating the underlying issues of problems that pop up, not just treating surface-level symptoms and putting out fires.

Benefits of fishbone diagrams

Fishbone diagrams help you visualize and explore the underlying causes of a particular problem. Top benefits of fishbone diagrams include:

Identifying potential causes of a problem

The main benefit of a fishbone diagram is its ability to help you identify potential causes of a problem. With the different types of fishbone diagrams available, there is a layout to fit any type of business problem in any industry. You can use a diagram with predefined categories or assign your own categories to fit your needs.

Revealing areas of weakness or bottlenecks in current processes

With a fishbone diagram, you can ensure no stone remains unturned as you study the problem. As you explore potential causes, the fishbone diagram will reveal any areas of weakness or bottlenecks in your current processes. You'll be able to address these issues, and any other root causes you uncover along the way.

Accelerating problem-solving

Most people are visual learners, and visual aids are proven to boost memory retention and recall. The visual format of the fishbone diagram accelerates the problem-solving process, helping you organize and categorize your thoughts and findings within a logical structure.

How to make a fishbone diagram

To get started making a fishbone diagram, follow these steps:

• Identify a problem to solve. The problem will form the "head" of your fishbone diagram. In addition to describing the problem, you can add information regarding where and when it occurred, if it was a specific event, who was involved, and the impact on your business.
• Choose the cause categories. Draw the "backbone" of your fishbone diagram and add lines branching from it to represent your cause categories. Refer to the types of fishbone diagrams section if you need ideas for cause categories to use.
• Brainstorm potential causes. Write the specific cause ideas as branches off their corresponding cause categories.
• Delve deeper. You may need to create further branches connected to your cause branches to explore the potential root cause(s) thoroughly. When collaborating with your team, include everyone's input and ideas.
• Agree on a root cause. Once you've finished your fishbone diagram, discuss and agree upon a root cause. There may be more than one.
• Discuss solutions. After using your fishbone diagram to find your root cause, take the time to devise solutions to prevent the same problem from recurring.

Why use MindManager to make fishbone diagrams

With a fishbone diagram software like MindManager , problem-solving and root cause analysis is changed forever—for the better. Features of MindManager include:

• User-friendly, intuitive interface
• Extensive image library—over 700 topic images, icons, and symbols to add to your fishbone diagrams
• Convenient file storage, retrieval, and sharing
• Powerful integrations with file storage apps like Box and OneDrive
• Google Docs integration via Zapier
• Numerous templates, tools, and features to facilitate brainstorming and strategic planning
• Google Chrome extension—MindManager Snap—to easily collect and import text, links, and images from the web
• Ability to add rich data—links, images, and documents—directly to your diagrams and charts

When you use MindManager as your fishbone diagram maker, you'll be able to quickly and easily record all the information you need, collaborate closely with your team, and gain a clearer perspective on the problem at hand and its potential causes.

Fishbone diagram templates

MindManager comes pre-installed with fishbone diagram templates. To use these templates:

• Open MindManager
• Click NEW in the navigation menu
• Select the template you want to use
• A preview screen will appear - check to see if you'd like to use your selected template
• Select 'Create Map'
• Customize the template for your specific project

Fishbone diagram FAQs

How is a fishbone diagram used for problem-solving.

Fishbone diagrams provide a visual framework for investigating the possible causes of a problem. They help you clearly sort ideas and explore various cause-and-effect connections within your business.

What is a fishbone diagram also known as?

There are many different names for the fishbone diagram. Some of the most common include:

• Cause and effect diagram
• Ishikawa diagram
• Fishikawa diagram
• Herringbone diagram

Conquer cause and effect with a fishbone diagram

Fishbone diagrams provide a way to visually organize and examine the potential causes relating to a particular problem. There are multiple types of fishbone diagrams, and they're popular across various industries and functions, including manufacturing, service-based industries, and business administration.

With a fishbone diagram, you can more easily identify the causes of a problem, reveal areas of weakness in current business processes, and accelerate your problem-solving activities.

Visualize more with MindManager

MindManager's fishbone diagram maker features a user-friendly interface, numerous premade templates, and an extensive library of images to support your diagram. To make a fishbone diagram, try MindManager today .

Related Articles

by MindManager Blog

9 essential problem solving tools: the ultimate guide

July 7, 2020

What is problem solving? And why is it important at work?

June 30, 2020

Using fishbone diagrams for problem solving

December 30, 2019

Other types of maps and charts

Task and project management, problem solving/ decision making, brainstorming, organizing data, process mapping, try the full version of mindmanager free for 30 days.

• Mind Map Maker
• Concept Map Maker
• Bubble Map Maker
• Brace Map Maker
• Sunburst Chart Maker
• Online AI Note Taker
• Timeline Maker
• Tree Diagram Maker
• Fishbone Diagram Maker
• Organizational Chart Maker
• Gantt Chart Maker
• Spider Diagram Maker
• EdrawMind AI
• AI Summarize
• AI Mind map
• AI Article generation
• AI Copywriting
• AI Translation
• --> --> >--> -->