<?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: Some thoughts on Consensus vs. Collaboration</title>
	<atom:link href="http://www.omakasegroup.com/blog/archives/43/feed" rel="self" type="application/rss+xml" />
	<link>http://www.omakasegroup.com/blog/archives/43</link>
	<description>Unleashing the power within organizations with facilitation and visualization.</description>
	<lastBuildDate>Mon, 07 Jun 2010 13:13:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Patrick Keenan</title>
		<link>http://www.omakasegroup.com/blog/archives/43/comment-page-1#comment-294</link>
		<dc:creator>Patrick Keenan</dc:creator>
		<pubDate>Mon, 14 Sep 2009 22:33:27 +0000</pubDate>
		<guid isPermaLink="false">http://danielroseca.wordpress.com/?p=45#comment-294</guid>
		<description>Consensus seems to have a couple parts like you mentioned: approach vs outcome.

Also there is just the matter of being understood. So much of people&#039;s complaints stem from feelings of not being considered. Often when people are heard &amp; addressed, they don&#039;t mind so much that their concerns are not completely satisfied.

I like the additive &quot;and&quot; rather than the subtractive &quot;but&quot;. Its amazing how much it changes conversation when you get on an &quot;and&quot; streak. Sometimes I have to stop myself because its just too much.

One thing we might be better at in this regard is the &quot;or&quot;. That is, providing many options and understanding that they are all good. Maybe it could be the &quot;and or&quot;, because its additive, just in a different way.

I don&#039;t know that &quot;consensus building&quot; is an oxymoron. Maybe just &quot;understanding &amp; addressing other people&quot; would do though.</description>
		<content:encoded><![CDATA[<p>Consensus seems to have a couple parts like you mentioned: approach vs outcome.</p>
<p>Also there is just the matter of being understood. So much of people&#8217;s complaints stem from feelings of not being considered. Often when people are heard &amp; addressed, they don&#8217;t mind so much that their concerns are not completely satisfied.</p>
<p>I like the additive &#8220;and&#8221; rather than the subtractive &#8220;but&#8221;. Its amazing how much it changes conversation when you get on an &#8220;and&#8221; streak. Sometimes I have to stop myself because its just too much.</p>
<p>One thing we might be better at in this regard is the &#8220;or&#8221;. That is, providing many options and understanding that they are all good. Maybe it could be the &#8220;and or&#8221;, because its additive, just in a different way.</p>
<p>I don&#8217;t know that &#8220;consensus building&#8221; is an oxymoron. Maybe just &#8220;understanding &amp; addressing other people&#8221; would do though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: danielroseca</title>
		<link>http://www.omakasegroup.com/blog/archives/43/comment-page-1#comment-26</link>
		<dc:creator>danielroseca</dc:creator>
		<pubDate>Wed, 06 Aug 2008 18:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://danielroseca.wordpress.com/?p=45#comment-26</guid>
		<description>I&#039;m definitely intrigued by the comments on this post coming back to the Quaker model. I like the distinction between the approach and the outcome.

Maybe the fundamental difference is that in corporate speak consensus means that the high powered exec tells everyone what they should think until consensus is achieved. Whereas the Quaker approach is about what Michael described and assumes a more holistic view of how the world works and an appreciation for diversity.

I look forward to giving this topic a lot more thought.</description>
		<content:encoded><![CDATA[<p>I&#8217;m definitely intrigued by the comments on this post coming back to the Quaker model. I like the distinction between the approach and the outcome.</p>
<p>Maybe the fundamental difference is that in corporate speak consensus means that the high powered exec tells everyone what they should think until consensus is achieved. Whereas the Quaker approach is about what Michael described and assumes a more holistic view of how the world works and an appreciation for diversity.</p>
<p>I look forward to giving this topic a lot more thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Anton Dila</title>
		<link>http://www.omakasegroup.com/blog/archives/43/comment-page-1#comment-25</link>
		<dc:creator>Michael Anton Dila</dc:creator>
		<pubDate>Thu, 31 Jul 2008 22:10:30 +0000</pubDate>
		<guid isPermaLink="false">http://danielroseca.wordpress.com/?p=45#comment-25</guid>
		<description>I, too, have had a bit of experience with the concept and practice of consensus. I have had less experience with the corporate variety, which I think is often merely code for decision by committee, which is part of a cover-your-as-by-making-sure-that-no-decision-you-make-is-traceable-to-anyone-in-particularism.

On the other hand, I went to a Quaker college in the American midwest and was part of many governance bodies and processes that used consensus. Personally, my best experiences were in situations in which consensus was a conversational norm rather than a tightly prescriptive process. Here, consensus is as much about how we &quot;govern&quot; a conversation as about how we reach an outcome or agreement. I think of the ideal of consensus as an agreement to seek an outcome that satisfies everyone, not because it compromises and reaches a lowest common denominator, but because it forces us to grapple with diversity and nuance and to seek &quot;larger&quot; solutions that can contain everyone&#039;s perspectives and goals with shoe-horning them into crappy versions of people&#039;s third choice options.

A big clue to this in Quaker religious practice is the fundamental belief in &quot;that light of God that is in everyone&quot;.

True consensus is, I think, an agreement to respect each other and to work hard to put that respect into practice instead of into the empty phrases of &quot;mission&quot; statements.</description>
		<content:encoded><![CDATA[<p>I, too, have had a bit of experience with the concept and practice of consensus. I have had less experience with the corporate variety, which I think is often merely code for decision by committee, which is part of a cover-your-as-by-making-sure-that-no-decision-you-make-is-traceable-to-anyone-in-particularism.</p>
<p>On the other hand, I went to a Quaker college in the American midwest and was part of many governance bodies and processes that used consensus. Personally, my best experiences were in situations in which consensus was a conversational norm rather than a tightly prescriptive process. Here, consensus is as much about how we &#8220;govern&#8221; a conversation as about how we reach an outcome or agreement. I think of the ideal of consensus as an agreement to seek an outcome that satisfies everyone, not because it compromises and reaches a lowest common denominator, but because it forces us to grapple with diversity and nuance and to seek &#8220;larger&#8221; solutions that can contain everyone&#8217;s perspectives and goals with shoe-horning them into crappy versions of people&#8217;s third choice options.</p>
<p>A big clue to this in Quaker religious practice is the fundamental belief in &#8220;that light of God that is in everyone&#8221;.</p>
<p>True consensus is, I think, an agreement to respect each other and to work hard to put that respect into practice instead of into the empty phrases of &#8220;mission&#8221; statements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christine Martell</title>
		<link>http://www.omakasegroup.com/blog/archives/43/comment-page-1#comment-24</link>
		<dc:creator>Christine Martell</dc:creator>
		<pubDate>Sat, 12 Jul 2008 16:06:44 +0000</pubDate>
		<guid isPermaLink="false">http://danielroseca.wordpress.com/?p=45#comment-24</guid>
		<description>Daniel,
Years ago I was working for two organizations that used consensus decision making. Yes, especially when people first arrived, the conversations could feel subtractive. But as people gained experience and learned more about consensus decision making, the conversations shifted to be more collaborative and additive. We began to recognize that taking people who were coming from hierarchal decision structures, and plopping them down expecting them to be collaborative was unrealistic.

I began to understand the differences at a deeper level through trial and error and not giving up too soon. I also really deepened my understanding through multiple long conversations with Quaker colleagues who had been living with consensus their whole lives in their personal worlds, while living in different structures in the world around them.</description>
		<content:encoded><![CDATA[<p>Daniel,<br />
Years ago I was working for two organizations that used consensus decision making. Yes, especially when people first arrived, the conversations could feel subtractive. But as people gained experience and learned more about consensus decision making, the conversations shifted to be more collaborative and additive. We began to recognize that taking people who were coming from hierarchal decision structures, and plopping them down expecting them to be collaborative was unrealistic.</p>
<p>I began to understand the differences at a deeper level through trial and error and not giving up too soon. I also really deepened my understanding through multiple long conversations with Quaker colleagues who had been living with consensus their whole lives in their personal worlds, while living in different structures in the world around them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

