<?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"
	>
<channel>
	<title>Comments on: Careful what you Measure</title>
	<atom:link href="http://www.dailykaizen.org/archives/140/feed" rel="self" type="application/rss+xml" />
	<link>http://www.dailykaizen.org/archives/140</link>
	<description>A blog about improvement in health care</description>
	<pubDate>Fri, 21 Nov 2008 02:57:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Lee Fried</title>
		<link>http://www.dailykaizen.org/archives/140#comment-74</link>
		<dc:creator>Lee Fried</dc:creator>
		<pubDate>Mon, 04 Sep 2006 23:11:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/archives/140#comment-74</guid>
		<description>Dear Karl,

I appreciate the long comment and really like the the three points. I will use them with my leadership team tomorrow.
 
I think you are absolutely correct, I would take many small improvements any day over the "silver bullet" that often organizations are looking for.  The "small stuff" is not so small to those that are working in the processes and have to deal with the same problems day in and day out.  By empowering and resourcing teams to implement their ideas and fix the problems an organization gets the best return on investment that it could ever ask for: an engaged and high performing culture.  Just don't ask me to measure it!  :)

Thanks for your input,

Lee</description>
		<content:encoded><![CDATA[<p>Dear Karl,</p>
<p>I appreciate the long comment and really like the the three points. I will use them with my leadership team tomorrow.</p>
<p>I think you are absolutely correct, I would take many small improvements any day over the &#8220;silver bullet&#8221; that often organizations are looking for.  The &#8220;small stuff&#8221; is not so small to those that are working in the processes and have to deal with the same problems day in and day out.  By empowering and resourcing teams to implement their ideas and fix the problems an organization gets the best return on investment that it could ever ask for: an engaged and high performing culture.  Just don&#8217;t ask me to measure it!  <img src='http://www.dailykaizen.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thanks for your input,</p>
<p>Lee</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl McCracken</title>
		<link>http://www.dailykaizen.org/archives/140#comment-73</link>
		<dc:creator>Karl McCracken</dc:creator>
		<pubDate>Mon, 04 Sep 2006 20:44:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailykaizen.org/archives/140#comment-73</guid>
		<description>Hi Lee -

I tend to agree - trying to work out ROI on this sort of stuff is generally rather pointless. If Lean is really working, then in addition to the Halleluja Chorus Kaizens, it'll be generating hundreds of tiny improvements a month. Individually, these are probably worth a few dollars here and there, but they add up to a whole bunch of benefit. Because the individual returns are small, an ROI focus would tend to dismiss them as worthless (especially as the cost of working out ROI would have to be met from somewhere . . . ), and you'd end up just doing the big Kaizen events.

Now, a lot of people would like this - afterall, why bother with the small improvements of dubious payback when you can bet on some fully justified and costed winners?

But this is completely missing the point. Three points in fact. Firstly, Lean is about creating a culture of improvement, and to do that, it's essential that people feel empowered to make whatever improvements they can - no matter how small the benefit. Secondly, lots of small improvements have a significant competitive advantage - they're extremely hard to copy, and often, there's a degree of path-dependancy, making them IMPOSSIBLE for competitors to copy. And finally . . . statistically most things do in fact fail. But given an equal probability of failure (say, 99%), it's better to have a hundred low cost improvements of which only one pays back big-time, than trying to engineer out that the odds for that one big project!

That's what I think - and sorry, as I'd intended this to be a nice short reply!

Karl.</description>
		<content:encoded><![CDATA[<p>Hi Lee -</p>
<p>I tend to agree - trying to work out ROI on this sort of stuff is generally rather pointless. If Lean is really working, then in addition to the Halleluja Chorus Kaizens, it&#8217;ll be generating hundreds of tiny improvements a month. Individually, these are probably worth a few dollars here and there, but they add up to a whole bunch of benefit. Because the individual returns are small, an ROI focus would tend to dismiss them as worthless (especially as the cost of working out ROI would have to be met from somewhere . . . ), and you&#8217;d end up just doing the big Kaizen events.</p>
<p>Now, a lot of people would like this - afterall, why bother with the small improvements of dubious payback when you can bet on some fully justified and costed winners?</p>
<p>But this is completely missing the point. Three points in fact. Firstly, Lean is about creating a culture of improvement, and to do that, it&#8217;s essential that people feel empowered to make whatever improvements they can - no matter how small the benefit. Secondly, lots of small improvements have a significant competitive advantage - they&#8217;re extremely hard to copy, and often, there&#8217;s a degree of path-dependancy, making them IMPOSSIBLE for competitors to copy. And finally . . . statistically most things do in fact fail. But given an equal probability of failure (say, 99%), it&#8217;s better to have a hundred low cost improvements of which only one pays back big-time, than trying to engineer out that the odds for that one big project!</p>
<p>That&#8217;s what I think - and sorry, as I&#8217;d intended this to be a nice short reply!</p>
<p>Karl.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
