<?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: Why Doesn&#8217;t Daily Kaizen Happen?</title>
	<atom:link href="http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/feed/" rel="self" type="application/rss+xml" />
	<link>http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/</link>
	<description>Thoughts and insights from the shop floor.</description>
	<lastBuildDate>Wed, 08 Feb 2012 00:11:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: The Essential Lean Blogosphere of 2008 &#124; learnsigma</title>
		<link>http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/comment-page-1/#comment-18217</link>
		<dc:creator>The Essential Lean Blogosphere of 2008 &#124; learnsigma</dc:creator>
		<pubDate>Sat, 17 Jan 2009 14:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/#comment-18217</guid>
		<description>[...] doing kaizen. That may be part of the answer to the question by Mark Rosenthal at the Lean Thinker, Why Doesn&#8217;t Daily Kaizen Happen? Speaking of which, Ted Eytan at Daily Kaizen gives practical advice on his Guide to Bringing Your [...]</description>
		<content:encoded><![CDATA[<p>[...] doing kaizen. That may be part of the answer to the question by Mark Rosenthal at the Lean Thinker, Why Doesn&#8217;t Daily Kaizen Happen? Speaking of which, Ted Eytan at Daily Kaizen gives practical advice on his Guide to Bringing Your [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura Colman</title>
		<link>http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/comment-page-1/#comment-9985</link>
		<dc:creator>Laura Colman</dc:creator>
		<pubDate>Sun, 28 Sep 2008 03:18:37 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/#comment-9985</guid>
		<description>Mark, you are sooo right.  My mantra for my own work and for those I coach is &#039;what gets scheduled gets done&#039;.  And I find this works 95% of the time.  I recently started coaching a team who do prepare healthcare claims for processing.  While 80% of claims are received electronically that still leaves a lot of paper to enter sort and enter in the system.  If they don&#039;t get them in system in a timely manner the rest of the processing cycle doesn&#039;t have any chance of making expected processing times.  They were routinely running a backlog of several thousand claims (some weeks old).  So we started by calling any claim they were waiting to process that was over 5 days old a defect.  Every day the team took time to work on the causes of the defects and eliminating those causes.  We started in July and as of today that team is consistently processing 99.9% of their receipts within 2 days.  Thanks for your suggestions.  This stuff works when you actually DO it.  The &#039;Knowing-Doing Gap&#039; is alive and well in most organizations.</description>
		<content:encoded><![CDATA[<p>Mark, you are sooo right.  My mantra for my own work and for those I coach is &#8216;what gets scheduled gets done&#8217;.  And I find this works 95% of the time.  I recently started coaching a team who do prepare healthcare claims for processing.  While 80% of claims are received electronically that still leaves a lot of paper to enter sort and enter in the system.  If they don&#8217;t get them in system in a timely manner the rest of the processing cycle doesn&#8217;t have any chance of making expected processing times.  They were routinely running a backlog of several thousand claims (some weeks old).  So we started by calling any claim they were waiting to process that was over 5 days old a defect.  Every day the team took time to work on the causes of the defects and eliminating those causes.  We started in July and as of today that team is consistently processing 99.9% of their receipts within 2 days.  Thanks for your suggestions.  This stuff works when you actually DO it.  The &#8216;Knowing-Doing Gap&#8217; is alive and well in most organizations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Fernandez</title>
		<link>http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/comment-page-1/#comment-9632</link>
		<dc:creator>Jim Fernandez</dc:creator>
		<pubDate>Wed, 24 Sep 2008 22:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/#comment-9632</guid>
		<description>Mark:

Your right on the button with this.  

I have created 20 6S teams and 20 team leaders. Everyone in the plant is on a team.  I have asked them to have a team meeting every two weeks to discuss improvement ideas.  I go around every two weeks to collect the ideas.  

I asked for a stop work time for 15 minutes every other week for team meetings.  Managemant said no.  Currently the teams have to find the time to meet on their own.

Guess what; I have three teams that are actually having the meetings and coming up with ideas.</description>
		<content:encoded><![CDATA[<p>Mark:</p>
<p>Your right on the button with this.  </p>
<p>I have created 20 6S teams and 20 team leaders. Everyone in the plant is on a team.  I have asked them to have a team meeting every two weeks to discuss improvement ideas.  I go around every two weeks to collect the ideas.  </p>
<p>I asked for a stop work time for 15 minutes every other week for team meetings.  Managemant said no.  Currently the teams have to find the time to meet on their own.</p>
<p>Guess what; I have three teams that are actually having the meetings and coming up with ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/comment-page-1/#comment-9624</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 24 Sep 2008 21:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/#comment-9624</guid>
		<description>Hi Gabriela - 
Thanks for commenting!

Yes, some improvements can be done while the lines are running, but who is supposed to do them? If there is good takt / cycle balance, then the production workers do not have time during the course of their regular work. SOME office / administration tasks are just as busy, others have more slack in them, so in those cases, this is less of an issue.

The main thing is that the workforce cannot become engaged as long as someone else is making all of the improvements on their work.

To be sure, I would fully expect a supervisor or a team leader, if there is an opportunity, to make an improvement when there is time. But if they do so at the expense of missing an opportunity to teach the production team member how to improve their own work, that team member is disempowered in the process, and the number of people who make improvements is reduced by a factor of 5 or 10.

Planning need not be elaborate or cumbersome. It is acknowledging that if I expect someone to do something (in this case, the production workers to make improvements to their own work), then I need to make sure they have the time, resources, skill and guidance to succeed vs. simply telling them &quot;they are empowered&quot; and wishing they would find the time I haven&#039;t allowed them to have.</description>
		<content:encoded><![CDATA[<p>Hi Gabriela &#8211;<br />
Thanks for commenting!</p>
<p>Yes, some improvements can be done while the lines are running, but who is supposed to do them? If there is good takt / cycle balance, then the production workers do not have time during the course of their regular work. SOME office / administration tasks are just as busy, others have more slack in them, so in those cases, this is less of an issue.</p>
<p>The main thing is that the workforce cannot become engaged as long as someone else is making all of the improvements on their work.</p>
<p>To be sure, I would fully expect a supervisor or a team leader, if there is an opportunity, to make an improvement when there is time. But if they do so at the expense of missing an opportunity to teach the production team member how to improve their own work, that team member is disempowered in the process, and the number of people who make improvements is reduced by a factor of 5 or 10.</p>
<p>Planning need not be elaborate or cumbersome. It is acknowledging that if I expect someone to do something (in this case, the production workers to make improvements to their own work), then I need to make sure they have the time, resources, skill and guidance to succeed vs. simply telling them &#8220;they are empowered&#8221; and wishing they would find the time I haven&#8217;t allowed them to have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriela</title>
		<link>http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/comment-page-1/#comment-9606</link>
		<dc:creator>Gabriela</dc:creator>
		<pubDate>Wed, 24 Sep 2008 19:25:31 +0000</pubDate>
		<guid isPermaLink="false">http://theleanthinker.com/2008/09/23/why-doesnt-daily-kaizen-happen/#comment-9606</guid>
		<description>Some improvements can be done while the production lines are running. There is so much to improve and some things can be done on the run, too; we don&#039;t need to always plan, just do it as we have a few minutes. Surely, if it&#039;s more involved, we need to carefully plan for it.
I think sometimes we talk/plan too much and do too little.</description>
		<content:encoded><![CDATA[<p>Some improvements can be done while the production lines are running. There is so much to improve and some things can be done on the run, too; we don&#8217;t need to always plan, just do it as we have a few minutes. Surely, if it&#8217;s more involved, we need to carefully plan for it.<br />
I think sometimes we talk/plan too much and do too little.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

