<?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: An Excuse to Sluice</title>
	<atom:link href="http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/</link>
	<description>Investigations Into Enterprise 2.0</description>
	<lastBuildDate>Thu, 28 Jan 2010 19:42:42 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ric</title>
		<link>http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/comment-page-1/#comment-215</link>
		<dc:creator>Ric</dc:creator>
		<pubDate>Tue, 01 Jul 2008 15:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/#comment-215</guid>
		<description>What&#039;s so bad about the F-bomb? 

DHH (of rails and 37signals fame) thinks it&#039;s not so bad:
http://www.loudthinking.com/posts/15-potty-mouths

In fact, he dislikes the term &#039;F-bomb&#039; more than the word on which you&#039;re trying to put the proverbial fig-leaf.</description>
		<content:encoded><![CDATA[<p>What&#8217;s so bad about the F-bomb? </p>
<p>DHH (of rails and 37signals fame) thinks it&#8217;s not so bad:<br />
<a href="http://www.loudthinking.com/posts/15-potty-mouths" rel="nofollow">http://www.loudthinking.com/posts/15-potty-mouths</a></p>
<p>In fact, he dislikes the term &#8216;F-bomb&#8217; more than the word on which you&#8217;re trying to put the proverbial fig-leaf.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/comment-page-1/#comment-126</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Thu, 22 May 2008 02:34:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/#comment-126</guid>
		<description>Well, as the still sole administrative edit in our wiki, and given the proximity of the offense to the &quot;I hope he gets fired&quot; above...  Albeit mine was a touch wittier.

Complete transparency is not a bad thing - it is only a scary thing.  It is scary because it means multiple things - we must expose our weaknesses and thoughts before we are ready, and we must then not judge others for doing the same.  A truly merits based system requires a mixing of transparency with honesty.  Hiding behind the &quot;management only&quot; decision making so keep your nose out tree is a facet of laziness, not management...

At some point we must embrace the path we preach to the third world countries - that attempting to control the innovation within your borders stifles the innovation, and stifles the bringing in of money.  Letting go yields more fruit than holding tight, and in the end your decision to enable that paradigm will be remembered (even if not in the immediate) - however squeezing the child to death in its infancy for fear of its future will have you known earlier,  but for the wrong reasons.</description>
		<content:encoded><![CDATA[<p>Well, as the still sole administrative edit in our wiki, and given the proximity of the offense to the &#8220;I hope he gets fired&#8221; above&#8230;  Albeit mine was a touch wittier.</p>
<p>Complete transparency is not a bad thing &#8211; it is only a scary thing.  It is scary because it means multiple things &#8211; we must expose our weaknesses and thoughts before we are ready, and we must then not judge others for doing the same.  A truly merits based system requires a mixing of transparency with honesty.  Hiding behind the &#8220;management only&#8221; decision making so keep your nose out tree is a facet of laziness, not management&#8230;</p>
<p>At some point we must embrace the path we preach to the third world countries &#8211; that attempting to control the innovation within your borders stifles the innovation, and stifles the bringing in of money.  Letting go yields more fruit than holding tight, and in the end your decision to enable that paradigm will be remembered (even if not in the immediate) &#8211; however squeezing the child to death in its infancy for fear of its future will have you known earlier,  but for the wrong reasons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Nash</title>
		<link>http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/comment-page-1/#comment-114</link>
		<dc:creator>Nate Nash</dc:creator>
		<pubDate>Sat, 17 May 2008 14:23:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/#comment-114</guid>
		<description>Thanks for the comment Austin! I agree that some of the capabilities I describe could be helpful in spurring additional adoption amongst the &quot;middle class&quot; users. However, I worry that if some of those controls were engaged in the early days, the hyperusers (who have carried the implementation so far), would not have been able to flex their creative muscles. 

An example of something that  Confluence empowered due to its blank slate capabilities is the Advisor Tracking app. I am pretty sure that this could not be accomplished in Clearspace. 

An example of something that could be accomplished much more elegantly in Clearspace is the Clearinghouse. 

Finding the middle ground is tough...maybe one approach is a predecessor to the other...</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Austin! I agree that some of the capabilities I describe could be helpful in spurring additional adoption amongst the &#8220;middle class&#8221; users. However, I worry that if some of those controls were engaged in the early days, the hyperusers (who have carried the implementation so far), would not have been able to flex their creative muscles. </p>
<p>An example of something that  Confluence empowered due to its blank slate capabilities is the Advisor Tracking app. I am pretty sure that this could not be accomplished in Clearspace. </p>
<p>An example of something that could be accomplished much more elegantly in Clearspace is the Clearinghouse. </p>
<p>Finding the middle ground is tough&#8230;maybe one approach is a predecessor to the other&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Austin</title>
		<link>http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/comment-page-1/#comment-112</link>
		<dc:creator>Austin</dc:creator>
		<pubDate>Fri, 16 May 2008 16:42:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/#comment-112</guid>
		<description>Aside from the hyperusers, adoption will only happen if one of two things happen: use is required (fear) or users see a clear benefit for their volutary use of the product.    &quot;Middle class&quot; users will not see the benefit in using a product like Confluence without some degree of support (training, templates, examples, handholding, etc).  

That said, (as a user of confluence), I would want to see some usage of the capabilities you saw in Clearspace to extend the interest (don&#039;t lock it down but provide more options to both hypousers and hyperusers).  

I agree with just marketing the capabilities that an team charged with building collaboration deems necessary to fit their particular organization and hiding the rest.</description>
		<content:encoded><![CDATA[<p>Aside from the hyperusers, adoption will only happen if one of two things happen: use is required (fear) or users see a clear benefit for their volutary use of the product.    &#8220;Middle class&#8221; users will not see the benefit in using a product like Confluence without some degree of support (training, templates, examples, handholding, etc).  </p>
<p>That said, (as a user of confluence), I would want to see some usage of the capabilities you saw in Clearspace to extend the interest (don&#8217;t lock it down but provide more options to both hypousers and hyperusers).  </p>
<p>I agree with just marketing the capabilities that an team charged with building collaboration deems necessary to fit their particular organization and hiding the rest.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
