<?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: 8 Step Problem Solving Method</title>
	<atom:link href="http://www.jamesrick.com/8-step-problem-solving-method/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jamesrick.com/8-step-problem-solving-method/</link>
	<description>Live Your Full Potential</description>
	<lastBuildDate>Sun, 18 Jul 2010 14:39:16 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Xavier manuel Encela</title>
		<link>http://www.jamesrick.com/8-step-problem-solving-method/comment-page-1/#comment-65071</link>
		<dc:creator>Xavier manuel Encela</dc:creator>
		<pubDate>Wed, 19 Aug 2009 12:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://jamesrick.com/blog/?p=114#comment-65071</guid>
		<description>This method is related to scientific method.  Awesome!!!!!!!</description>
		<content:encoded><![CDATA[<p>This method is related to scientific method.  Awesome!!!!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.jamesrick.com/8-step-problem-solving-method/comment-page-1/#comment-58625</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 22 Feb 2009 13:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://jamesrick.com/blog/?p=114#comment-58625</guid>
		<description>Thanks for sharing this useful information.I learned a lot from it.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing this useful information.I learned a lot from it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jivan kumar</title>
		<link>http://www.jamesrick.com/8-step-problem-solving-method/comment-page-1/#comment-54707</link>
		<dc:creator>jivan kumar</dc:creator>
		<pubDate>Tue, 09 Dec 2008 09:53:21 +0000</pubDate>
		<guid isPermaLink="false">http://jamesrick.com/blog/?p=114#comment-54707</guid>
		<description>great tool to be pratise and emphahize ; have helped a lot;

 regrds;

 jivan</description>
		<content:encoded><![CDATA[<p>great tool to be pratise and emphahize ; have helped a lot;</p>
<p> regrds;</p>
<p> jivan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stormy</title>
		<link>http://www.jamesrick.com/8-step-problem-solving-method/comment-page-1/#comment-46686</link>
		<dc:creator>Stormy</dc:creator>
		<pubDate>Wed, 08 Oct 2008 19:02:14 +0000</pubDate>
		<guid isPermaLink="false">http://jamesrick.com/blog/?p=114#comment-46686</guid>
		<description>This is very closely related to the problem solving being used by Toyota Motor Manufacturing.  I have used this method in reference to deep rooted issues and find the resolution to major issues generally involves simple fixes and enhanced communication through the process. The key is doing your homework in step 2 and thoroughly understanding the problem and breaking it down into tangible, bite size portions (don&#039;t try to eat the elephant in one setting!!!).  Do not try to answer the question &quot;why&quot; until step 4.  Then go through the 5 Whys process in stepo 4 to drive down to root cause determination.  Your team will generate a head of steam and tackle the issue in bite size portions as opposed to getting frustrated and yielding minimum results.  This requires time and management support!!!</description>
		<content:encoded><![CDATA[<p>This is very closely related to the problem solving being used by Toyota Motor Manufacturing.  I have used this method in reference to deep rooted issues and find the resolution to major issues generally involves simple fixes and enhanced communication through the process. The key is doing your homework in step 2 and thoroughly understanding the problem and breaking it down into tangible, bite size portions (don&#8217;t try to eat the elephant in one setting!!!).  Do not try to answer the question &#8220;why&#8221; until step 4.  Then go through the 5 Whys process in stepo 4 to drive down to root cause determination.  Your team will generate a head of steam and tackle the issue in bite size portions as opposed to getting frustrated and yielding minimum results.  This requires time and management support!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: website design</title>
		<link>http://www.jamesrick.com/8-step-problem-solving-method/comment-page-1/#comment-28400</link>
		<dc:creator>website design</dc:creator>
		<pubDate>Wed, 11 Jun 2008 16:30:47 +0000</pubDate>
		<guid isPermaLink="false">http://jamesrick.com/blog/?p=114#comment-28400</guid>
		<description>Good information thanks for sending it</description>
		<content:encoded><![CDATA[<p>Good information thanks for sending it</p>
]]></content:encoded>
	</item>
</channel>
</rss>
