<?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: Consensus and Compromise in Project Management</title>
	<atom:link href="http://www.pmhut.com/consensus-and-compromise-in-project-management/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/consensus-and-compromise-in-project-management</link>
	<description></description>
	<pubDate>Mon, 21 May 2012 14:55:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: michel operto</title>
		<link>http://www.pmhut.com/consensus-and-compromise-in-project-management/comment-page-1#comment-15358</link>
		<dc:creator>michel operto</dc:creator>
		<pubDate>Wed, 13 Jan 2010 16:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4568#comment-15358</guid>
		<description>Hello Susan, I agree with your post as it relates to what I call STRONG consensus and its value. However, it is my experience in large corporations that consensus are most often soft, weak, very weak in fact... i.e. the people do not dare to object and let the decision be made without really committing themselves to it. A good compromise is often better that such a weak consensus. Don't you think? Michel.</description>
		<content:encoded><![CDATA[<p>Hello Susan, I agree with your post as it relates to what I call STRONG consensus and its value. However, it is my experience in large corporations that consensus are most often soft, weak, very weak in fact&#8230; i.e. the people do not dare to object and let the decision be made without really committing themselves to it. A good compromise is often better that such a weak consensus. Don&#8217;t you think? Michel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura Bamberg</title>
		<link>http://www.pmhut.com/consensus-and-compromise-in-project-management/comment-page-1#comment-15311</link>
		<dc:creator>Laura Bamberg</dc:creator>
		<pubDate>Tue, 12 Jan 2010 16:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4568#comment-15311</guid>
		<description>Hi Susan - this was a good post. Another tactic - to start off by determining what you hope to accomplish team-wise - not the decision itself at hand. For example - do we want to build trust with this decision, learn to work together better? If so, each team member - including the project manager - should come to the table with an attitude of trust and engage each other from that basis. This is something we're trying in our own organization and we have seen good, long-lasting results from it. This doesn't mean you don't ever have to sit down to come to a consensus again, or that there are never going to be differing opinions. It does mean that when these situations come up, the team is better able to make a decision with less frustration and anger.</description>
		<content:encoded><![CDATA[<p>Hi Susan - this was a good post. Another tactic - to start off by determining what you hope to accomplish team-wise - not the decision itself at hand. For example - do we want to build trust with this decision, learn to work together better? If so, each team member - including the project manager - should come to the table with an attitude of trust and engage each other from that basis. This is something we&#8217;re trying in our own organization and we have seen good, long-lasting results from it. This doesn&#8217;t mean you don&#8217;t ever have to sit down to come to a consensus again, or that there are never going to be differing opinions. It does mean that when these situations come up, the team is better able to make a decision with less frustration and anger.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

