<?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 for Daily Kaizen</title>
	<atom:link href="http://dailykaizen.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://dailykaizen.org</link>
	<description>Just another Dashboard.ghmedicalhome.org site</description>
	<lastBuildDate>Wed, 16 May 2012 20:00:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on All Happy Families by Julie Fox</title>
		<link>http://dailykaizen.org/2012/03/17/all-happy-families/#comment-2438</link>
		<dc:creator>Julie Fox</dc:creator>
		<pubDate>Wed, 16 May 2012 20:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://dailykaizen.org/?p=1245#comment-2438</guid>
		<description>Here in CSP we really don&#039;t have divisional rivalries as what we do is so different from the rest of the Coop, but we are finding interdepartmental rivalries. As we narrow our focus on a few key processes we have people upset that the focus is not on what they perceive to be the most important process.  We have to be careful that the parking lot for ideas doesn&#039;t become a graveyard.</description>
		<content:encoded><![CDATA[<p>Here in CSP we really don&#8217;t have divisional rivalries as what we do is so different from the rest of the Coop, but we are finding interdepartmental rivalries. As we narrow our focus on a few key processes we have people upset that the focus is not on what they perceive to be the most important process.  We have to be careful that the parking lot for ideas doesn&#8217;t become a graveyard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 50% Improvement Today by MindEdge Monthly: Top Blog Picks&#8230;May 2012 &#171; Quality At Work</title>
		<link>http://dailykaizen.org/2012/04/27/50-improvement-today/#comment-2425</link>
		<dc:creator>MindEdge Monthly: Top Blog Picks&#8230;May 2012 &#171; Quality At Work</dc:creator>
		<pubDate>Thu, 03 May 2012 21:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://dailykaizen.org/?p=1251#comment-2425</guid>
		<description>[...] &#8220;50% Improvement Today&#8221; &#8211; Daily Kaizen [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8220;50% Improvement Today&#8221; &#8211; Daily Kaizen [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 50% Improvement Today by Lean Simulations</title>
		<link>http://dailykaizen.org/2012/04/27/50-improvement-today/#comment-2418</link>
		<dc:creator>Lean Simulations</dc:creator>
		<pubDate>Mon, 30 Apr 2012 20:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://dailykaizen.org/?p=1251#comment-2418</guid>
		<description>Just do it. 
This slogan can be bad if you have no direction, but if you have a long term plan or goal, then start with the first step and the rest will follow, one step at a time.</description>
		<content:encoded><![CDATA[<p>Just do it.<br />
This slogan can be bad if you have no direction, but if you have a long term plan or goal, then start with the first step and the rest will follow, one step at a time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 50% Improvement Today by Helga Ding</title>
		<link>http://dailykaizen.org/2012/04/27/50-improvement-today/#comment-2407</link>
		<dc:creator>Helga Ding</dc:creator>
		<pubDate>Fri, 27 Apr 2012 21:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://dailykaizen.org/?p=1251#comment-2407</guid>
		<description>Your reflection got me to thinking about the careful balance (both Lean principles) of going slow to go fast (so we need to assure we do the appropriate root cause thinking and make sure we are addressing the problem that needs to be solved).  Then, implement quickly, even if not perfect, and learn from that implementation.  If you go too quickly before doing the right thinking, you could end up not even coming close to solving the problem. If you hesistate too long to move into implementation (it&#039;s one reason we love our &quot;pilots&quot;), you&#039;ll never learn if your solution gets you closer to your goals.
Thanks Lee, as always.</description>
		<content:encoded><![CDATA[<p>Your reflection got me to thinking about the careful balance (both Lean principles) of going slow to go fast (so we need to assure we do the appropriate root cause thinking and make sure we are addressing the problem that needs to be solved).  Then, implement quickly, even if not perfect, and learn from that implementation.  If you go too quickly before doing the right thinking, you could end up not even coming close to solving the problem. If you hesistate too long to move into implementation (it&#8217;s one reason we love our &#8220;pilots&#8221;), you&#8217;ll never learn if your solution gets you closer to your goals.<br />
Thanks Lee, as always.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Seeing Waste by Chris H</title>
		<link>http://dailykaizen.org/2012/01/11/seeing-waste/#comment-2406</link>
		<dc:creator>Chris H</dc:creator>
		<pubDate>Thu, 19 Apr 2012 03:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://dailykaizen.org/?p=1225#comment-2406</guid>
		<description>Great article thank you for sharing. 

The ability to see waste is a great skill to learn and  is often over looked.

Good luck to Chris in his new job, it sounds like you have your work cut out. 

Showing the wastes as a dollar figure is a good way to motivate management. As all to often they are not interested in the principals. They employ you for that. 

After demonstrating the principals lead to savings, management is usually more supportive.</description>
		<content:encoded><![CDATA[<p>Great article thank you for sharing. </p>
<p>The ability to see waste is a great skill to learn and  is often over looked.</p>
<p>Good luck to Chris in his new job, it sounds like you have your work cut out. </p>
<p>Showing the wastes as a dollar figure is a good way to motivate management. As all to often they are not interested in the principals. They employ you for that. </p>
<p>After demonstrating the principals lead to savings, management is usually more supportive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Solve Your Own Problems by Rob</title>
		<link>http://dailykaizen.org/2011/12/01/solve-your-own-problems/#comment-2169</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Tue, 13 Mar 2012 17:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://dailykaizen.org/?p=1219#comment-2169</guid>
		<description>Many managers that you may come across, probably me included to some extent, incorrectly assumes that if a problem is identified then someone, somewhere will solve it. Unfortunately, problems have a nasty of habit of selecting an organisation rather than the other way round, and the magnitude and importance of a problem is usually a product of both the prevalent systems which exist (or don’t exist) and the culture.

A key question to ask yourself is how many people in your firm can identify these problems and deal with all of them at the same time? I’m going to guess there’s not many. So what’s the solution then?

Generally, firms need to be able to solve many, many more problems, simultaneously than they do now. This will only be achieved by implementing processes that unite people who have the capacity to solve the problem. This is a major omission in the majority of organisations. The result? Root causes may be identified, which may in themselves be correct but the solutions will be ineffective for two reasons:

1. The corrective action is made to fit the problem (which is usually a symptom of some other issue) and is disconnected from the actual identified root cause. The consequence of this is extra resource is thrown at an already broken process, which results in increased waste. What ultimately results from this approach is that the “solution” fades out after a while.

2. The corrective action centres on a, “must do better” mentality. Here extra training is rolled-out or even worse incentives are used. People are asked to try harder, with management help. The outcome is that the original problem isn’t eliminated and demotivation and frustration sets in when it recurs.

The one simple rule I always try is to apply Occam’s razor in finding a solution to a problem: when you have opposing solutions, always choose the easiest and/or simplest until evidence is found that indicates that this way forward isn’t the best.

However, the fundamental issue that is often overlooked is not to wait around for a problem present itself but to make processes, cultures and indeed the entire organisation focused on identifying and preventing problems from occurring in the first place.</description>
		<content:encoded><![CDATA[<p>Many managers that you may come across, probably me included to some extent, incorrectly assumes that if a problem is identified then someone, somewhere will solve it. Unfortunately, problems have a nasty of habit of selecting an organisation rather than the other way round, and the magnitude and importance of a problem is usually a product of both the prevalent systems which exist (or don’t exist) and the culture.</p>
<p>A key question to ask yourself is how many people in your firm can identify these problems and deal with all of them at the same time? I’m going to guess there’s not many. So what’s the solution then?</p>
<p>Generally, firms need to be able to solve many, many more problems, simultaneously than they do now. This will only be achieved by implementing processes that unite people who have the capacity to solve the problem. This is a major omission in the majority of organisations. The result? Root causes may be identified, which may in themselves be correct but the solutions will be ineffective for two reasons:</p>
<p>1. The corrective action is made to fit the problem (which is usually a symptom of some other issue) and is disconnected from the actual identified root cause. The consequence of this is extra resource is thrown at an already broken process, which results in increased waste. What ultimately results from this approach is that the “solution” fades out after a while.</p>
<p>2. The corrective action centres on a, “must do better” mentality. Here extra training is rolled-out or even worse incentives are used. People are asked to try harder, with management help. The outcome is that the original problem isn’t eliminated and demotivation and frustration sets in when it recurs.</p>
<p>The one simple rule I always try is to apply Occam’s razor in finding a solution to a problem: when you have opposing solutions, always choose the easiest and/or simplest until evidence is found that indicates that this way forward isn’t the best.</p>
<p>However, the fundamental issue that is often overlooked is not to wait around for a problem present itself but to make processes, cultures and indeed the entire organisation focused on identifying and preventing problems from occurring in the first place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Hero by Ed Hayes by Jim Byrnes</title>
		<link>http://dailykaizen.org/2012/02/16/the-hero-by-ed-hayes/#comment-2152</link>
		<dc:creator>Jim Byrnes</dc:creator>
		<pubDate>Thu, 08 Mar 2012 18:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://dailykaizen.org/?p=1239#comment-2152</guid>
		<description>This was an excellent description of what I experienced in another organization’s lean transformation.</description>
		<content:encoded><![CDATA[<p>This was an excellent description of what I experienced in another organization’s lean transformation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Hero by Ed Hayes by Jim Byrnes</title>
		<link>http://dailykaizen.org/2012/02/16/the-hero-by-ed-hayes/#comment-2151</link>
		<dc:creator>Jim Byrnes</dc:creator>
		<pubDate>Thu, 08 Mar 2012 18:18:28 +0000</pubDate>
		<guid isPermaLink="false">http://dailykaizen.org/?p=1239#comment-2151</guid>
		<description>This was an excellent description of the Lean Journey to continuous improvement. It was exactly what I experienced in another organization&#039;s lean transformation.</description>
		<content:encoded><![CDATA[<p>This was an excellent description of the Lean Journey to continuous improvement. It was exactly what I experienced in another organization&#8217;s lean transformation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Hero by Ed Hayes by Carrie Barr</title>
		<link>http://dailykaizen.org/2012/02/16/the-hero-by-ed-hayes/#comment-2112</link>
		<dc:creator>Carrie Barr</dc:creator>
		<pubDate>Fri, 17 Feb 2012 20:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://dailykaizen.org/?p=1239#comment-2112</guid>
		<description>Dramatic....much like the Lean life.  Thank you Ed for making sense of it all.  :)</description>
		<content:encoded><![CDATA[<p>Dramatic&#8230;.much like the Lean life.  Thank you Ed for making sense of it all.  <img src='http://dailykaizen.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Stop Selling by Carlos</title>
		<link>http://dailykaizen.org/2006/08/01/stop-selling/#comment-2091</link>
		<dc:creator>Carlos</dc:creator>
		<pubDate>Tue, 07 Feb 2012 16:07:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/archives/118#comment-2091</guid>
		<description>There are cilraenty a lot of details like that to take into consideration. That is a great point to bring up.</description>
		<content:encoded><![CDATA[<p>There are cilraenty a lot of details like that to take into consideration. That is a great point to bring up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

