<?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: Does Activity = Progress?</title>
	<atom:link href="http://www.dailykaizen.org/archives/95/feed" rel="self" type="application/rss+xml" />
	<link>http://www.dailykaizen.org/archives/95</link>
	<description>A blog about improvement in health care</description>
	<pubDate>Wed, 07 Jan 2009 17:06:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Graban</title>
		<link>http://www.dailykaizen.org/archives/95/comment-page-1#comment-24</link>
		<dc:creator>Mark Graban</dc:creator>
		<pubDate>Thu, 06 Jul 2006 15:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/archives/95#comment-24</guid>
		<description>You're absolutely correct that activity does not equal progress.  I've seen (back in the factory world) many kaizen events that were selected because they were easy or could be completed in a week rather than being problems that really impacted the customer, the employees, or the finances of the organization.  I've seen kaizen activities get very bureaucratic, focusing on the administration of kaizens, rather than focusing on lean.  Some problems are truely complex (such as a laboratory layout) and can't be solved in just one week.  A kaizen event often times sets up an artificial time limit and you end up cutting corners to "get done" rather than getting it done right.

You also have to make sure that kaizen events are done with good solid lean principles in mind.  If the kaizen "solutions" include more batching, for example, that's headed in the completely wrong direction.  You have to engage people, but if their ideas run counter to lean, as the consultant you have to teach them the lean principles and steer them in that direction.

Some in the auto industry thought you could "kaizen your way to lean."  Not so.  Kaizen is just one tool in the lean world.  Once you kaizen bliz an area, how do you keep continuously improving (true kaizen)?  How do you manage things and manage people in a true lean/TPS manner?  Kaizen events won't teach managers how to manage lean and to develop their people on a daily basis.</description>
		<content:encoded><![CDATA[<p>You&#8217;re absolutely correct that activity does not equal progress.  I&#8217;ve seen (back in the factory world) many kaizen events that were selected because they were easy or could be completed in a week rather than being problems that really impacted the customer, the employees, or the finances of the organization.  I&#8217;ve seen kaizen activities get very bureaucratic, focusing on the administration of kaizens, rather than focusing on lean.  Some problems are truely complex (such as a laboratory layout) and can&#8217;t be solved in just one week.  A kaizen event often times sets up an artificial time limit and you end up cutting corners to &#8220;get done&#8221; rather than getting it done right.</p>
<p>You also have to make sure that kaizen events are done with good solid lean principles in mind.  If the kaizen &#8220;solutions&#8221; include more batching, for example, that&#8217;s headed in the completely wrong direction.  You have to engage people, but if their ideas run counter to lean, as the consultant you have to teach them the lean principles and steer them in that direction.</p>
<p>Some in the auto industry thought you could &#8220;kaizen your way to lean.&#8221;  Not so.  Kaizen is just one tool in the lean world.  Once you kaizen bliz an area, how do you keep continuously improving (true kaizen)?  How do you manage things and manage people in a true lean/TPS manner?  Kaizen events won&#8217;t teach managers how to manage lean and to develop their people on a daily basis.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
