“Ishikawa Diagram (Cause-and-Effect or Fishbone Diagram)” from Real World Project Management
Perrin, R. (2008). Ishikawa Diagram (Cause-and-Effect or Fishbone Diagram). In Real World Project Management: Beyond Conventional Wisdom, Best Practices, and Project Methodologies (315-323).Hoboken , NJ
Perrin, R. (2008). Ishikawa Diagram (Cause-and-Effect or Fishbone Diagram). In Real World Project Management: Beyond Conventional Wisdom, Best Practices, and Project Methodologies (315-323).
Ishikawa Diagram
Purpose
This article is from a book written for project management professionals and those who are trying to learn and implement project management best practices in the modern workplace.
Strengths and Weaknesses
Strengths
> Users are able to visualize a series of events and see cause-and-effect relationships.
> The process of developing the diagram is educational.
> Cause-and-effect diagrams spur dialogue.
> Ishikawa diagrams can be used for a variety of problems and provide a plan of action.
Weaknesses
> Diagram may turn out too complex if the issue is not well-defined or specific enough.
> Diagram developers must identify enough details to make the end product useful.
Description
Perrin describes the development of an Ishikawa diagram as a five-step process:
Description
Perrin describes the development of an Ishikawa diagram as a five-step process:
1. Define the issue.
2. Identify key factors causing the issue.
3. Identify the causes leading to each factor.
4. Add detail as necessary to describe processes impacting the issue.
5. Review diagram and identify intelligence gaps for further research.
Uses
Ishikawa diagrams are used to investigate processes, and the starting point is usually an evaluation of what Ishikawa referred to as “The Four Ms + E”: methods, machinery, manpower, materials, and environment. The process of developing cause-and-effect diagrams aids in the examination of how each indentified factor contributes positively or negatively to the end result.
Comparison
Perrin describes the method of developing Ishikawa diagrams in a similar manner to Six Sigma Online with a focus on project management; however, he includes references to Ishikawa's original text which increases interest and authority.
Sources Cited
Ishikawa, K. (1968). Guide to Quality Control.Tokyo , Japan
Most Informative
Perrin illustrates the process with a simple sports-related example: the coach of a volleyball team is trying to identify why his team is keeps losing games despite a full roster of skilled athletes. The example is diagrammed step-by-step demonstrating the brainstorming process and making it easy to see the cause-and-effect relationships among various factors.
Source Author
Author Richard Perrin, PMP, CSM, MBB, has more than 30 years of experience working for Fortune 100 and Global 10 companies with a focus on lean business process and quality practices. For the past three years, he has been a coach and trainer for Agile/Scrum processes writing and speaking on project management techniques. His blog, The Project-Ninja!, is available at http://www.project-ninja.com/.
Source Reliability
Very high credibility
Critique Author
Kenda Puchalski, kenda.puchalski@gmail.com, “Mercyhurst College , Erie PA
Uses
Ishikawa diagrams are used to investigate processes, and the starting point is usually an evaluation of what Ishikawa referred to as “The Four Ms + E”: methods, machinery, manpower, materials, and environment. The process of developing cause-and-effect diagrams aids in the examination of how each indentified factor contributes positively or negatively to the end result.
Comparison
Perrin describes the method of developing Ishikawa diagrams in a similar manner to Six Sigma Online with a focus on project management; however, he includes references to Ishikawa's original text which increases interest and authority.
Sources Cited
Ishikawa, K. (1968). Guide to Quality Control.
Most Informative
Perrin illustrates the process with a simple sports-related example: the coach of a volleyball team is trying to identify why his team is keeps losing games despite a full roster of skilled athletes. The example is diagrammed step-by-step demonstrating the brainstorming process and making it easy to see the cause-and-effect relationships among various factors.
Source Author
Author Richard Perrin, PMP, CSM, MBB, has more than 30 years of experience working for Fortune 100 and Global 10 companies with a focus on lean business process and quality practices. For the past three years, he has been a coach and trainer for Agile/Scrum processes writing and speaking on project management techniques. His blog, The Project-Ninja!, is available at http://www.project-ninja.com/.
Source Reliability
Very high credibility
Critique Author
Kenda Puchalski, kenda.puchalski@gmail.com, “
Kenda
ReplyDeleteAfter reading your review of fishbone diagram methodology article, it is interesting to note this methodology is used in Project management. I like the cause and effect methodology of this technique and feel that given the proper inputs can be a very powerful technique for tactical intelligence analysis problems.
Fuad
Kenda,
ReplyDeleteIn doing research for my methodology of causal flow diagramming I found that many tend to place it under the category of RCA (root cause analysis) tools and I frequently find fish bone diagramming and tree structure methods placed under it as well. Both of our tools are mainly used to establish that cause and effect relationship. One difference is that flow diagramming not only can be developed in a tree like structure (root cause leading up to main effect) they can be formed into circular or loop diagrams. It will be interesting to see how each technique performs at developing a clear cause and effect relationship.
Sarah