<?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"
	>
<channel>
	<title>Comments on: It&#8217;s the economy, stupid.</title>
	<atom:link href="http://blog.enterprise2open.com/2009/04/10/its-the-economy-stupid/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.enterprise2open.com/2009/04/10/its-the-economy-stupid/</link>
	<description>Bonding the Enterprise 2.0 Community</description>
	<pubDate>Fri, 12 Mar 2010 01:55:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Want to look behind the scenes of the E2.0 SUMMIT? Processes and all &#8230;</title>
		<link>http://blog.enterprise2open.com/2009/04/10/its-the-economy-stupid/#comment-5155</link>
		<dc:creator>Want to look behind the scenes of the E2.0 SUMMIT? Processes and all &#8230;</dc:creator>
		<pubDate>Sun, 12 Apr 2009 09:34:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enterprise2open.com/?p=81#comment-5155</guid>
		<description>[...] discussing has happened behind the stage of the Enterprise 2.0 SUMMIT - and it is triggering more worthwhile posts as well. As the idea of the E2.0 SUMMIT on Oct 6-8th is to represent a community and expertise hub for the [...]</description>
		<content:encoded><![CDATA[<p>[...] discussing has happened behind the stage of the Enterprise 2.0 SUMMIT - and it is triggering more worthwhile posts as well. As the idea of the E2.0 SUMMIT on Oct 6-8th is to represent a community and expertise hub for the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Venkat</title>
		<link>http://blog.enterprise2open.com/2009/04/10/its-the-economy-stupid/#comment-4991</link>
		<dc:creator>Venkat</dc:creator>
		<pubDate>Fri, 10 Apr 2009 18:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enterprise2open.com/?p=81#comment-4991</guid>
		<description>Hmm... I hadn't thought of this operational quicksand and 'reaction to pricing' dynamics and the effects of different way of organizing to realize an ROI model.

I did my own take on the ROI question here: &lt;a href="http://enterprise2blog.com/2008/12/the-hit-by-a-bus-social-media-roi-method/" rel="nofollow"&gt;The 'hit by a bus' social media ROI method&lt;/a&gt; which takes on very different issues of whether ROI is even a coherent concept.

The big confusion is that in information-work companies, there is no easy way to compute the ROI of any unit smaller than the entire company. Everything is a 'cost' and returns happen only at the level of a customer engaging the whole value proposition. Staff/line distinctions become meaningless, and it is hard to say how much of a lost/won sale to attribute to presence/absence of (say) a wiki to accelerate the sales cycle, and how much to feature comparisons with competing products. It all matters.

There was some movement starting decades ago to rationalize accounting for information-work based companies. I am no accountant, but the big distinction is between cost-accounting and activity-based accounting.

But, not to sound like a broken record, the ROI argument is a red herring set up by those who want to confuse an issue of strategy by bringing in irrelevant notions of accounting. The only accounting term that matters are strategic ones: the "opportunity cost" of not enjoying a period of social-media fueled differentiation before it becomes a "cost of doing business."

Operational sub-company-sized ROI arguments can and have been made (for example ROI in customer acquisition/retention terms for a specifically marketing-oriented investment), but a war is not the sum of a bunch of battles, some measurable and some not. Social media as point-fix tactics is ROI-measurable and not very interesting. Social media as representing the DNA of a business strategy is NOT ROI-measurable and IS interesting.

In other words, ROI illuminates the sideshows and leaves the big tent in darkness.</description>
		<content:encoded><![CDATA[<p>Hmm&#8230; I hadn&#8217;t thought of this operational quicksand and &#8216;reaction to pricing&#8217; dynamics and the effects of different way of organizing to realize an ROI model.</p>
<p>I did my own take on the ROI question here: <a href="http://enterprise2blog.com/2008/12/the-hit-by-a-bus-social-media-roi-method/" rel="nofollow">The &#8216;hit by a bus&#8217; social media ROI method</a> which takes on very different issues of whether ROI is even a coherent concept.</p>
<p>The big confusion is that in information-work companies, there is no easy way to compute the ROI of any unit smaller than the entire company. Everything is a &#8216;cost&#8217; and returns happen only at the level of a customer engaging the whole value proposition. Staff/line distinctions become meaningless, and it is hard to say how much of a lost/won sale to attribute to presence/absence of (say) a wiki to accelerate the sales cycle, and how much to feature comparisons with competing products. It all matters.</p>
<p>There was some movement starting decades ago to rationalize accounting for information-work based companies. I am no accountant, but the big distinction is between cost-accounting and activity-based accounting.</p>
<p>But, not to sound like a broken record, the ROI argument is a red herring set up by those who want to confuse an issue of strategy by bringing in irrelevant notions of accounting. The only accounting term that matters are strategic ones: the &#8220;opportunity cost&#8221; of not enjoying a period of social-media fueled differentiation before it becomes a &#8220;cost of doing business.&#8221;</p>
<p>Operational sub-company-sized ROI arguments can and have been made (for example ROI in customer acquisition/retention terms for a specifically marketing-oriented investment), but a war is not the sum of a bunch of battles, some measurable and some not. Social media as point-fix tactics is ROI-measurable and not very interesting. Social media as representing the DNA of a business strategy is NOT ROI-measurable and IS interesting.</p>
<p>In other words, ROI illuminates the sideshows and leaves the big tent in darkness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paula Thornton</title>
		<link>http://blog.enterprise2open.com/2009/04/10/its-the-economy-stupid/#comment-4974</link>
		<dc:creator>Paula Thornton</dc:creator>
		<pubDate>Fri, 10 Apr 2009 16:16:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.enterprise2open.com/?p=81#comment-4974</guid>
		<description>Great piece...heck, I'm still reading it. There's a lot of thought here.

My only extra 2cents is that understanding SOA is less of an issue than having an 'architect' to engage in and champion/facilitate it's fruits, rather than the typical 'drafters' that are employed by IT.

In reading "if you are not doing so with a meaning for the words 'return', or 'investment'", made me think, for the typical endeavor the title should be JTI: Justify This Investment. There is clearly no 'continuity' in the process (in most cases) as implied by the term ROI. If there were, we'd have continuous ROI dashboards to watch the investments and their return continue to compete with one another. Ever seen one?</description>
		<content:encoded><![CDATA[<p>Great piece&#8230;heck, I&#8217;m still reading it. There&#8217;s a lot of thought here.</p>
<p>My only extra 2cents is that understanding SOA is less of an issue than having an &#8216;architect&#8217; to engage in and champion/facilitate it&#8217;s fruits, rather than the typical &#8216;drafters&#8217; that are employed by IT.</p>
<p>In reading &#8220;if you are not doing so with a meaning for the words &#8216;return&#8217;, or &#8216;investment&#8217;&#8221;, made me think, for the typical endeavor the title should be JTI: Justify This Investment. There is clearly no &#8216;continuity&#8217; in the process (in most cases) as implied by the term ROI. If there were, we&#8217;d have continuous ROI dashboards to watch the investments and their return continue to compete with one another. Ever seen one?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
