<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>e2.oh &#187; clearspace</title>
	<atom:link href="http://www.e2oh.com/tag/clearspace/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.e2oh.com</link>
	<description>Investigations Into Enterprise 2.0</description>
	<lastBuildDate>Mon, 10 Jan 2011 19:20:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>An Excuse to Sluice</title>
		<link>http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/</link>
		<comments>http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/#comments</comments>
		<pubDate>Thu, 15 May 2008 03:28:36 +0000</pubDate>
		<dc:creator>Nate Nash</dc:creator>
				<category><![CDATA[Nate Nash]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[clearspace]]></category>
		<category><![CDATA[confluence]]></category>
		<category><![CDATA[enterprise 2.0]]></category>

		<guid isPermaLink="false">http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/</guid>
		<description><![CDATA[Jay and I had a banging good time today attending Jive&#8217;s Clearspace Administrator training. Our instructor for the session, Ricky Palmer, gave a great run down on the robust capabilities available to the man (or woman) behind the curtain. We had seen the latest release of the product, but this session gave a much better [...]]]></description>
			<content:encoded><![CDATA[<p>Jay and I had a banging good time today attending <a href="http://www.jivesoftware.com">Jive&#8217;s</a> <a href="http://www.jivesoftware.com/products/clearspace/">Clearspace</a> Administrator training. Our instructor for the session, <a href="http://www.rickysays.com/">Ricky Palmer</a>, gave a great run down on the robust capabilities available to the man (or woman) behind the curtain. We had <a href="http://www.e2oh.com/2008/04/07/jive-talkin/">seen the latest release of the product</a>, but this session gave a much better feel for what I sort of refer to as &#8220;Floodgates on the River Collaboration.&#8221;</p>
<p>As I was sitting in the session today, <a href="http://twitter.com/natenash203">tweeting my thoughts</a> on Enterprise 2.0, I began to ponder the value of moderating collaboration. If you haven&#8217;t had a chance to see the admin features in Clearspace, they are <strong>robusto</strong>. Essentially, you can control everything. It ranges from deciding who can and can not blog to creating automated filters for users with a propensity to curse like a a trucker. It is very clear (at least to me) that their content moderation approach was baked via <a href="http://www.jivesoftware.com/products/jive-forums">their deep experience with forums</a> facing the jagged masses of the public internet. And as their marketing guns also seem to have shifted aim toward powering external communities, these capabilities make even more sense. But I wonder&#8230;.could these same capabilities, which are much needed on the public facing side of collaboration, provide an opportunity to over-manage an internal user community?</p>
<p>I contrast the capabilities I saw today with those available in the (internal) enterprise Wiki I administer, powered by <a href="http://www.atlassian.com">Atlassian&#8217;s</a> <a href="http://www.atlassian.com/confluence">Confluence</a>. Hands down, Confluence has nowhere near the control and admin capabilities of Clearspace. And when implementing in a low-risk, high-lawyer internal environment I fear that the mere presence of such control may encourage unnecessary administrative fear-mongering. By extension, the resulting collaboration environment could be so locked down that the users contribute little content and create little value.</p>
<p>Frankly, I sort of like the idea that if some moron in my company drops an F bomb on a blog post, that slickness is immediately exposed to the entire company. I <strong>hope</strong> he gets fired. And HR keeps the post up as an example of &#8220;what not to do with the enterprise Wiki.&#8221; If you are that dense I am 1) glad other people know, 2) convinced you don&#8217;t deserve a job here, and 3) now aware that we might need more stringent hiring practices. All good things in my book. This staffing action can happen in our Wiki.  If the filtering capability was there, I am not sure I could have convinced the risk-dodgers to turn it off.</p>
<p>On another other hand, Clearspace&#8217;s admin capabilities do a great job of providing much needed structure and tailoring to the collaboration needs of a community. I would guess that their adoption rates are much quicker with the vast majority of users than that of a wiki. The blank-slate paradigm works only for the hyper-creative. We continue to run into adoption issues with people who &#8220;just want more structure&#8221; or &#8220;don&#8217;t know where to start&#8221;. We could very easily solve this is we had the admin capabilities of Clearspace.</p>
<p>Don&#8217;t get me wrong, I think Clearspace is an awesome product with a boatload of power. It toasts my E2 Reuben for sure.  The administrative capabilities are both flexible and powerful. But as with any powerful tool placed in paranoid hands, incorrect use could lead to undesired results. Maybe the answer is don&#8217;t let the FUDdites know some of the the admin capabilities exist? Maybe different communities need different paradigms?</p>
<p>What do you think?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.e2oh.com/2008/05/14/an-excuse-to-sluice/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Open Collaboration With Customers = Sell More Stuff</title>
		<link>http://www.e2oh.com/2008/02/08/open-collaboration-with-customers-sell-more-stuff/</link>
		<comments>http://www.e2oh.com/2008/02/08/open-collaboration-with-customers-sell-more-stuff/#comments</comments>
		<pubDate>Fri, 08 Feb 2008 21:26:28 +0000</pubDate>
		<dc:creator>Jay Hariani</dc:creator>
				<category><![CDATA[Jay Hariani]]></category>
		<category><![CDATA[clearspace]]></category>
		<category><![CDATA[enterprise 2.0]]></category>
		<category><![CDATA[jive]]></category>
		<category><![CDATA[management 2.0]]></category>
		<category><![CDATA[mozilla]]></category>

		<guid isPermaLink="false">http://www.e2oh.com/2008/02/08/open-collaboration-with-customers-sell-more-stuff/</guid>
		<description><![CDATA[Making good software is hard. Really hard. From my experience working with vendors, enterprise software is hard to get right. Good software companies learned a while ago that allowing their customers insight into their development process helps them make better software more quickly &#8211; creating a feedback loop makes customers see that their input is [...]]]></description>
			<content:encoded><![CDATA[<p>Making good software is hard. Really hard. From my experience working with vendors, enterprise software is hard to get right. Good software companies learned a while ago that allowing their customers insight into their development process helps them make better software more quickly &#8211; creating a feedback loop makes customers see that their input is valued, and leads to a higher quality product. Atlassian, for example, allows customers to submit not just bugs, but <a href="http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements">submit and vote on feature requests</a>. Jive, with their <a href="http://www.jivesoftware.com/products/clearspace/clearspacex.jsp">Clearspace X product,</a> allows more then just software companies to engage their customers. I think Clearspace X is a very exciting product, and firmly believe companies will start buying into E2.0 CRM solutions aggressively. They offer what is (at least right now) perhaps the most compelling use of E2.0 &#8211; building vibrant customer communities and networks &#8211; something tied directly to the bottom line.<span id="more-20"></span></p>
<p><a href="http://www.mckinseyquarterly.com/Strategy/Innovation/Succeeding_at_open-source_innovation__An_interview_with_Mozillas_Mitchell_Baker_2098">This interview</a>, with Mozilla’s Mitchell Baker, elaborates how exposing the inner working of your company to your customers can have many, many benefits .  Mozilla, as an organization, operates in a fishbowl. Very little of what happens inside of the company is hidden from public scrutiny. This poses some intersting management challenges, but at the end of the day has lead to exceptional products. Because Mozilla&#8217;s customers are so integral to its process, it&#8217;s much easier for it&#8217;s products to be what users want them to be</p>
<p>These vocal, contributory communities of customers &#8211; fostered by technologies like Clearspace X and management that supports open collaboration and transparency &#8211; could be referred to as &#8220;Marketing 2.0&#8243;. No degree of advertising could have given Firefox the level of momentum it has. Again, I&#8217;d wager that software companies aren&#8217;t the only businesses that harness their customers in this fashion. Opening the enterprise to two-way collaboration with customers will prove to be a competitive advantage. But it will take a touch of vision, and a certain willingness to have your mistakes publicized, to realize that value.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.e2oh.com/2008/02/08/open-collaboration-with-customers-sell-more-stuff/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

