<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Understanding the Ishikawa diagram	</title>
	<atom:link href="https://creately.com/blog/meeting-visual-collaboration/understanding-the-ishikawa-diagram/feed/" rel="self" type="application/rss+xml" />
	<link>https://creately.com/blog/meeting-visual-collaboration/understanding-the-ishikawa-diagram/</link>
	<description>Latest Product Updates and Tips on Working Visually</description>
	<lastBuildDate>Mon, 05 Jun 2023 08:21:10 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>
		By: jefferysikes		</title>
		<link>https://creately.com/blog/meeting-visual-collaboration/understanding-the-ishikawa-diagram/#comment-45085</link>

		<dc:creator><![CDATA[jefferysikes]]></dc:creator>
		<pubDate>Mon, 30 Mar 2015 15:09:00 +0000</pubDate>
		<guid isPermaLink="false">https://creately.com/blog/?p=4440#comment-45085</guid>

					<description><![CDATA[With over 3 decades of experience, I can honestly say that the Ishikawa diagram is one of the most misunderstood of business management tools, just beneath the most misunderstood, abused and misused, that being Root Cause analysis. 

Perhaps the failure to use these tools properly stems from the misconstrued use of Deming’s PDSA which was change do PDCA.  Both Deming and Ishikawa intended their tools to be useful in studying the variation present in a given process.  They assumed that users would understand that a process is not singular in its function and that it can include many Tasks with each task having the possibility of contain many Actions (or Inactions).  This is why the Ishikawa diagram indicates several possible causes for any one effect.  The idea is not to define a single root cause, because that is most likely not possible related to a complex process of tasks and actions.   The idea is to address all of the possible causes and Study which ones are the most probable contributors to the effect.    

One may never be able to recreate the events which combined together to become the ultimate cause of the event, however with this tool one can discover the most probable common causes of variation, and even determine some special causes of variation and determine if adequate controls are in place to detect the occurrence of the common or special causes of variation identified as a result of the exercise.  

Whatever one decides concerning this tool, its best to avoid the trap of “Root Cause” when using it for solving process issues/problems.]]></description>
			<content:encoded><![CDATA[<p>With over 3 decades of experience, I can honestly say that the Ishikawa diagram is one of the most misunderstood of business management tools, just beneath the most misunderstood, abused and misused, that being Root Cause analysis. </p>
<p>Perhaps the failure to use these tools properly stems from the misconstrued use of Deming’s PDSA which was change do PDCA.  Both Deming and Ishikawa intended their tools to be useful in studying the variation present in a given process.  They assumed that users would understand that a process is not singular in its function and that it can include many Tasks with each task having the possibility of contain many Actions (or Inactions).  This is why the Ishikawa diagram indicates several possible causes for any one effect.  The idea is not to define a single root cause, because that is most likely not possible related to a complex process of tasks and actions.   The idea is to address all of the possible causes and Study which ones are the most probable contributors to the effect.    </p>
<p>One may never be able to recreate the events which combined together to become the ultimate cause of the event, however with this tool one can discover the most probable common causes of variation, and even determine some special causes of variation and determine if adequate controls are in place to detect the occurrence of the common or special causes of variation identified as a result of the exercise.  </p>
<p>Whatever one decides concerning this tool, its best to avoid the trap of “Root Cause” when using it for solving process issues/problems.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
