The fishbone diagram, or the cause and effect diagram, is a simple graphic display that shows all the possible causes of a problem in a business process. It is also called the Ishakawa diagram.
Fishbone diagrams are useful due to how they portray information. There are 4 Main Reasons to use a Fishbone Diagram:
- Display relationships - The fishbone diagram captures the associations and relationships among the potential causes and effects displayed in the diagram. These relationships can be easily understood.
- Show all causes simultaneously - Any cause or causal chain featured on the fishbone diagram could be contributing to the problem. The fishbone diagram illustrates each and every possible cause in an easily comprehendible way; this makes it a great tool for presenting the problem to stakeholders.
- Facilitate brainstorming - The fishbone diagram is a great way to stimulate and structure brainstorming about the causes of the problem because it captures all the causes. Seeing the fishbone diagram may stimulate your team to explore possible solutions to the problems.
- Help maintain team focus - The fishbone framework can keep your team focused as you discuss what data needs to be gathered. It helps ensure that everyone is collecting information in the most efficient and useful way, and that nobody is wasting energy chasing nonexistent problems.
- Six Sigma - Defining the Problem Statement
- Understanding the 7 categories of waste
- The four key approaches of Healthcare Lean Six-Sigma
Subscribe and Share!
Did you enjoy this article? Your feedback is very important! I'd like to invite you to keep up to date with the latest posts from Anticlue. We offer several venues. If you have some questions, help can be found here.- Become a Facebook Fan
- Subscribe to Anticlue
- Follow me on Twitter
- Add to Technorati Favorites
- Digg this post
2 Comments to “4 Reasons to Use Fishbone Diagrams”
Mentioned your excellent blog today at http://betterprojects.jiscinvolve.org/2009/10/21/chaotic-project-management/
Great News! Thank you Paul!



