Comments on: The Ishikawa Diagram http://www.pmhut.com/the-ishikawa-diagram Thu, 24 May 2012 18:51:30 +0000 http://wordpress.org/?v=abc hourly 1 By: Root Cause Analysis in Project Management - PM Hut http://www.pmhut.com/the-ishikawa-diagram/comment-page-1#comment-13976 Root Cause Analysis in Project Management - PM Hut Thu, 17 Dec 2009 13:38:32 +0000 http://www.pmhut.com/the-ishikawa-diagram#comment-13976 [...] There are many tools available to the project manager embarking on an RCA exercise. Many, such as Pareto analysis, Barrier analysis, and Bayesian inference rely on statistics observed over time that the project manager simply won’t have. Kepner-Tregoe also offer a unique approach to problem solving. They’ve been using this unique approach for over 50 years so it does get results if used properly. Using the Kepner-Tregoe approach requires proper training which is beyond the scope of this article. If you’d like to explore using their approach, I’d recommend taking their course so that you’ll become proficient with their methods. The method I will use in this article is based on the Ishikawa or fishbone diagram. [...] [...] There are many tools available to the project manager embarking on an RCA exercise. Many, such as Pareto analysis, Barrier analysis, and Bayesian inference rely on statistics observed over time that the project manager simply won’t have. Kepner-Tregoe also offer a unique approach to problem solving. They’ve been using this unique approach for over 50 years so it does get results if used properly. Using the Kepner-Tregoe approach requires proper training which is beyond the scope of this article. If you’d like to explore using their approach, I’d recommend taking their course so that you’ll become proficient with their methods. The method I will use in this article is based on the Ishikawa or fishbone diagram. [...]

]]> By: Quality Control in Project Management - PM Hut http://www.pmhut.com/the-ishikawa-diagram/comment-page-1#comment-673 Quality Control in Project Management - PM Hut Sun, 30 Nov 2008 16:53:20 +0000 http://www.pmhut.com/the-ishikawa-diagram#comment-673 [...] Ishikawa Diagrams: these are also known as cause-and-effect diagrams and fishbones, but Ishikawa sounds brainier. The point of these diagrams, regardless of the nomenclature, is to facilitate a conversation on why causes and contributing to a problem. [...] [...] Ishikawa Diagrams: these are also known as cause-and-effect diagrams and fishbones, but Ishikawa sounds brainier. The point of these diagrams, regardless of the nomenclature, is to facilitate a conversation on why causes and contributing to a problem. [...]

]]> By: Michel Operto http://www.pmhut.com/the-ishikawa-diagram/comment-page-1#comment-672 Michel Operto Wed, 23 Apr 2008 15:07:22 +0000 http://www.pmhut.com/the-ishikawa-diagram#comment-672 I like these cause and effect diagrams. They are easy to read even for new comers. I found their usage beneficial when trying to focus a project team on the real root causes rather than addressing the immediate visible symptoms. When associated with a simple problem resolution approach they can be very effective to support the standard 7 steps: 1 Define/scope project/problem 2 Describe current situation - Gather data and team 3 Identify/Analyze/confirm root cause with data 4 Implement (pilot) solutions 5 Evaluate results 6 Standardize effective methods 7 Communicate results / Lessons learned I like these cause and effect diagrams. They are easy to read even for new comers. I found their usage beneficial when trying to focus a project team on the real root causes rather than addressing the immediate visible symptoms.

When associated with a simple problem resolution approach they can be very effective to support the standard 7 steps:
1 Define/scope project/problem
2 Describe current situation - Gather data and team
3 Identify/Analyze/confirm root cause with data
4 Implement (pilot) solutions
5 Evaluate results
6 Standardize effective methods
7 Communicate results / Lessons learned

]]>