<?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: Six Sigma-Love It or Hate It?</title>
	<atom:link href="http://www.sixsigmatraining.org/introduction-to-six-sigma/six-sigma-love-it-or-hate-it.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sixsigmatraining.org/introduction-to-six-sigma/six-sigma-love-it-or-hate-it.html?source=rss</link>
	<description>Lean Six Sigma Training and Information</description>
	<lastBuildDate>Tue, 09 Mar 2010 20:45:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Thomas Pyzdek</title>
		<link>http://www.sixsigmatraining.org/introduction-to-six-sigma/six-sigma-love-it-or-hate-it.html/comment-page-1#comment-25</link>
		<dc:creator>Thomas Pyzdek</dc:creator>
		<pubDate>Wed, 17 Jun 2009 14:45:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.sixsigmatraining.org/?p=1546#comment-25</guid>
		<description>I received this response to this posting from LinkedIn:
&quot;While I agree with much of your perspective, I take exception to the the statement that R&amp;D is inherently and unavoidably wasteful. Waste is defined by its economic value. A well planned well executed and effectively analyzed experiment has value, even if the intended result is not achieved. The learning acquired has value. To call this waste invites and reinforces the often cited conflict between corporate leadership and R&amp;D.&quot;

Here&#039;s my response:

A rose by any other name...

I think we need to call a spade a spade here and work to change management&#039;s misconception. When &quot;the intended result is not achieved&quot; most people call this failure and view the expended resources as waste. Why not just admit that such outcomes are an inherent part of the discovery process and learn to deal with it? Six Sigma, lean and quality aren&#039;t the only evidence of management&#039;s abhorrence of waste, it&#039;s an integral part of management. The conflict between management and R&amp;D is largely due to the ambiguity of R&amp;D activities and the difficulty in &quot;managing&quot; them. Management, including Six Sigma, is all about trying to eliminate uncertainty to help us make better decisions. The less variability, the less uncertainty. But when this philosophy is applied to R&amp;D, it hampers the discovery process.

By the way, I want to separate the &quot;R&quot; from the &quot;D&quot; in R&amp;D. While I believe there are inherent conflicts between traditional management practices and research, I do not think this is the case with development. Once a research discovery has been made, the development process truly is a manageable process and Six Sigma, Lean, and Quality principles can and should be applied.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->I received this response to this posting from LinkedIn:<br />
&#8220;While I agree with much of your perspective, I take exception to the the statement that R&#038;D is inherently and unavoidably wasteful. Waste is defined by its economic value. A well planned well executed and effectively analyzed experiment has value, even if the intended result is not achieved. The learning acquired has value. To call this waste invites and reinforces the often cited conflict between corporate leadership and R&#038;D.&#8221;</p>
<p>Here&#8217;s my response:</p>
<p>A rose by any other name&#8230;</p>
<p>I think we need to call a spade a spade here and work to change management&#8217;s misconception. When &#8220;the intended result is not achieved&#8221; most people call this failure and view the expended resources as waste. Why not just admit that such outcomes are an inherent part of the discovery process and learn to deal with it? Six Sigma, lean and quality aren&#8217;t the only evidence of management&#8217;s abhorrence of waste, it&#8217;s an integral part of management. The conflict between management and R&#038;D is largely due to the ambiguity of R&#038;D activities and the difficulty in &#8220;managing&#8221; them. Management, including Six Sigma, is all about trying to eliminate uncertainty to help us make better decisions. The less variability, the less uncertainty. But when this philosophy is applied to R&#038;D, it hampers the discovery process.</p>
<p>By the way, I want to separate the &#8220;R&#8221; from the &#8220;D&#8221; in R&#038;D. While I believe there are inherent conflicts between traditional management practices and research, I do not think this is the case with development. Once a research discovery has been made, the development process truly is a manageable process and Six Sigma, Lean, and Quality principles can and should be applied.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
</channel>
</rss>
