Browse Definitions :
Definition

fishbone diagram (Ishikawa cause and effect)

Contributor(s): Sarah Lewis

A fishbone diagram, also called a cause and effect diagram or Ishikawa diagram, is a visualization tool for categorizing the potential causes of a problem in order to identify its root causes. Typically used for root cause analysis, a fishbone diagram combines the practice of brainstorming with a type of mind map template.

A fishbone diagram is useful in product development and troubleshooting processes to focus conversation. After the group has brainstormed all the possible causes for a problem, the facilitator helps the group to rate the potential causes according to their level of importance and diagram a hierarchy. The design of the diagram looks much like a skeleton of a fish. Fishbone diagrams are typically worked right to left, with each large "bone" of the fish branching out to include smaller bones containing more detail.

Dr. Kaoru Ishikawa, a Japanese quality control expert, is credited with inventing the fishbone diagram to help employees avoid solutions that merely address the symptoms of a much larger problem. Fishbone diagrams are considered one of the seven basic quality tools and are used in the "analyze" phase of Six Sigma's DMAIC (define, measure, analyze, improve, control) approach to problem solving.

How to create a fishbone diagram

Fishbone diagrams are typically made during a team meeting and drawn on a flipchart or whiteboard. Once a problem that needs to be studied further is identified, teams can take the following steps to create the diagram:

  1. The head of the fish is created by listing the problem in a statement format and drawing a box around it. A horizontal arrow is then drawn across the page with an arrow pointing to the head, this acts as the backbone of the fish.
  2. Then at least four overarching “causes” are identified that might contribute to the problem. Some generic categories to start with may include methods, skills, equipment, people, materials, environment or measurements. These causes are then drawn to branch off from the spine with arrows, making the first bones of the fish.
  3. For each overarching cause, team members should brainstorm any supporting information that may contribute to it. This typically involves some sort of questioning method, such as the 5 Whys or the 4P’s (Policies, Procedures, People and Plant) to keep the conversation focused. These contributing factors are written down to branch off their corresponding cause.
  4. This process of breaking down each cause is continued until the root causes to the problem have been identified. The team then analyzes the diagram until an outcome and next steps are agreed upon.

Example of a fishbone diagram

The following graphic is an example of a fishbone diagram with the problem “Website went down.” Two of the overarching causes have been identified as “Unable to connect to server” and “DNS lookup problem” with further contributing factors branching off.

Example of a fishbone diagram
Example of a fishbone diagram

When to use a fishbone diagram

A few reasons a team might want to consider using a fishbone diagram are:

  • To identify the possible causes of a problem.
  • To help develop a product that addresses issues within current market offerings.
  • To reveal bottlenecks or areas of weakness in a business process.
  • To avoid reoccurring issues or employee burnout.
  • To ensure that any corrective actions put into place will resolve the issue.
This was last updated in November 2019

Continue Reading About fishbone diagram (Ishikawa cause and effect)

Join the conversation

8 comments

Send me notifications when other members comment.

Please create a username to comment.

Can someone provide the fishbone diagram please?
Cancel
Why does the fishbone work from left-to-right?
Cancel
If I am correct, its independent of the direction. It will only focus to the problem.
Cancel
Anyone using the Fishbone to produce a sales plan (not identifying problems)? Also, is there any significance as to where the categories feeding the spine are place? i.e. one closest to the head the biggest issue or contribution?
Cancel
When does your organization create fishbone diagrams?
Cancel
Fish bones make you smart, because they are reach in phosporous, which feeds your brain manually. Don't pay attention to all that say negative, because eventually they will try to shut me up with their nonsense stories.
Cancel
The Ishikawa Fishbone Diagram (IFD) is a tool used to identify and present possible root causes to a problem.
Cancel
Very nice and informative details on Fishbone diagram.
Cancel

-ADS BY GOOGLE

File Extensions and File Formats

Powered by:

SearchCompliance

  • risk management

    Risk management is the process of identifying, assessing and controlling threats to an organization's capital and earnings.

  • compliance as a service (CaaS)

    Compliance as a Service (CaaS) is a cloud service service level agreement (SLA) that specified how a managed service provider (...

  • data protection impact assessment (DPIA)

    A data protection impact assessment (DPIA) is a process designed to help organizations determine how data processing systems, ...

SearchSecurity

  • NIST Cybersecurity Framework

    The NIST Cybersecurity Framework (NIST CSF) is a policy framework surrounding IT infrastructure security.

  • Port Scan

    A port scan is a series of messages sent by someone attempting to break into a computer to learn which computer network services ...

  • DMZ (networking)

    In computer networks, a DMZ (demilitarized zone), also sometimes known as a perimeter network or a screened subnetwork, is a ...

SearchHealthIT

SearchDisasterRecovery

  • business continuity plan (BCP)

    A business continuity plan (BCP) is a document that consists of the critical information an organization needs to continue ...

  • disaster recovery team

    A disaster recovery team is a group of individuals focused on planning, implementing, maintaining, auditing and testing an ...

  • cloud insurance

    Cloud insurance is any type of financial or data protection obtained by a cloud service provider. 

SearchStorage

Close