<?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: Kaizen vs. Kaikaku</title>
	<atom:link href="http://timebackmanagement.com/blog/kaizen-vs-kaikaku/feed/" rel="self" type="application/rss+xml" />
	<link>http://timebackmanagement.com/blog/kaizen-vs-kaikaku/</link>
	<description>Working At The Intersection of Personal Productivity and Lean Manufacturing</description>
	<lastBuildDate>Fri, 30 Jul 2010 18:18:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kevin</title>
		<link>http://timebackmanagement.com/blog/kaizen-vs-kaikaku/comment-page-1/#comment-170</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-170</guid>
		<description>Kaikaku is about getting the basics in place.
Its about getting the workforce to start thinking about what they are supposed to do. Standardising the process.
Without the Kaikaku you are building Kaizen on sandy foundations.
 1.Throw out the traditional concept of manufacturing methods.
2.Think about how the new method will work, not how it won&#039;t work.
3.Don&#039;t accept excuses; totally deny the status quo.
4.Don&#039;t seek perfection; a 50% implementation rate is fine as long as it&#039;s done on the spot.
5.Correct mistakes the moment they are found.
6.Don&#039;t spend money on Kaikaku.
7.Problems give you a chance to use your brains.
8.Ask &quot;Why&quot; five times.
9.Ten person&#039;s ideas are better than one person&#039;s knowledge.
10.Kaikaku knows no limits.
The above 10 commandments are all good basic principles to start any improvement journey.
It is top down initiative to activate a bottom up empowerment for change.</description>
		<content:encoded><![CDATA[<p>Kaikaku is about getting the basics in place.<br />
Its about getting the workforce to start thinking about what they are supposed to do. Standardising the process.<br />
Without the Kaikaku you are building Kaizen on sandy foundations.<br />
 1.Throw out the traditional concept of manufacturing methods.<br />
2.Think about how the new method will work, not how it won&#8217;t work.<br />
3.Don&#8217;t accept excuses; totally deny the status quo.<br />
4.Don&#8217;t seek perfection; a 50% implementation rate is fine as long as it&#8217;s done on the spot.<br />
5.Correct mistakes the moment they are found.<br />
6.Don&#8217;t spend money on Kaikaku.<br />
7.Problems give you a chance to use your brains.<br />
8.Ask &#8220;Why&#8221; five times.<br />
9.Ten person&#8217;s ideas are better than one person&#8217;s knowledge.<br />
10.Kaikaku knows no limits.<br />
The above 10 commandments are all good basic principles to start any improvement journey.<br />
It is top down initiative to activate a bottom up empowerment for change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Ely</title>
		<link>http://timebackmanagement.com/blog/kaizen-vs-kaikaku/comment-page-1/#comment-210</link>
		<dc:creator>Joe Ely</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-210</guid>
		<description>Kaikaku is real though.  It is the Prius.  

Kaizen is the new model of the Camry.

Interstingly, inside Toyota (from what I have observed) kaikaku is not a lot more than focused, stacked-up, on-a-single-topic kaizen...and a lot of kaizen...done in a hurry. 

Kaikaku also tends to be a little more top down, than bottom up (which is kaizen).  Strategic rather than tactical.

But, the one thing all of us can do...now...today...is kaizen.  

Did two this morning...it felt good.  </description>
		<content:encoded><![CDATA[<p>Kaikaku is real though.  It is the Prius.  </p>
<p>Kaizen is the new model of the Camry.</p>
<p>Interstingly, inside Toyota (from what I have observed) kaikaku is not a lot more than focused, stacked-up, on-a-single-topic kaizen&#8230;and a lot of kaizen&#8230;done in a hurry. </p>
<p>Kaikaku also tends to be a little more top down, than bottom up (which is kaizen).  Strategic rather than tactical.</p>
<p>But, the one thing all of us can do&#8230;now&#8230;today&#8230;is kaizen.  </p>
<p>Did two this morning&#8230;it felt good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Walker</title>
		<link>http://timebackmanagement.com/blog/kaizen-vs-kaikaku/comment-page-1/#comment-211</link>
		<dc:creator>Tim Walker</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-211</guid>
		<description>Dan -- I may have made this parallel before, but I think the kaizen process for organizations is similar to the &quot;deliberate practice&quot; process for individuals:  the consistent pursuit of improvement via little changes day by day leads to revolutionary results in the long run.

More info on deliberate practice &lt;a href=&quot;http://www.hooversbiz.com/2008/04/14/deliberate-practice-in-the-working-world/&quot;&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Dan &#8212; I may have made this parallel before, but I think the kaizen process for organizations is similar to the &#8220;deliberate practice&#8221; process for individuals:  the consistent pursuit of improvement via little changes day by day leads to revolutionary results in the long run.</p>
<p>More info on deliberate practice <a href="http://www.hooversbiz.com/2008/04/14/deliberate-practice-in-the-working-world/">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Wroblewski</title>
		<link>http://timebackmanagement.com/blog/kaizen-vs-kaikaku/comment-page-1/#comment-212</link>
		<dc:creator>Mike Wroblewski</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-212</guid>
		<description>Cool Post!  I would view it as Kaizen AND Kaikaku.  Both are needed to improve if used in balance.  Beware though, using your example, if you choose both your spouse and the smoking hot blonde.  That would not be wise!</description>
		<content:encoded><![CDATA[<p>Cool Post!  I would view it as Kaizen AND Kaikaku.  Both are needed to improve if used in balance.  Beware though, using your example, if you choose both your spouse and the smoking hot blonde.  That would not be wise!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Cornell</title>
		<link>http://timebackmanagement.com/blog/kaizen-vs-kaikaku/comment-page-1/#comment-219</link>
		<dc:creator>Matthew Cornell</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-219</guid>
		<description>Put another way, evolution vs. revolution?</description>
		<content:encoded><![CDATA[<p>Put another way, evolution vs. revolution?</p>
]]></content:encoded>
	</item>
</channel>
</rss>