<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Where is enterprise data really going?</title>
	<atom:link href="http://www.fastforwardblog.com/2008/11/20/where-is-enterprise-data-really-going/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2008/11/20/where-is-enterprise-data-really-going/</link>
	<description></description>
	<lastBuildDate>Fri, 28 Oct 2011 01:28:22 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jordan Frank</title>
		<link>http://www.fastforwardblog.com/2008/11/20/where-is-enterprise-data-really-going/comment-page-1/#comment-198092</link>
		<dc:creator>Jordan Frank</dc:creator>
		<pubDate>Tue, 09 Dec 2008 18:29:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/?p=1214#comment-198092</guid>
		<description>If we all keep squinting, we&#039;ll get there. The tendency is to look at W2.0 apps and talk about them as if they will work the same in the enterprise. 

For one, all your incentives and permissions in W2.0 environment are focused on the individual. In Facebook or twitter, the concern is who do you connect to? who can see your info? who do you follow? and so on. 

By contrast, in the enterprise, content is organized around groups, projects, or departments which may see individuals come and go. Take an engineering team - the lead users may leave the company as a new crop comes in. The content &quot;belongs&quot; to the product line as much or more than to the individuals who authored it. 

How about a consulting company doing a customer case? An expert may be brought into a customer case blog for just long enough to contribute. After even a short period, the expert may be blocked out of the continuing conversation. 

With respect to the security related differences, see &lt;a href=&quot;http://traction.tractionsoftware.com/traction/permalink/Blog837&quot; rel=&quot;nofollow&quot;&gt;

I&#039;ll agree that data will become more accessible and activities of all sorts will become more transparent as network effects are realized to be more important than privacy (or simply hoarding) benefits. But the way we get there in the Enterprise may borrow some principals from W2.0, while being careful not to simply clone it.</description>
		<content:encoded><![CDATA[<p>If we all keep squinting, we&#8217;ll get there. The tendency is to look at W2.0 apps and talk about them as if they will work the same in the enterprise. </p>
<p>For one, all your incentives and permissions in W2.0 environment are focused on the individual. In Facebook or twitter, the concern is who do you connect to? who can see your info? who do you follow? and so on. </p>
<p>By contrast, in the enterprise, content is organized around groups, projects, or departments which may see individuals come and go. Take an engineering team &#8211; the lead users may leave the company as a new crop comes in. The content &#8220;belongs&#8221; to the product line as much or more than to the individuals who authored it. </p>
<p>How about a consulting company doing a customer case? An expert may be brought into a customer case blog for just long enough to contribute. After even a short period, the expert may be blocked out of the continuing conversation. </p>
<p>With respect to the security related differences, see <a href="http://traction.tractionsoftware.com/traction/permalink/Blog837" rel="nofollow"></p>
<p>I&#8217;ll agree that data will become more accessible and activities of all sorts will become more transparent as network effects are realized to be more important than privacy (or simply hoarding) benefits. But the way we get there in the Enterprise may borrow some principals from W2.0, while being careful not to simply clone it.</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

