Assignment Fish Bone Diagram
Assignment Fish Bone Diagram
Submitted By:
Student ID:
DEPARTMENT OF STATISTICS
Assignment No. 02
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.
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.
A few reasons a team might want to consider using a fishbone diagram are:
To help develop a product that addresses issues within current market offerings.