0% found this document useful (0 votes)
1K views

Assignment Fish Bone Diagram

The document discusses fishbone diagrams, also known as Ishikawa diagrams or cause-and-effect diagrams. It provides: 1) A brief history of fishbone diagrams and how they are used to systematically list the potential causes that can be attributed to a problem or effect. 2) Steps for creating a fishbone diagram including identifying the central problem, overarching causes, and contributing factors through brainstorming. 3) An example fishbone diagram showing causes like "Unable to connect to server" branching from the problem "Website went down". 4) Contexts where fishbone diagrams are useful like identifying problems, weaknesses, and avoiding reoccurring issues.

Uploaded by

shahenshah
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
1K views

Assignment Fish Bone Diagram

The document discusses fishbone diagrams, also known as Ishikawa diagrams or cause-and-effect diagrams. It provides: 1) A brief history of fishbone diagrams and how they are used to systematically list the potential causes that can be attributed to a problem or effect. 2) Steps for creating a fishbone diagram including identifying the central problem, overarching causes, and contributing factors through brainstorming. 3) An example fishbone diagram showing causes like "Unable to connect to server" branching from the problem "Website went down". 4) Contexts where fishbone diagrams are useful like identifying problems, weaknesses, and avoiding reoccurring issues.

Uploaded by

shahenshah
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

FISH BONE DIAGRAM/CAUSE-EFFECT DIAGRAM

Submitted By:

Student ID:

DEPARTMENT OF STATISTICS

Submitted To: Prof. Dr. Umair Khalil

Assignment No. 02

Course: Statistical Quality Control

Abdul Wali Khan University, Mardan


CAUSE EFFECT DIAGRAM/FISH BONE DIAGRAM OR ISHIKAWA DIAGRAM

Cause-and-effect diagrams were developed by Kaoru Ishikawa of Tokyo University in 1943 and thus are
often called Ishikawa Diagrams. They are also known as fishbone diagrams because of their appearance
(in the plotted form). Cause-and-effect diagrams are used to list systematically the different causes that
can be attributed to a problem (or an effect). A cause-and-effect diagram can aid in identifying the reasons
why a process goes out of control. As such, they should be part of the PLAN stage of the PDCA
CIRCLE.

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.

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.

Fish Bone /Cause-effect Diagra Exaple from Manufacturing Industry:

Fish Bone /Cause-effect Diagra Exaple from Service Industry:


Fish Bone Diagram Depicting The Root Causes for Long Queues
Fish Bone /Cause-effect Diagra Exaple from Marketing Industry:

A Fish Bone Diagram for the analysis of Order Fulfillment:

A Fish Bone Diagram for The Poor Quality Product:


A Fish Bone Diagram for the Food Wastage:

You might also like