<?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: Web 2.0 ROI Must Read: EMC&#124;ONE White Paper</title>
	<atom:link href="http://collaborationevangelist.com/2009/05/04/web-20-roi-must-read-emcone-white-paper/feed/" rel="self" type="application/rss+xml" />
	<link>http://collaborationevangelist.com/2009/05/04/web-20-roi-must-read-emcone-white-paper/</link>
	<description>Craig Underwood's blog about Web 2.0, loyalty and customer service</description>
	<lastBuildDate>Mon, 22 Jun 2009 13:51:28 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chet Geschickter</title>
		<link>http://collaborationevangelist.com/2009/05/04/web-20-roi-must-read-emcone-white-paper/comment-page-1/#comment-58</link>
		<dc:creator>Chet Geschickter</dc:creator>
		<pubDate>Fri, 08 May 2009 13:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://collaborationevangelist.com/?p=409#comment-58</guid>
		<description>Craig,
I&#039;m glad you made the flight ;-) and endured the platitudes to get to Chuck&#039;s comments.
In some respects, I think the whole debate about social media ROI is a little misguided.  Did people debate the ROI of email when it first came into use?  Short answer, no.  Lotus might have strapped together some ROI business cases for enterprise sales of Lotus Notes, but all in all, how do you put an ROI on people connecting with people and on the value of sharing ideas?  We must default to ad-hoc vignettes (for instance, when launching this product employee a connected with employee b on topic z, saving abc months, etc. etc.).  
The knowledge management &quot;industry&quot; has spun around this issue of ROI from human interaction for many years now, without reaching any sound conclusions.  The cold hard reality is that &quot;ROI&quot; resides at the soft intersection of culture, business process and behaviors, none of which fits tidily into an Excel spreadsheet.  Which is all a bit of a drawn out way of saying that Chuck hits the nail on the head when he talks about measurement philosophy being more important than specific metrics.  
For those that need numbers, his sweeping estimates should serve the purpose.  They are certain to reverberate around the blogosphere.
Good post.</description>
		<content:encoded><![CDATA[<p>Craig,<br />
I&#8217;m glad you made the flight <img src='http://collaborationevangelist.com/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  and endured the platitudes to get to Chuck&#8217;s comments.<br />
In some respects, I think the whole debate about social media ROI is a little misguided.  Did people debate the ROI of email when it first came into use?  Short answer, no.  Lotus might have strapped together some ROI business cases for enterprise sales of Lotus Notes, but all in all, how do you put an ROI on people connecting with people and on the value of sharing ideas?  We must default to ad-hoc vignettes (for instance, when launching this product employee a connected with employee b on topic z, saving abc months, etc. etc.).<br />
The knowledge management &#8220;industry&#8221; has spun around this issue of ROI from human interaction for many years now, without reaching any sound conclusions.  The cold hard reality is that &#8220;ROI&#8221; resides at the soft intersection of culture, business process and behaviors, none of which fits tidily into an Excel spreadsheet.  Which is all a bit of a drawn out way of saying that Chuck hits the nail on the head when he talks about measurement philosophy being more important than specific metrics.<br />
For those that need numbers, his sweeping estimates should serve the purpose.  They are certain to reverberate around the blogosphere.<br />
Good post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
