Writers' Community!
Home Page Two Columnists Q&A Submit an Article FAQs Contact Author Login
Article Submission
We Need YOUR Articles!
We'll Promote Them for FREE!

Author Login

New Authors
Register Here


Now Serving 7,753 Authors
70,419 Quality Articles
& 5,256 Current Users Online!
Featured Authors
Fran Larson (1,867)
Joel Hendon (15,913)
Shari Vaudo (422)
David Tanguay (9,529)
Michael Ramzy (641)
Missing Link (645)
E. Raymond Rock (3,072)
Gregory Lewis (1,665)
Nancy Daniels (1,438)
Mark Parsec (14,913)
Sandra E. Graham (7,796)
David Pekrul (3,696)
Ira Coffin (6,743)
Julian Price (4,285)

View All Featured Authors
Most Recent
Ten Enterprise Performance Management Best Practices - Executing Phase

11 Enterprise Performance Management Best Practices - Planning Phase

Eight Enterprise Performance Management Best Practices - Defining Phase

How to Develop a Performance Metrics Repository That Drives Organizational Success

Secrets of Developing Simple, Powerful Performance Measures That Drive Organizational Success

PRINCE2 Training Myths and Misconceptions

Project Managers, What's Your Competitive Advantage?

Protect Your Business from the Vishing scam

PMP Exam Prep Strategy: Learn By Distinction

I Simply Do Not Get On With the Project Team Member

Home » Categories » Business » Project Management » Root Cause Analysis: Fishbone Diagram and Analysis » Printer Friendly

Daiv Russell

Root Cause Analysis: Fishbone Diagram and Analysis

Rated 3 out of 5
Rated 4.6 by 1 Reader ?
Rate It  /  View Comments  /  View All Articles submitted by Daiv Russell
Submitted Sunday, December 28, 2008
Daiv Russell (3,635)
Daiv Russell

Envision Web Marketing
Log in to become a member of Daiv Russell's Fan Club!


In root cause analysis, the Fishbone diagram can be used to facilitate root cause analysis for a specific problem. The fishbone diagram provides a structured method for identifying and documenting potential root causes during the brainstorming process, encouraging teams to think about a problem in a systematic fashion, digging deeper to discover less obvious root causes.

The fishbone diagram is also known as a cause and effect diagram. In some circles, it is referred to as an Ishikawa diagram, after its innovator, Dr. Kaoru Ishikawa, the Japanese quality control expert. The popular name for this chart, however, "fishbone", stems from the fact that the diagram resembles the skeleton of a fish.

 

The Fishbone Analysis process

Fishbone analysis starts with a problem to be investigated. This problem is written in the form of a question on the right side of the page. An arrow, or sometimes a drawing of a fish head, will point to the question under consideration. To the left of the problem statement, a horizontal line divides the paper in two. This is the "backbone" of the fishbone diagram.

The next set of bones represent major categories of factors that could contribute to the root cause. These category names are written along the top and the bottom of the paper. Angled arrows point back to the backbone and toward the head, forming a herringbone pattern.

Conventions have developed to provide starting categories appropriate for different types of problems domains.
 
  • In manufacturing, the 6 M's are used:
    • Machine,
    • Methods,
    • Materials,
    • Maintenance,
    • Man, and
    • Mother Nature.
  • Modern analysis of manufacturing problems adds categories like:
    • Equipment,
    • Process,
    • People,
    • Materials,
    • Environment, and
    • Management.
  • The 8 P's are a useful starting point for analysis of service and administrative problems:
    • Price,
    • Promotion,
    • People,
    • Processes,
    • Place / Plant,
    • Policies,
    • Procedures, and
    • Product.
  • A service industry business may also use the 4 S's:
    • Surroundings,
    • Suppliers,
    • Systems, and
    • Skills

Once the basic skeletal frame is in place, the fishbone analysis begins by listing factors that contribute to each category of issues that produce the root cause. These are written above arrows that point back to the category line. These lines in turn can have their own lines pointing into them, breaking down factors that contribute to it. This can go on infinitely, but will be difficult to draw beyond a few levels for obvious reasons.

With the skeleton of the fishbone diagram in place a team brainstorms about each category, looking for reasons that produce the end result. Generally, it is good to phrase a problem as a question and ask team members to answer the question in the context of each category. In general, the question is "Why is this happening?" Then, for each category, the question shifts to "How are factors in this category causing this?"

The brainstorming continues until team members can no longer think of useful items to add to the diagram. At this point, the results are analyzed to identify the most likely root causes of the problem. Finding the same issue within multiple categories is a good indication that it is an important root cause in the system. Likewise, areas of the diagram that are densely populated with detail are likely to point to areas of significance.

Daiv Russell is a management consultant with Envision Consulting in Tampa, Florida. Learn more about Fishbone Analysis - Using Ishikawa's Fishbone Diagram for Root Cause analysis.



tweet this!



Reprint Rights

Log in to become a member of Daiv Russell's Fan Club!

Comments on this article: (1 total)


» left by Peter Alfieri (557)
Peter Alfieri
(309 days 13 hours ago.)

Reader Rating: 4 out of 5
Great article! Clearly you are an inspired writer. Some of this was over my head, but I think this was very well written! Keep up the good work!

Respond to this comment

Was this article helpful to you? Leave a Public Comment or Question:

This Article has been viewed 1,304 times.
Article added to SearchWarp.com on 12/28/2008 5:54:09 AM.
View other articles written by Daiv Russell (3,635)
Daiv Russell


If you found this article interesting, you may want to check out:

Disclaimer:  All information on this site is provided for informational purposes only! By no means is any information presented herein intended to substitute for the advice provided to you by any health care or other professional or organization.


Today's Most Popular
Gantt Charts & PERT Charts - How to use these things?

Project Management Training: Strong Matrix Organization Structure

Project Management Training: Balanced Matrix Organization Structure

Statistical Quality Control and Quality Control Charts

Fishbone Analysis Using the Ishikawa Diagram

Project Management Training: Weak Matrix Organization Structure

Root Cause Analysis: Fishbone Diagram and Analysis

Find Your Root Cause With Fishbone Diagrams

Project Management Training: Matrix Organization Structure Origins

History of Project Management: How Did We Get Here?

Viewed from Cache. Load Time: 0.000.

Home  |  Page Two  |  FAQ's  |  Contact  |  Terms of Service  |  Article Submission Guidelines  |  Questions & Answers  |  Privacy  |  Mission / About
Copyright © 1999-2009 SearchWarp.com, All Rights Reserved - SearchWarp.com is an IcoLogic, Inc. Company