fishbone in problem solving

Have a language expert improve your writing

Run a free plagiarism check in 10 minutes, generate accurate citations for free.

• Knowledge Base
• Starting the research process
• What Is a Fishbone Diagram? | Templates & Examples

What Is a Fishbone Diagram? | Templates & Examples

Published on January 2, 2023 by Tegan George . Revised on January 29, 2024.

A fishbone diagram is a problem-solving approach that uses a fish-shaped diagram to model possible root causes of problems and troubleshoot possible solutions. It is also called an Ishikawa diagram, after its creator, Kaoru Ishikawa, as well as a herringbone diagram or cause-and-effect diagram.

Fishbone diagrams are often used in root cause analysis , to troubleshoot issues in quality management or product development. They are also used in the fields of nursing and healthcare, or as a brainstorming and mind-mapping technique many students find helpful.

Table of contents

How to make a fishbone diagram, fishbone diagram templates, fishbone diagram examples, advantages and disadvantages of fishbone diagrams, other interesting articles, frequently asked questions about fishbone diagrams.

A fishbone diagram is easy to draw, or you can use a template for an online version.

• Your fishbone diagram starts out with an issue or problem. This is the “head” of the fish, summarized in a few words or a small phrase.
• Next, draw a long arrow, which serves as the fish’s backbone.
• From here, you’ll draw the first “bones” directly from the backbone, in the shape of small diagonal lines going right-to-left. These represent the most likely or overarching causes of your problem.
• Branching off from each of these first bones, create smaller bones containing contributing information and necessary detail.
• When finished, your fishbone diagram should give you a wide-view idea of what the root causes of the issue you’re facing could be, allowing you to rank them or choose which could be most plausible.

Receive feedback on language, structure, and formatting

Professional editors proofread and edit your paper by focusing on:

• Academic style
• Vague sentences
• Style consistency

See an example

There are no built-in fishbone diagram templates in Microsoft programs, but we’ve made a few free ones for you to use that you can download below. Alternatively, you can make one yourself using the following steps:

• In a fresh document, go to Insert > Shapes
• Draw a long arrow from left to right, and add a text box on the right-hand side. These serve as the backbone and the head of the fish.
• Next, add lines jutting diagonally from the backbone. These serve as the ribs, or the contributing factors to the main problem.
• Next, add horizontal lines jutting from each central line. These serve as the potential causes of the problem.

Lastly, add text boxes to label each function.

You can try your hand at filling one in yourself using the various blank fishbone diagram templates below, in the following formats:

Fishbone diagram template Excel

Download our free Excel template below!

Fishbone diagram template Word

Download our free Word template below!

Fishbone diagram template PowerPoint

Download our free PowerPoint template below!

Fishbone diagrams are used in a variety of settings, both academic and professional. They are particularly popular in healthcare settings, particularly nursing, or in group brainstorm study sessions. In the business world, they are an often-used tool for quality assurance or human resources professionals.

Fishbone diagram example #1: Climate change

Let’s start with an everyday example: what are the main causes of climate change?

Fishbone diagram example #2: Healthcare and nursing

Fishbone diagrams are often used in nursing and healthcare to diagnose patients with unclear symptoms, or to streamline processes or fix ongoing problems. For example: why have surveys shown a decrease in patient satisfaction?

Fishbone diagram example #3: Quality assurance

QA professionals also use fishbone diagrams to troubleshoot usability issues, such as: why is the website down?

Fishbone diagram example #4: HR

Lastly, an HR example: why are employees leaving the company?

Fishbone diagrams come with advantages and disadvantages.

• Great tool for brainstorming and mind-mapping, either individually or in a group project.
• Can help identify causal relationships and clarify relationships between variables .
• Constant iteration of “why” questions really drills down to root problems and elegantly simplifies even complex issues.

Disadvantages

• Can lead to incorrect or inconsistent conclusions if the wrong assumptions are made about root causes or the wrong variables are prioritized.
• Fishbone diagrams are best suited to short phrases or simple ideas—they can get cluttered and confusing easily.
• Best used in the exploratory research phase, since they cannot provide true answers, only suggestions.

Here's why students love Scribbr's proofreading services

Discover proofreading & editing

If you want to know more about the research process , methodology , research bias , or statistics , make sure to check out some of our other articles with explanations and examples.

Methodology

• Sampling methods
• Simple random sampling
• Stratified sampling
• Cluster sampling
• Likert scales
• Reproducibility

 Statistics

• Null hypothesis
• Statistical power
• Probability distribution
• Effect size
• Poisson distribution

Research bias

• Optimism bias
• Cognitive bias
• Implicit bias
• Hawthorne effect
• Anchoring bias
• Explicit bias

Fishbone diagrams have a few different names that are used interchangeably, including herringbone diagram, cause-and-effect diagram, and Ishikawa diagram.

These are all ways to refer to the same thing– a problem-solving approach that uses a fish-shaped diagram to model possible root causes of problems and troubleshoot solutions.

Fishbone diagrams (also called herringbone diagrams, cause-and-effect diagrams, and Ishikawa diagrams) are most popular in fields of quality management. They are also commonly used in nursing and healthcare, or as a brainstorming technique for students.

Cite this Scribbr article

If you want to cite this source, you can copy and paste the citation or click the “Cite this Scribbr article” button to automatically add the citation to our free Citation Generator.

George, T. (2024, January 29). What Is a Fishbone Diagram? | Templates & Examples. Scribbr. Retrieved April 2, 2024, from https://www.scribbr.com/research-process/fishbone-diagram/

Is this article helpful?

Tegan George

Other students also liked, how to define a research problem | ideas & examples, data collection | definition, methods & examples, exploratory research | definition, guide, & examples, what is your plagiarism score.

• 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

How to build a fishbone diagram and get the most out of it

No business operates without problems along the way. But to solve them in time, you’ll need to be able to determine the cause quickly. That’s where using a fishbone diagram comes in.

A fishbone diagram , also known as the Ishikawa diagram or cause-and-effect diagram, is a tool you can use to visualize all of a problem’s potential causes, allowing you to discover the root causes and identify the best possible solution.

We put this guide together to show you how to make a fishbone diagram based on a fictional problem we’ll be investigating: why a software company’s customer churn is so high.

Let’s get started.

Step 1 – Define the problem

The first step to solving any problem – and the key to learning how to make a fishbone diagram – is correctly defining it. A clearly defined problem makes it easier to identify causes. It also encourages us to determine whether there’s even a problem to begin with.

In this case, the problem we’ve identified is that 40% of users cancel their subscriptions after the first month — which keeps us from reaching our goal of keeping cancellations below 20%. Now that we’ve identified our main problem, we can go ahead and add that to the fishbone diagram.

Problem definition tips:

• If you’re using the fishbone diagram to design a process or increase productivity, it’s just as important to correctly define your output. Your goals should be objective and achievable.
• Place the problem (the fish head) on one side of the diagram, and build the rest of the diagram (the fish bones) out to its left or right. The idea is that the “fish bones” indicate the impact of the causes.
• Place the causes with the biggest impact closer to the fish head and the causes with the smaller impact further away.

Step 2 – Decide on key categories of causes

Next, decide what areas of the problem are key to determining the actual cause. Going back to our example of investigating a high churn rate, here are three areas worth looking into:

• Subscription system

Once you start considering potential causes, you might find that most of them fall within one of these three categories. But you can always add more categories if needed. For example, If you think marketing impacted your retention figures, you could add that as a fourth area.

You can have as many areas as you need to. But to keep things simple, we recommend limiting yourself to no more than 10 — especially since we’re only learning how to make a fishbone diagram with this example.

Step 3 – Determine the actual causes of the problem

Now that you’ve defined the key areas to look into, let’s go through each one to determine all the individual influences that can affect our output. Look at each category and list every possible cause you can think of.

Looking at the subscription system, some possible causes include:

• We aren’t offering enough payment options
• The payment and registration systems are difficult to navigate
• Credit cards expire, voiding renewal
• The system doesn’t send out reminders for renewals.

When considering the user, potential causes include:

• Users don’t understand the full benefit of the software
• Users don’t know how to use all the functions
• Users experience delays when contacting support
• Users don’t use the software continuously, only requiring it for a few days at a time
• Users forget about the product.

When it comes to the software itself, potential causes may be:

• The software is unstable and crashes regularly
• The software is difficult to use
• Software installation requires multiple plugins to function well
• Key functionality requires additional subscriptions
• The software is insecure.

These are just a few potential causes. You should fill your fishbone diagram with as many different causes as you can come up with. Note that not every area of your diagram needs to have causes. Some might even have more causes than others.

Regardless, you now have a starting point to determine root causes. To keep going, investigate each cause to establish its actual effect on your output.

Tips to determine the actual cause:

• Run a brainstorming session or lay out a process map to generate better causes for your fishbone diagram
• Invite other team members in the process to make sure you’ve identified all the potential causes
• Some causes may have multiple sub-causes. Expand your fishbone diagram as needed to encompass all possible causes.

Step 4 – Using tools to plan the way forward

Remember, a fishbone diagram helps identify a problem’s causes. It doesn’t lead to solutions on its own. In fact, part of learning how to make a fishbone diagram is knowing what other tools you can use to identify causes more effectively.

Here are a few more tools to help you take your fishbone diagram to the next level:

Process Map

A process map is a flowchart of a specific system, showing all its inputs and outputs. It works best in areas like the manufacturing industry, where each product has a clearly defined process with multiple steps.

Process mapping involves looking at each step of the process one by one and listing all the potential influences. In an actual manufacturing environment, this may include being present on the production line and viewing the system, taking notes as you go through the process.

A process map is very effective at making sure you consider all the steps and influences involved in a system. In other words, it helps you clearly identify potential causes and add them to your fishbone diagram.

Brainstorming

Brainstorming is a fairly common tool in modern businesses. Instead of considering all the factors of a fishbone diagram by yourself, include others in the process. When working alone, it’s easy to overlook certain areas and completely miss others.

That’s why it’s worth making sure your  brainstorming session  takes the shape of a clearly-defined meeting. Have someone lead the session, taking note of any ideas team members offer up and leaving room for discussion. The goal is to end the brainstorming session with a list of causes to add to your fishbone diagram.

Once you’ve filled out your fishbone diagram, make sure everyone’s on the same page about how to follow up — whether it’s about delegating tasks or setting clear deadlines.

Tips for planning next steps:

• Not sure what causes to investigate? Collaborate with your team members on developing a cause-and-effect matrix. This way, you’ll get to rank causes by priority based on your team’s experience.
• Want to address a problem’s root cause and not just its symptom? Use our 5 Whys Template to take a closer look.
• How to make a fishbone diagram in a remote team

A fishbone diagram is more effective when multiple people get involved in creating it. But if your team works in remote and hybrid settings, you’ll need a tool designed to facilitate seamless collaboration.

Miro’s visual workspace is built for collaboration, making it easy to make a fishbone diagram together in real time — even if you aren’t in the same room. Seamlessly build diagrams using our intuitive, automated diagramming tools and our drag-and-drop, infinite canvas.

Not sure how to make a fishbone diagram from scratch? Save time using our free Fishbone Diagram Template . It’s fully customizable, allowing your team to add as much detail as you want and adjust its look and feel.

Tips for collaborating on a fishbone diagram in Miro:

• Invite your team to edit your board with you in real-time
• Invite stakeholders to view and comment on your Miro board for instant feedback
• Differentiate ideas by color-coding them
• Use frames to present your fishbone diagram and easily export it as a PDF or image
• Use sticky notes to add important context when building your fishbone diagram

Above all, avoid trying to build your fishbone diagram too quickly. Take the time to understand all the contributing factors, and make sure that anything you add to the fishbone diagram adds value.

• When to use a fishbone diagram?

Though fishbone diagrams were originally meant for problem-solving, they’re far more versatile — helping you break down any process or system into its contributing factors.

Here are a few use cases where knowing how to make a fishbone diagram comes in handy:

• To analyze a problem statement
• To brainstorm the causes of the problem (root cause analysis)
• To analyze a new design
• Process improvement
• Quality improvement

When in doubt, talk to your team to clarify the problem you’re investigating and how a fishbone diagram would help.

Miro is your team's visual platform to connect, collaborate, and create — together.

Join millions of users that collaborate from all over the planet using Miro.

• Step 1 – Define the problem
• Step 2 – Decide on key categories of causes
• Step 3 – Determine the actual causes of the problem
• Step 4 – Using tools to plan the way forward

Keep reading

Don’t let ideas die post-retro: 5 ways to make retrospectives more actionable.

Removing the hassle of brainstorm documentation with Miro + Naer

From ideas to execution: 5 ways to go beyond brainstorming to bring ideas to life

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

Fishbone Diagram

A fishbone diagram, also known as an Ishikawa diagram or cause and effect diagram, is a tool used to identify the root causes of a problem. It is named after Japanese quality control expert Kaoru Ishikawa, who developed the concept in the 1960s. Organizations across a variety of industries, including manufacturing, healthcare, and service use the fishbone diagram to identify and analyze the factors that contribute to a particular problem or issue.

Teams typically use a fishbone diagram to identify all of the possible causes of a specific problem or effect. You construct it by drawing a horizontal line with the problem or effect written at the end, and then drawing lines coming off of the central line to represent the different categories of causes. Teams typically label it with the major contributing factors, such as people, equipment, materials, environment, and methods.

Once a team determines the categories, the next step is to brainstorm and list out all of the potential causes within each category. You then draw the causes as branches off of the main lines, with each branch representing a specific cause.

Once a team has identified and listed all of the causes, the next step is to analyze the relationships between the causes to identify the root causes of the problem. You can do this through a variety of techniques, such as the 5 Whys method, which involves asking why the problem occurs repeatedly until the root cause is identified.

Once a team has identified the root causes, the next step is to develop and implement solutions to address those root causes. This can involve making changes to processes, equipment, training, or other factors that contribute to the problem.

The fishbone diagram is a valuable tool for identifying and addressing the root causes of a problem. By systematically analyzing the factors that contribute to a problem, organizations can develop effective solutions and improve the overall performance and quality of their processes.

Fishbone Diagram Example

When building a fishbone team members should be careful to include only the actual physical causes. It can be tempting to include items someone believes is happening or wishes were happening. Consequently, a fishbone can turn into a “wishbone” diagram.

Additional Resources on the Fishbone Diagram

• Ask Art: How Useful is Six Sigma and the Black Belts and Green Belts that Come with It?
• Jim Womack on how lean compares with Six Sigma, Re-engineering, TOC, TPM, etc., etc.
• Not Every Problem Is a “Nail” But Companies Typically Reach for the Same Old “Hammer”
• Why A3 Thinking is the Ideal Problem-Solving Method
• Developing Problem Solvers
• Fishbone Diagrams and Mind Maps

Privacy Overview

• Skip to main content
• Skip to primary sidebar
• Skip to footer

Additional menu

Fishbone diagrams: How to use them for problem-solving

October 5, 2023 by MindManager Blog

When something goes wrong, it’s essential to understand the root cause in order to prevent it from occurring again.

However, life and business are both complex, making it difficult to identify at times the underlying causes which created the situation you’re facing now. That’s where and when a fishbone diagram can help!

In this article, we’ll dive into everything you need to know about fishbone diagrams and how to use them for problem-solving.

What is a fishbone diagram?

Fishbone diagrams (also called Ishikawa diagrams and cause-and-effect diagrams) are visualizations used to identify and illustrate the causes for a specific event. Potential causes are often brainstormed and then categorized in order to identify a problem’s root cause.

The diagram gets its name due to the branches radiating out from the main issue in a way that resembles a side view of a fish skeleton. However, the process can be applied to most mind map layouts.

Here’s a fishbone diagram example:

When to use fishbone diagrams

Fishbone diagrams help focus you and your team’s energy on the root cause of a problem instead of merely addressing and wasting time on the symptoms.

Here are a few common applications of Fishbone diagrams:

Manufacturing: Discover the root cause of a manufacturing issue by brainstorming and ranking the likelihood and impact of all the areas that influence the production process.

How to create a fishbone diagram in MindManager in 5 steps

Fishbone diagrams are quick to make in MindManager and the examples above are included as templates to make it even easier.

MindManager’s ease of capturing ideas during brainstorming makes it the ideal tool to capture and organize potential causes. The visual format allows you to see all the causes simultaneously, draw relationships between causes, and identify if the root cause is found multiple times within the diagram.

Here’s how to create a fishbone diagram:

• In MindManager, go to the File menu, select New and then click into the Problem-Solving folder. There you’ll find three templates for Fishbones, the manufacturing, service, and product analyses. Select a template.
• Enter the issue in the central topic.
• Next, either brainstorm potential causes and add them as floating topics initially and categorize them after the brainstorming session. Or, use each category as a guide for a mini-brainstorm session and enter the potential causes directly in the appropriate branch.
• Add more details to your causes as new subtopics or notes with the cause itself.
• Once all the potential causes have been identified, you can take the diagram a step further and rank each cause. One way to do this would be to use the Priority marker to rank the cause between 1 and 9. You can later filter the diagram and view specific priorities and hide the less important ones that will distract the focus of the team.

Key MindManager features for fishbone diagrams

There is no one single ‘right’ way to create, categorize, or rank items within a fishbone diagram.

With that said, here’s a list of ways to apply some of MindManager’s features to transform an ordinary diagram into a powerful application to visualize and empower your work.

• Use color (fonts, topic fill color) to categorize different causes.
• Change the font characteristics to emphasize different causes (e.g. bold, larger fonts, different font types, etc.).
• Use topic images to add greater context and enhance the visualizations.
• Write topic notes for more in-depth details related to each cause.
• Apply icons and tags to categorize causes.
• Hyperlink or add attachments to provide more details.
• Draw relationship lines between different connected causes throughout the diagram.
• Assign resources to any causes that you have identified. This may clarify who is responsible or accountable for that cause.
• Collapse branches for a quick overview or drill down into all the details.
• View the diagram through multiple lenses. For instance, you are not confined to the layout of the Fishbone diagram. Switch views to see the diagram as an outline, or dive in the Schedule, Icon or Tag views to see your content in groupings based on your assigned categories or due dates.
• Filter content to either show or hide topics that you have annotated with tags or icon markers. For instance, filter on all the top priority potential causes that need additional investigation.
• Share your diagram by either publishing it onto the web (and sharing a link) where anyone can open and view the Fishbone diagram interactively in their browser or export the diagram into a variety of different formats (e.g. Microsoft Word, HTML5, Microsoft Project, etc.).

Download MindManager today to get started on your fishbone diagram!

Ready to take the next step?

MindManager helps boost collaboration and productivity among remote and hybrid teams to achieve better results, faster.

Why choose MindManager?

MindManager® helps individuals, teams, and enterprises bring greater clarity and structure to plans, projects, and processes. It provides visual productivity tools and mind mapping software to help take you and your organization to where you want to be.

Explore MindManager

• 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

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

Just In Time: an Inventory Management Method

Also interesting.

Project budget explained: theory and a template

SOAR Analysis: the theory plus example and template

Stakeholder Analysis explained plus template

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

Fishbone Diagram Tutorial

What are your fishbone diagram needs.

A fishbone diagram is a powerful problem-solving tool used in healthcare, engineering, and many other industries. Find out how you can use Lucidchart to construct one.

4 minute read

Want to make a Fishbone diagram of your own? Try Lucidchart. It's quick, easy, and completely free.

What is a fishbone diagram?

A fishbone diagram is also known as an Ishikawa diagram, herringbone diagram, or cause-and-effect diagram. This is because it describes the potential causes of a given problem or outcome. The diagram resembles an actual fish bone, with a long line running down the center pointing to the main outcome, also called the "problem statement". The other bones branch out from the middle bone and represent different categories of causes. In the template below, we've shown the six standard categories, Measurements, Materials, People, Machine, Methods, and Environment. However, feel free to swap these out for categories that best fit your problem.

What is a cause and effect analysis?

A cause and effect diagram is also known as a fishbone diagram due to its appearance. Cause and effect analysis can be used in a wide variety of industries, including engineering, marketing, and manufacturing. It was invented by Kaoru Ishikawa as a way to pinpoint contributing factors in business problems, especially in the field of industrial manufacturing. When conducting cause and effect analysis, teams start with a problem or challenge, then look at which roadblocks stand in the way of success.

Make a fishbone diagram in Lucidchart

You can make your own fishbone diagram with Lucidchart. To design the skeleton, simply use the line tool by clicking the "L" key. A crosshair will appear and let you draw a line. Easily add lines to the template below, and then drag out text boxes onto the lines to properly label them. Lucidchart also supports a variety of convenient features that make diagramming easy, like draggable resizing, pop-out context menus, and custom image upload. And once you’ve finished perfecting your diagram, you can share or publish it online.

How to create a fishbone diagram

It’s simple to create your own cause and effect analysis example by using Lucidchart. It’s professional diagramming software that runs seamlessly in your browser. This example shows the brainstorming process for a marketing team that’s trying to understand why website traffic has dipped. Open our editable template to start tackling your own business’s obstacles.

Get started in Lucidchart

2. Navigate to My Documents.

3. Click Create > New Document.

4. Explore and start with a fishbone diagram template or create a new document in Lucidchart.

Determine your problem statement

5. The first thing you need for your fishbone diagram is a problem statement. Since fishbone diagrams are used to analyze cause-and-effect relationships, the problem statement is your final effect or result. Drag out a box from the toolbox in Lucidchart (it’s accessible from the left side of the screen), then double-click to label it accordingly. Depending on your industry and use case, the problem could be anything from “shipments arrive late” to “patient readmitted to the hospital.” Once you have the problem statement, draw a line out from it. Your line will be shorter or longer depending on how many categories you want to include.

List categories

6.  Next, you’ll add lines and corresponding boxes to show the categories of causes for your problem statement. It might be helpful here to think backwards. First, determine all the potential causes for a problem, and then group them into categories. The traditional categories for a fishbone diagram are the six M's:

Measurements

Mother Nature

If you’re not sure what to include, these categories are a great first step. You are also free to choose your own, more specific categories, depending on what best fits your diagram.

7. To add causes, draw new lines from the category lines and label them with text boxes. To draw a line without dragging it out from a shape, simply hold down the L key and crosshairs will appear. Click on any line again to angle it or rotate it. Remember to add as many causes as you can think of, even if some of them are less likely to occur than others. The more details you have, the easier it will be to analyze your problem.

Review your work

After you’ve completed the document, it’s time to review. Make sure your text is error-free and large enough to read. Did you include all relevant information, and is it organized under the right categories? Try sending a URL to a colleague and inviting them to comment or collaborate with you.

Additional Resources

• How to Make a Fishbone Diagram Template in PowerPoint
• Fishbone Diagram Template in Excel
• How to Create a Fishbone Diagram in Microsoft Word

Evaluate the cause and effect analysis of any process with a fishbone diagram. Easy to make and free when you sign up, try Lucidchart today!

• 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

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

Fishbone Diagrams for Consequential Problem-Solving

Visualize Processes and Improve

The most successful businesses are not perfect. They are resilient. Every business encounters problems; most encounter them frequently. The ones that thrive are developing a problem-solving culture and arm employees with the tools to find and resolve the root causes of issues effectively. When employees are effective, empowered problem-solvers, obstacles turn into opportunities. One powerful problem-solving tool is the Fishbone Diagram.

What is a Fishbone Diagram?

A Fishbone Diagram also called an Ishikawa diagram or cause and effect diagram is a visual management tool used to document all the potential causes of a problem to uncover the root causes. The Fishbone Diagram helps users group these causes into categories and provides a structure to display them. When used effectively, it ensures that teams address the actual cause of the problem and don’t just implement a Band-aid solution.

The Fishbone Diagram is called such due to its resemblance to a fish’s skeleton. It was developed by Kaoru Ishikawa and became popular in the 1960s. It is used within many modern quality management methodologies, including Six Sigma and Lean Manufacturing. 

When to Use a Fishbone Diagram

Although we refer to the Fishbone Diagram as a structured problem-solving tool, it has other uses. It is helpful in breaking down the contributors to any process or system. Some ways to use it to test a problem statement, conduct root cause analysis, predict the results of a new process, streamline an existing process, improve quality outcomes, and uncover bottlenecks. 

How to Use a Fishbone Diagram

Step 1: Define the Problem

The first step in problem-solving, whether you use the Fishbone or not, is defining the problem correctly. Ideally, the problem statement will include an objective metric that can be used to determine success. For example, a problem statement such as, “The contact center abandon rate is too high,” will not be as helpful as a statement like, “The contact center abandon rate increased by 20% last month.”

In terms of the Diagram, the problem statement represents the “head” of the fish.

Keep in mind:

• If you are using a fishbone diagram to improve a process, instead of the problem, you will define your desired outcome in an objective and achievable way.
• Each of the “bones” in the diagram will represent a category of potential causes, but causes with the most significant impact should be closest to the “head.”

Step 2: Decide on Categories of Causes

The Fishbone tool forces you to think about the potential causes for the problem in several categories represented by the bones. The number will depend on the type and complexity of the problem. You can choose categories that make sense for your project, but in manufacturing, the 6 Ms are often used. They include:

• Man - the people involved in the process
• Methods - the Standard Work by which the process is performed
• Machines - the equipment and tools needed for the process
• Materials - the raw inputs, parts, consumables, and so forth
• Measurements - the data that is used to evaluate process results
• Mother Nature (Environment) - the conditions under which the process is performed.

Another commonly used structure is the McKinsey 7S Framework, which includes Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff. Marketers may go with the 4Ps of Marketing; Product, Place, Price, and Promotion. Non-manufacturing process may include additional categories such as:

In our software call center abandon rate example, we’ll choose the categories of :

• Measurement
• Environment

Step 3: Brainstorm Potential Causes and Identify Roots

Now that the categories are defined, the team can go through each one and try to determine all the individual influences that can affect our results. Look at each type and list everything that falls within it. If a potential cause sounds more like a symptom than the root of the matter, the 5 Whys technique can be used to ensure that bottom-line reasons are included. If a source cause supersedes a potential cause, it can be removed from the diagram, or you can use strikethrough to preserve it while moving on to the fundamental problem. In this example, I’ve struck through “Low morale” as a potential cause because it is most likely a symptom of the lack of training and scheduling problems.

Step 4: Analyze the Diagram and Determine Next Steps

The Fishbone Diagram does not direct you to the solution, but it gives you an idea about where to look. By identifying potential causes in this manner, the team can assess the impact of each and brainstorm possible solutions. As in the case of our example, you’ll probably find more opportunities for improvement than you can tackle at once, but the exercise will put the team in a better position to decide what to do next. The Fishbone Diagram also becomes a good starting point for the next improvement cycle once your most critical root causes are addressed.

See How it Works: Schedule a Demo

The benefits of digital fishbone diagrams.

Back in the 1960s when the Fishbone Diagram was introduced, teams used paper to visualize their problem statement and possible causes. While that approach is acceptable for small groups working in the same space for a short period, it is not ideal for the way people work today.

That’s why KaiNexus has incorporated Fishbone Diagrams into our continuous improvement software platform. 

• The Fishbone Diagram is created and managed in the same platform you will use for implementing the changes once the analysis is complete.
• Information about your problem, the potential causes, and possible solutions are all collected for future review.
• Remote teams can be as effective as in-person ones.
• Roles and permissions can be applied to determine who can add access and edit Fishbones.
• Fishbone Diagrams can be used for Items, Projects, Improvements, Incidents, Tasks, and Charts. 
• Set up to 6 custom categories per diagram or reuse existing categories
• Highlight or strikethrough items

Using digital Fishbone Diagrams that are integrated with your improvement management software will help your team solve problems faster and accelerate the pace of positive change.

Fishbone Diagram Tips

The Fishbone diagram approach is not complicated, but you can do a few things to get the most out of it. We recommend:

• Use category names that are meaningful for your business. If “Methods” isn’t quite right, maybe “Procedures” is a better fit, for example.
• Don’t overload the categories. Create a new one if necessary. Likewise, don’t overcomplicate it; there’s no need to use six categories if four will do.
• Be careful not to add causes that are actually solutions.
• Prioritize your causes by keeping the most impactful ones closest to the “head”
• Use Fishbone Diagrams along with, not instead of, other problem-solving techniques such as The 5 Whys, A3s, process maps, and control charts.

KaiNexus is delighted to put one more digital improvement tool in the hands of our customers. If you’d like to know more about the impact of KaiNexus, one of our experts is available to help.

Want to learn more about KaiNexus Fishbone Diagrams?

Check out our fishbone video or support.kainexus.com for more information..

Improvement Software Features

virtual visual management

IMPROVEMENTS & PROJECTS

whatever you do

CHARTS & DATA

track key metrics

KAINEXUS MOBILE

improve from anywhere

engagement, activity & impact

increase collaboration

SMART NOTIFICATIONS

knowledge sharing

see how it works

• Our Customers

Why KaiNexus

• Collaboration
• Standardization
• Customer Success Manager
• Lean Strategy
• Solutions Engineering
• Customer Marketing
• Configuration
• Continuous Enhancements
• Employee Driven
• Leader Driven
• Strategy Development
• Process Driven
• Daily Huddles
• Idea Generation
• Standard Work
• Visual Management
• Advanced ROI
• Notifications
• Universal Badges
• Case Studies
• Education Videos

Copyright © 2024 Privacy Policy

You are using an outdated browser. Please upgrade your browser .

• Stay up to date with TXM

Using Fishbone Diagrams to Solve Problems

Fishbone diagrams may also be referred to as “Cause and Effect” diagrams, or Ishikawa diagrams , after their founder Kaoru Ishikawa. Whatever your preferred term, the fishbone diagram is a great tool for delving into a problem when we need to determine the root cause, and you are surrounded by the opinions of those around you. It provides a process to clearly define the “Effect” and then puts you to thinking about the possible causes, based on the categories of common problems in manufacturing.

Defining your “Effect”

The first step in using the fishbone diagram as a problem-solving tool is to clearly define your effect or outcome that you don’t like. This could be a quality issue, not meeting metrics or troubleshooting the introduction of a new process or product line. This becomes the “head” of the diagram. Use butchers paper or a whiteboard to sketch out out the fishbones template.

Defining an effect takes a little practice. Make sure it is brief and succinct. Use facts and numbers where possible. Spend a few minutes reflecting on your effect with the team; does everyone agree that the statement defines the problem as fully as possible?

Brainstorming the “Causes”

With your team, we want to add the bones to this diagram, brainstorming all of the possible influencing factors. Each idea needs to be put into a category or branch.

In manufacturing, it is accepted that there are 6 main branches that need investigation. These are often described as the “6M’s” but feel free to use the terms that best suit your company.

• People / Manpower: Everyone involved with the process across the value stream, including support functions
• Processes / Methods: This defines how the process is performed and the all requirements needed for doing it, including quality procedures, work orders / travellers / work instructions, drawings.
• Machines / Equipment: All machines and equipment, needed to accomplish the job, including tools
• Materials: Raw materials, purchased parts and subassemblies that feed into the end product
• Measurements: defines how have we determined that the outcome is wrong
• Environment: The conditions that influence the process including time, temperature, humidity or cleanliness

As the team suggests possible causes, determine which heading that idea belongs under, jotting it down clearly. Also add another branch, covering “why” that cause would influence the effect we are investigating. Continue until the team runs out of ideas.

If you find there are branches of the diagram that are missing, delve into that area further, asking questions; “Is it possible that the environment has affected our problem” too hot, too cold, too wet?

When you are out of ideas, take a break to clear everyone’s head. Here we change modes and needs a little time for our brains to shift gears. Now we don’t need any new ideas, we need to determine the top 2 or 3 possible causes that can be resolved and will have the most impact of the effect. You can use an A3 plan  to outline the current state, future state and the steps needed to achieve it.

If the top few causes are not clear, determine what further information is needed. While using a fishbone diagram does take time to develop, it will help you and your team to determine the real causes and allow you to improve your process and implement lasting change.

Related Content

Txm article: problem solving, txm article: learn about creating a culture of daily problem solving in this lean minute video, txm lean minute: videos about lean problem solving, txm lean minute: learn simple techniques to finding the root cause in this lean minute video, purchase lean products including problem solving concern strips from our e-store.

Continuous improvement is at the heart of what we do at TXM. We have a proven track record of helping our customers achieve sustained superior operational performance. One of the tools we use to help our clients achieve this is the fishbone diagram. Also known as a Cause and Effect Diagram, the Fishbone Diagram is a valuable tool for identifying the root causes of problems. By identifying and addressing the root causes of problems, our clients are able to achieve significant improvements in their operations. If you are facing operational challenges, we encourage you to contact us to learn more about how we can help you using fishbone diagrams and other Lean tools. Continuous improvement is essential for achieving Operational Excellence, and TXM is here to help you every step of the way.

Author: Robert Chittenden

Robert Chittenden is a Senior Lean Consultant at TXM Lean Solutions

Easy Access: Reaching New Heights

Easyquip Interview: Moving from Batch to Flow Production

Interpod Interview: Building the Production Process for Modular Bathrooms

Unmissable articles.

• The Ultimate Guide To Lean Plant Layout
• Guide To Visual Management for a Lean System
• What is Lean Manufacturing?
• What Is the Fourth Industrial Revolution? Industry 4.0?

LATEST NEWS

• TXM Exhibiting at Australian Manufacturing Week (AMW) 2024
• TXM Lean Solutions Exhibiting at MACH 2024
• Ron Spiteri Departs TXM After 12 Years of Dedication
• TXM Attending Australasian Processing & Packaging Expo 2024
• ISO 18404 Lean Practitioner Online Course 2024

LATEST BLOGS

• Top Five Organisational Structure Mistakes and How to Avoid Them
• A Dream Come True – Luciano’s Japanese Kaizen Study Tour
• How to Manufacture “Manufactured Buildings” Like a Real Manufacturer!
• What is Industry 5.0?

We use essential cookies to make Venngage work. By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.

Manage Cookies

Cookies and similar technologies collect certain information about how you’re using our website. Some of them are essential, and without them you wouldn’t be able to use Venngage. But others are optional, and you get to choose whether we use them or not.

Strictly Necessary Cookies

These cookies are always on, as they’re essential for making Venngage work, and making it safe. Without these cookies, services you’ve asked for can’t be provided.

Show cookie providers

• Google Login

Functionality Cookies

These cookies help us provide enhanced functionality and personalisation, and remember your settings. They may be set by us or by third party providers.

Performance Cookies

These cookies help us analyze how many people are using Venngage, where they come from and how they're using it. If you opt out of these cookies, we can’t get feedback to make Venngage better for you and all our users.

• Google Analytics

Targeting Cookies

These cookies are set by our advertising partners to track your activity and show you relevant Venngage ads on other sites as you browse the internet.

• Google Tag Manager
• Infographics
• Daily Infographics
• Graphic Design
• Graphs and Charts
• Data Visualization
• Human Resources
• Training and Development
• Beginner Guides

Blog Beginner Guides

15+ Fishbone Diagram Examples for Brainstorming Problem Causes

By Danesh Ramuthi , Oct 13, 2023

The fishbone diagram, often referred to as the Ishikawa diagram or cause and effect diagram, is a powerful visualization tool that elucidates the intricate web of contributing factors behind a specific problem or issue. Characterized by its unique bone structure, it places the problem statement at the fish’s head, branching out to the various causes categorized into major segments.

The primary purpose of a fishbone diagram is to break down complex problems into understandable components, enabling team members to efficiently brainstorm and analyze causal relationships, making it indispensable in areas like quality management and root cause analysis.

Whether you’re aiming to delve deep into the causes of climate change or dissect the factors behind a the fishbone diagram provides a clear visual representation, highlighting the cause and effect relationship and underscoring the value of systematic problem solving.

For those eager to harness the potential of this great tool, Venngage offers a robust diagram maker . With customizable fishbone diagram templates , it empowers users to craft their diagrams effortlessly. These templates are meticulously designed to help you place ideas in the appropriate category, ensuring a comprehensive and organized cause and effect analysis.

Click to jump ahead:

Root cause fishbone diagram example

Cause and effect fishbone diagram example, ishikawa fishbone diagram example, medical fishbone diagram example, climate fishbone diagram example, project management fishbone diagram example, simple fishbone diagram example, how to use a fishbone diagram.

A root cause fishbone diagram, at its core, is a tool specifically tailored to identify, analyze and represent the underlying causes or root causes of a problem. Imagine a scenario where a manufacturing process has a recurring defect. 

In such a scenario, the problem statement or defect would be placed at the fish’s head. As one begins the fishbone analysis, the spine of the fish represents the main flow of the process, with smaller bones branching out. Each of these bones corresponds to a contributing factor or potential cause of the defect.

Utilizing the fishbone diagram for root cause analysis involves gathering team members for a brainstorming session. Here, the group would identify various major categories like “Machinery”, “Manpower”, “Materials”, “Methods”, etc. 

Under each of these categories, multiple factors are explored. For instance, under “Machinery”, potential causes could include outdated equipment, calibration errors or frequent breakdowns. The aim is to determine the root cause, or in some cases, multiple root causes, responsible for the defect. 

The visual representation afforded by the diagram aids in systematically breaking down the problem, ensuring no stone is left unturned.

One of the advantages of using a root cause fishbone diagram is its ability to pinpoint areas that might otherwise be overlooked. It offers a structured approach, helping teams avoid short-term fixes and instead address the deeper, underlying issues. However, it’s crucial to be aware of its disadvantages too. 

The success of the diagram heavily relies on the expertise and insights of the team members. If not all possible causes are considered, the analysis may be incomplete, leading to erroneous conclusions.

The cause and effect fishbone diagram is primarily used to map out the various causes contributing to a specific effect or outcome. For instance, consider a problem statement like “Decreased Sales in Quarter 3”. 

Placed at the head of the fish, this statement becomes the focal point of the analysis. The spine extends outwards, branching into multiple categories that could be influencing this decline.

Starting with a brainstorming session, team members can identify major categories such as “Marketing”, “Product Quality”, “External Factors”, and “Customer Service”. Under “Marketing”, for example, potential causes could be insufficient advertising, poor social media engagement, or ineffective promotional campaigns. 

The aim is to capture all the possible causes contributing to the decline in sales. Through the fishbone diagram’s structured format, teams can effectively map out the causal relationships, understanding how various factors interplay and lead to the overarching problem.

Using the cause and effect fishbone diagram offers a comprehensive overview, helping businesses or teams strategize effectively. They can prioritize areas that need urgent attention and develop strategies for improvement. 

However, like all tools, it has its disadvantages. It requires thoroughness and can become convoluted if too many minor issues are included. Thus, it’s essential to keep the diagram focused on significant, impactful causes to maintain its efficacy as a problem-solving tool.

The Ishikawa fishbone diagram or just fishbone diagram, named after its creator Kaoru Ishikawa, is a powerful visualization tool designed to map out causal relationships concerning a particular problem or issue. Its unique design, reminiscent of a fish’s skeletal structure, places the primary problem or effect at the fish’s head.

From this focal point, the “spine” of the fish extends, leading to branching “bones.” Each branch represents a category or a group of potential contributing factors that lead to the main problem. Often used in root cause analysis and quality management, the Ishikawa diagram breaks down complex issues by categorizing them into major areas such as “People”, “Processes”, “Environment” and more.

This structure allows for an organized exploration of potential causes, ensuring that various perspectives and elements related to the problem are considered.

By facilitating systematic identification and categorization of causes, the Ishikawa fishbone diagram becomes an essential tool in problem-solving and decision-making processes.

In the medical realm, the fishbone diagram finds a specialized application, offering clinicians a structured format to diagnose and understand patient conditions.

Given the critical nature of healthcare, pinpointing the root causes of medical symptoms or conditions becomes paramount. A medical fishbone diagram aids in this by visualizing potential causes related to a specific medical problem or symptom. Categories in a medical context might include “Laboratory Results”, “Patient History”, “Physical Examination Findings” and “Environmental Factors”.

Under each category, various factors or sub-causes can be listed. For instance, “Laboratory Results” could delve into specifics like electrolyte imbalances or abnormal blood cell counts.

The diagram’s visual representation ensures that healthcare professionals can comprehensively analyze patient conditions, considering multiple facets before determining a diagnosis or treatment plan. This systematic approach fosters enhanced patient care and promotes more accurate diagnostic processes.

Designed for meticulous cause and effect analysis, this fishbone diagram delves into the complex problems associated with climate change. Its visual representation, characteristic of the fish’s skeletal structure, places the overarching problem statement — for instance, “Global Warming” — at the fish’s head. From here, multiple categories branch out, representing major aspects such as “Anthropogenic Activities”, “Natural Causes” and “Economic Factors”. 

Each of these major categories further branches out to depict the specific factors contributing to the primary problem. 

The strength of the climate fishbone diagram lies in its ability to present a comprehensive overview, ensuring that all potential causes, whether they relate to deforestation, industrial emissions, or natural volcanic activities, are captured and analyzed. 

It serves as a visualization tool that aids researchers and decision-makers in crafting informed and effective strategies to combat climate-induced challenges.

In project management, where precision and systematic problem solving are paramount, the fishbone diagram finds significant utility. Project delays, cost overruns and unmet objectives often have multifaceted root causes. 

The project management fishbone diagram, an adaptation of the Ishikawa diagram, serves to identify, categorize and analyze these causes. 

Each category delineates into specific contributing factors, ensuring a thorough exploration of all potential issues. The visual format of the diagram aids team members during brainstorming sessions, facilitating the identification of challenges within the project lifecycle. 

By offering a clear visual representation of the cause and effect relationships inherent in project challenges, the project management fishbone diagram stands as an invaluable tool, helping teams to preemptively address issues, optimize processes and enhance overall project execution.

Related: How to Write a Comprehensive Project Management Plan [+ Examples]

For problems that may not be as intricate but still require structured analysis, a simple fishbone diagram becomes the tool of choice. Stripped of excessive categories and branches, the simple fishbone diagram focuses on presenting the main causes of a problem in a straightforward manner. 

Despite its simplicity, the core structure remains consistent: the primary issue or problem statement occupies the fish’s head, while a few major categories branch out from the central spine. This diagram’s strength lies in its accessibility; without delving into overly detailed branches, it offers a clear, concise visualization of the root causes and contributing factors. 

It’s particularly beneficial for quick brainstorming sessions or when introducing the concept of cause and effect analysis to those unfamiliar with the fishbone methodology. 

The simple fishbone diagram, while not exhaustive, provides a foundational framework, promoting structured thought and problem-solving in various contexts.

A fishbone diagram , also known as an Ishikawa or cause and effect diagram, provides a visual representation of potential causes leading to a particular problem or effect. 

It is a structured brainstorming tool that helps teams identify, explore and visually display the many potential causes related to a specific problem.

• Begin your fishbone diagram with the problem statement or the main effect you’re trying to understand. This is written on the right side and represents the fish’s head.
• Draw a horizontal line extending from the problem statement towards the left. This is the fish’s spine and serves as a foundation for the potential causes.
• Identify the major categories of causes. Common categories include “People”, “Processes”, “Equipment”, “Materials” and others, depending on the context. These are the primary bones branching off the central spine.
• Draw diagonal lines or “fishbones” branching off the spine for each major category.
• Under each major category, brainstorm and list down the potential contributing factors or sub-causes. These represent the smaller bones branching out from the primary bones.
• Connect these sub-causes to the respective major category lines using smaller diagonal lines.
• For causes that may have sub-components or more detailed breakdowns, further branch out from the main cause.
• Make sure to clearly label each cause and sub-cause for clarity.
• After the brainstorming session, analyze the diagram to determine the most likely root causes of the problem.
• Once complete, your fishbone diagram should offer a comprehensive visual overview of all the potential causes leading to the main problem. This structure enables teams to better understand the problem, prioritize potential causes and develop effective solutions or interventions.

Related: 10+ Types of Diagrams and How to Choose the Right One

We explored over 15 examples of fishbone diagrams to help you effectively brainstorm the causes of problems. 

This tool, with its visually intuitive structure, serves as a game-changer in analyzing root causes across various fields, from business challenges to technological snags. 

This article doesn’t just present examples but also educates readers on how to harness the power of the fishbone diagram to its fullest. 

For anyone inspired to create their own or seeking specialized templates, Venngage stands out as a go-to resource.

Explore Venngage’s diagram maker and discover an array of pre-designed fishbone diagram templates to kickstart your brainstorming sessions.

Advisory boards aren’t only for executives. Join the LogRocket Content Advisory Board today →

• Product Management
• Solve User-Reported Issues
• Find Issues Faster
• Optimize Conversion and Adoption

Cause and effect analysis with a fishbone (Ishikawa) diagram

Imagine you have been tasked with solving a problem: customers are experiencing lag while attempting to check out from their carts. Specifically, the app takes two minutes to transition from the cart page to the payment page once a customer clicks Continue .

What would you do? The first question that comes to mind is “why,” right? To answer this question, you’ll need to identify all the steps that customers take when checking out, and then assess how each step is performing. Together, these answers will enable you to determine the exact point in the checkout process where the problem is occurring.

This is called “root cause analysis” — you tried to list all the possibilities that could have created this problem. And out of all possibilities, you found which likely created the problem.

Let’s refer to the problem as the “effect,” and all the potential causes you identified during your analysis as the “causes.” Now, imagine trying to represent this cause-and-effect analysis visually. What types of diagrams could you create?

Maybe a tree whose roots are the effect and all the branches as the cause(s). Or maybe an Excel table listing all the causes and sub-causes in columns. Those are all good options, but in this article, we’ll discuss a cause-and-effect diagram (also called a fishbone diagram or Ishikawa diagram).

What is a fishbone diagram?

To start, a fishbone diagram (or Ishikawa diagram) is a tool to visually explore and represent the possible causes of an effect. The tool helps in identifying the potential causes that could have caused the problem.

A sample fishbone diagram looks like this:

It is called a fishbone as it looks like the skeleton of a fish. The head of the fish explains the problem statement (or the effect) and the bones attached explain the possible cause and sub-causes.

The history behind fishbone diagrams

Although the early history of fishbone analysis is slightly unclear, fishbone diagrams are believed to have been in use since the 1920s. However, it was during the 1960s that the diagram gained widespread popularity, thanks to the work of Dr. Kaoru Ishikawa on quality management processes for Kawasaki Shipyards.

It’s believed that Ishikawa first presented the fishbone analysis method in 1945, as part of the development of a company-wide quality control process. The creation of quality improvement processes and tools, along with the introduction of quality circles, played a significant role in the evolution of the concept of total quality management. The Ishikawa diagram became recognized as one of the seven basic quality tools.

When to use a fishbone diagram

The purpose of the fishbone diagram is to identify all the root causes of a problem. You can use fishbone analysis in product development — let’s list a few cases where you should use fishbone analysis:

• When you have to identify the possible causes of a problem
• When you have to develop a feature or product to fix the cause of a problem. This is a reverse analysis where business analysts find the gap in market need and fill that gap with a product or feature
• When evaluating a business process to find loopholes or gaps that create problems
• When you’re defining a process for quality control. Evaluate and find the current gap in quality and build processes to fill it

You can apply the fishbone analysis tool to most applications that need an establishment of quality control and management.

Now, we’ll go over the fishbone diagram and how you can apply it to multiple industries. Most businesses fall into one of these operation areas: services, manufacturing, and marketing, each of which can use a different fishbone diagram. While manufacturing may not be directly relevant to digital products, the fishbone diagram can still be a useful tool for uncovering problems and identifying potential causes. You can modify them accordingly to fit the context of your product.

Let’s start with the 4 Ws: what, why, when, and where. Applying these will help you find the possible potential causes for any effect. This is a good way to brainstorm and all fishbone diagrams must start with these, regardless of the industry you’re in. The 4 Ws are:

• What? There will be materials, products, lines of code, and other resources involved in the problem creation. Ask “what?” to help to pinpoint the specific components or resources that may be contributing to the issue
• Why? There will be situations or conditions that lead to the problem. Asking “why?” may help to uncover factors such as network failure, temperature, weather conditions, or other external considerations that may be impacting the system
• When? There will be a moment when a particular problem occurs. Ask “when?” to find out the time the problem occurs and figure out if it’s a recurring or isolated incident
• Where? Asking this question can help to identify specific areas, such as during the checkout process, a different part of the application, or within a specific context where the issue is most prominent.

Many businesses in the service industry indeed share similarities when it comes to cause analysis in their operational areas. Specifically, the 5 S’s (systems, suppliers, surroundings, safety, and skills) can be applied to cause and effect analysis within the service business.

Over 200k developers and product managers use LogRocket to create better digital experiences

While all service businesses don’t need to conduct a complete cause analysis using the 5 S’s, many find that these principles can be applied at the initial levels and then gradually approached more thoroughly as they identify potential causes within their unique environment:

Systems are the methods, policies, processes, products, and tools used to build operational excellence and provide service without any failure.

Suppliers are any issues in delivering the service itself, like lower quality of service, failure to support customers, delay in refunding payments, agents or vendors delay, and more.

Surroundings are any external factors such as market, competition, public relations, brand value/image, etc. that may contribute to the issue.

Skills focus on finding issues in training, qualifications, skill set, and the experience of employees providing the service.

Safety focuses on finding issues in the system’s overall safety, products, operational procedures, and work environment.

Though the 6 Ms apply mainly to the manufacturing industry, you can transfer this framework into the software industry as well. Since digital products don’t have physical parts, not all of them will be relevant, but we’ll highlight them anyway:

Material focuses on finding issues in any raw materials used for manufacturing. This includes issues with the quantity or quality of supplies, any issues with the timeline of procurement and supply, and more.

Method focuses on finding issues in processes, policies, regulations, training, and guidelines used by companies. Though this is relevant to manufacturing physical goods, these apply to digital products as well (in context).

Machine focuses on finding issues in machines that are used in manufacturing (production). This will help uncover any issues with the maintenance of machines, any failures in the machine or assembly line, etc.

Mother nature , aka the environment, focuses on finding issues in environmental conditions. For physical goods, this could mean issues with temperature, light conditions, etc. For digital products, this could mean issues with servers going down, weather causing latency problems, and more.

Manpower (aka people) focuses on finding issues in the workforce. This means any issues with the work itself, employee burnout, training and skill sets, and more.

Measurement focuses on finding issues in measuring the process and results. This is huge in any business, as metrics and measuring success are vital to the health of a company. Use this to find any issues in quality readings, calculations, and more.

There are 7 Ps that can be commonly applied in cause analysis. These are all related to marketing businesses, but nearly all physical and digital products have marketing functions that affect their product and that this can apply to:

People focuses on finding issues in people involved in marketing a product or service to customers. This implies issues with not targeting the right audience or marketers not having a good understanding of the product.

Product is focused on finding issues in the product or service of an organization. This could be several things, including the perceived image of the product , issues with availability to reach customers, or failure to meet customer needs .

Process works on finding issues in procedures for promoting and marketing the product or service. Are there any gaps in cross-functional team collaboration ? Are they any issues with the escalation matrix?

Price is a big one. This is where to uncover issues in the pricing of the product or service. Is the price too low? Maybe it’s too high? Are there any issues with the price range not matching the competition or with accepting certain payment methods?

Promotion focuses on finding issues in promotion methods, mediums, and strategies. Are social media advertisements reaching the right audience? Is it generating enough clicks?

Place identifies problems with the location of your product. Are there any issues with the availability of your product on particular devices?

Physical evidence is the last of the Ps. It focuses on finding issues in the direct visibility of your product or service. If it has a physical component, is there a problem with the packaging? Physical evidence literally implies any physical issues with the product getting into the hands of customers.

Advantages and disadvantages of fishbone diagrams

There are many advantages you carry when you use a fishbone diagram as a tool for your cause analysis, including:

• Simplicity : the visual representation is simple and easy to understand. Anyone who understands the problem can easily go through all the possible causes of that problem
• Flexibility : you can dissect the cause into sub-causes and go deeper to find the cause
• Associativity : any cause becomes a potential candidate to generate the effect. The relationship with the problem is tightly defined, helping you conclude your analysis
• Ease of use : it’s easy to brainstorm with a team and explain how to use the diagram. Everyone can instantly adapt and be involved in a brainstorm
• Fast : it helps you analyze the root causes quickly by applying the 5 Why’s and drill down potential causes
• Prioritization : visual representation helps you to prioritize your causes and narrow down the most important ones

There are also a few limitations that can make fishbone diagrams difficult to use, including:

• Causes may not be as relevant as you once thought. This could lead to confusion on the path forward or create another problem by accident
• If oversimplified, the fishbone analysis may not uncover what you’re looking for
• There’s potential to prioritize smaller causes over critical ones. Since prioritization is so easy, the team may focus on small causes and waste time in fixing them
• The more dissection into sub-clauses you do leads to more complex diagrams. These may eventually become messy and difficult to understand
• The analysis is mostly based on understanding and brainstorming. It needs additional evaluation of the cause, which in case all possibilities have to be evaluated, can become inefficient and time-consuming

Fishbone diagram template

If you’d like a fishbone diagram template to work with, you can download this one I made on Google Sheets . Feel free to make a copy of it and customize it for your own use.

If you’d like to try to create a fishbone diagram yourself for your own team and organization, here are some common steps to make and analyze it:

• Identify and write the effect (problem statement) as the fish head
• Brainstorm and identify major causes. Write a major cause on each side bone. These major causes can be the Ms, Ps, or S’s with regard to the industry you’re in, or a combination of multiple
• Brainstorm and identify sub-causes. Write the sub-cause on each smaller bone
• Check for completeness. Evaluate or review for too few causes or narrow it down if you have too many
• Analyze each potential cause to narrow it down further. The goal is to end up with one or more that need to be fixed
• Prioritize the potential cause based on its severity on the effect

Let’s draw the fishbone diagram for a digital product. We’ll use the problem we listed at the beginning where customers are facing problems during the checkout process:

While this list may not be comprehensive, it does cover many potential causes that could lead to delays in opening the payments page. It’s important to note that during a brainstorming session, many potential causes can arise, but it’s important to focus on the most likely causes to address first. In this case, we’ve highlighted a sub-cause in red that represents the result of the analysis and the area that should be addressed.

How product managers can use fishbone diagrams

There are many cases where product managers have to analyze the cause of a problem, and a fishbone diagram is a powerful tool for product managers to benefit from. Its easy and quick creation helps quickly narrow down potential causes and act upon them.

A few examples where product managers can make use of fishbone diagram are:

• Finding the root cause for a reduction in feature usage
• Finding the root cause of churn
• Learn the effects of new features on the application upfront
• Analyze what the team should focus on while prioritizing enhancements for a feature
• Presenting the quality measures taken on certain features to senior management

The process type fishbone diagram

A not-so-popular and not-so-in-use flavor for creating fishbone diagrams is the process-type fishbone diagram. It’s very similar but has a small change in the drawing:

The main bone of the fish is divided into multiple cause areas. Team brainstorms potential causes that could have created the problem in each of these areas. It is called process type because each area in the main bone (mostly) represents a process, but each area in the main bone also represents a department. Causes are explored in the process of each department as a result.

These diagrams are not that popular but are an efficient way to involve multiple cross-functional teams from various departments.

Kaoru Ishikawa popularized the fishbone diagram to analyze the root cause of any problem. It is also called the Ishikawa diagram or cause and effect diagram.

One can use the 4 Ws — what, why, when, and where — to begin cause analysis. Based on industry type, there are common areas of cause analysis: the 5 S’ for services, 6 Ms for manufacturing, and 7 Ps for marketing. If your company or product has a combination of these, you can create multiple fishbone diagrams to get to the root cause of your issue.

Featured image source: IconScout

LogRocket generates product insights that lead to meaningful action

Get your teams on the same page — try LogRocket today.

Share this:

• Click to share on Twitter (Opens in new window)
• Click to share on Reddit (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)
• #product strategy

Stop guessing about your digital experience with LogRocket

Recent posts:.

Leader Spotlight: The importance of challenging assumptions, with Alex Swain

Alex Swain talks about how the key to avoiding building a product that nobody will purchase is to always challenge assumptions.

How to use the PR/FAQ method to drive product innovation

The PR/FAQ method helps you clarify your vision, communicate your strategy, validate your assumptions, and solicit feedback from others.

Leader Spotlight: The nuances of quality localization, with Drew Wrangles

Drew Wrangles, Head of Product & Design at Taskrabbit, shares his experiences leading product localization.

Techniques for gaining insights from customers

A deep understanding of your customers helps you prioritize problems, define solutions, and adjust communications.

Leave a Reply Cancel reply

7 Steps to a Fishbone Diagram and to Identifying Those Causes

Often referred to as a cause and effect diagram, or Ishikawa, it is a simple root cause analysis tool that is used for brainstorming issues and causes of particular problems and can and often is used in conjunction with the 5 Whys tool.

In a fishbone diagram, the various causes are grouped into categories and the causes cascade from the main categories, flowing towards the effect, forming what resembles a fishbone appearance.

The prime remit is to brainstorm all the possibilities that could cause the problem and then drill down to the factor(s) that are causing this issue. Once found, eliminate them. It enables the team to focus on why the problem occurs, and not on the history or symptoms of the problem, or other topics that digress from the intent of the session. It also displays a real-time ‘snap-shot’ of the collective inputs of the team as it is updated.

How to Conduct a Fishbone Diagram

Draw the box on the right of a flip chart or large dry wipe board, and write the problem statement in the box. Be as clear and specific as you can about the problem.

Now draw the line going from left to right as the ‘Spine’, connecting to the problem statement.

Draw the ‘fishbones’ emanating from the spine. These represent the main cause categories.

Now label each Fishbone category. There are two options here. You can use the generic cause categories of People, Method, Machine, Material, Environment, which is easier to use for a group that is relatively new to this exercise, or you can brainstorm the major categories related to the specific problem.

Now brainstorm all the causes to the problem. You could use the approach of writing each cause on post it notes, going around the group asking each person for one cause. Continue going through the rounds, getting more causes, until all ideas are exhausted.

For each cause, agree in the group which category the issue should fall in. (An issue can fall in a number of categories) and continue this process until the group have run out of ideas.

• Next, get each individual in the team in turn, to put a tally mark against the top three causes they think affect the problem. You can use supporting data to help you decide, if it is available.
• Once completed, the facilitator adds up all the tallies for each cause and selects the top three with the highest scores. These three issues will now form the basis of additional investigation in order to find the root cause. The team may then investigate these causes further and use problem-solving techniques like 5 Whys to eliminate their occurrences.

An example Fishbone Diagram

The group in the example below, had a problem with excessive scrap. They then got a cross functional team together to understand possible reasons, listing each possible cause into categories.

The next step would be to pick the top three causes and delve deeper to find the true root causes.

A Few Tips Along the Way

1. Remember, as with any task-based activity, always close the session off with actions and owners – “Who is doing what by when?” This is important, as it keeps the teams focused on the project.

2. Hold people accountable and summarise the event, including the actions and deliverables to take away.

3. Have regular reviews with the team in between events, checking for status against the action plan, and work ways of getting tasks back on track if they are falling behind schedule. Keep on top of everything!

4. Leave every task and bit of information clear and concise, so the team understands what is expected of them.

5. As a part of Visual Management, why not create and place a number of large Problem solving boards around the shop floor or in the office. Get the teams to start identifying day to day issues, using QCPC charts and then running quick problem solving sessions, using fishbone diagrams and 5 whys together, 3 times a month for the highest turnbacks on these QCPC charts. You will systematically be embedding a problem solving and continuous improvement culture without even knowing it!

Other Related Articles

• Kepner Tregoe Problem solving
• Six Sigma Tools
• Consensus Decision making
• Lean Manufacturing Principles
• 5 Step Approach
• Failure Mode effects Analysis (FMEA)
• 8D Problem Solving