<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: David Schmaltz Was a Hit!</title>
	<link>http://www.reformingprojectmanagement.com/2004/01/22/298/</link>
	<description>The magazine for the project age</description>
	<pubDate>Fri, 04 Jul 2008 13:40:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Amy Schwab
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/01/22/298/#comment-146</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/01/22/298/#comment-146</guid>
					<description>
        I agree that many may react strongly to the 'inconsistency' comment.  A slight shift from inconsistency to customization might make all of the difference in getting the idea across.  In this one-to-one marketing world, this isn't a foreign concept.  And, by the way, there are consistent ways to go about the highly customized processes leading to consistent results.  But you have to work at a meta level rather than the process level.
      </description>
		<content:encoded><![CDATA[<p>I agree that many may react strongly to the &#8216;inconsistency&#8217; comment.  A slight shift from inconsistency to customization might make all of the difference in getting the idea across.  In this one-to-one marketing world, this isn&#8217;t a foreign concept.  And, by the way, there are consistent ways to go about the highly customized processes leading to consistent results.  But you have to work at a meta level rather than the process level.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Frank Winters
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/01/22/298/#comment-147</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/01/22/298/#comment-147</guid>
					<description>
        Amy, You hit the nail on the head! Process models need to be tailored for each project. But tailoring or customization doesn't really mean inconsistency. That term -- inconsistency -- is harmful and confusing  to many, I believe.
      </description>
		<content:encoded><![CDATA[<p>Amy, You hit the nail on the head! Process models need to be tailored for each project. But tailoring or customization doesn&#8217;t really mean inconsistency. That term &#8212; inconsistency &#8212; is harmful and confusing  to many, I believe.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David A. Schmaltz
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/01/22/298/#comment-148</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/01/22/298/#comment-148</guid>
					<description>
        Frank, I'd question whether embracing necessary inconsistency is more damaging than the pursuit of consistency. The power of the suggestion, which was made by someone who introduced himself as having 600 PMs working for his organization, is that it is provocative. It wakes up the slumbering questioner inside. He realized that his solution was the real problem.

His dilemma was that he has hundreds of customers, each clamboring for consistency. I suggested that if he spoke with each, he might well find that each has a very different definition of consistency, to which he replied that they were probably more interested in consistent results than in consistent process. He recognized that the relationship between consistent process and consistent results is spurious across different contexts, and that, as Amy notes, consistency takes on a surprising, seemingly paradoxical meaning then.
      </description>
		<content:encoded><![CDATA[<p>Frank, I&#8217;d question whether embracing necessary inconsistency is more damaging than the pursuit of consistency. The power of the suggestion, which was made by someone who introduced himself as having 600 PMs working for his organization, is that it is provocative. It wakes up the slumbering questioner inside. He realized that his solution was the real problem.</p>
<p>His dilemma was that he has hundreds of customers, each clamboring for consistency. I suggested that if he spoke with each, he might well find that each has a very different definition of consistency, to which he replied that they were probably more interested in consistent results than in consistent process. He recognized that the relationship between consistent process and consistent results is spurious across different contexts, and that, as Amy notes, consistency takes on a surprising, seemingly paradoxical meaning then.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
