<?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: Why Enterprise 2.0 Will Fail</title>
	<atom:link href="http://www.infovark.com/2010/03/01/why-enterprise-2-0-will-fail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.infovark.com/2010/03/01/why-enterprise-2-0-will-fail/</link>
	<description>Digging the world of Enterprise 2.0</description>
	<lastBuildDate>Fri, 10 Sep 2010 08:14:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Richard Veryard</title>
		<link>http://www.infovark.com/2010/03/01/why-enterprise-2-0-will-fail/comment-page-1/#comment-962</link>
		<dc:creator>Richard Veryard</dc:creator>
		<pubDate>Wed, 14 Apr 2010 11:28:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.infovark.com/?p=1827#comment-962</guid>
		<description>I agree that shifting away from firewall-based security is a significant strategic move for an organization, not just infrastructure but also political. There are some political issues that would have to be tackled, if the organization is to achieve any potential benefits from Enterprise 2.0.

But the shift away from firewall (sometimes called Deperimeterization) doesn&#039;t necessarily entail the second shift Dean mentions, from a &#039;network of networks&#039; paradigm to a &#039;unified network&#039; approach, and I am not advocating this.  There will perhaps always be limits to interoperability, and there will always be some structure to the network of networks, but this structure will be more open and innovative, and not driven primarily by an obsolete security architecture.</description>
		<content:encoded><![CDATA[<p>I agree that shifting away from firewall-based security is a significant strategic move for an organization, not just infrastructure but also political. There are some political issues that would have to be tackled, if the organization is to achieve any potential benefits from Enterprise 2.0.</p>
<p>But the shift away from firewall (sometimes called Deperimeterization) doesn&#8217;t necessarily entail the second shift Dean mentions, from a &#8216;network of networks&#8217; paradigm to a &#8216;unified network&#8217; approach, and I am not advocating this.  There will perhaps always be limits to interoperability, and there will always be some structure to the network of networks, but this structure will be more open and innovative, and not driven primarily by an obsolete security architecture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean</title>
		<link>http://www.infovark.com/2010/03/01/why-enterprise-2-0-will-fail/comment-page-1/#comment-903</link>
		<dc:creator>Dean</dc:creator>
		<pubDate>Mon, 15 Mar 2010 14:51:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.infovark.com/?p=1827#comment-903</guid>
		<description>Hey Richard,

It&#039;s true that many forward-thinking organizations are becoming more transparent, and the borders between them are becoming less distinct. Still, eliminating the firewall altogether would require a lot of infrastructure changes. For one thing, until IPv6 is implemented worldwide, there simply aren&#039;t enough IP addresses for everyone. Network address translation (NAT) makes the computers inside the corporate network opaque to outsiders.

An even bigger challenge is the political one. Changing the Internet from a &quot;network of networks&quot; paradigm to a &quot;unified network&quot; approach would require far more coordination than most companies -- and countries -- would be willing to undertake.

But I agree that the presence of company firewalls in the first place is an unspoken assumption of mine. Maybe it should be item #3 in my Enterprise 2.0 distortion field?</description>
		<content:encoded><![CDATA[<p>Hey Richard,</p>
<p>It&#8217;s true that many forward-thinking organizations are becoming more transparent, and the borders between them are becoming less distinct. Still, eliminating the firewall altogether would require a lot of infrastructure changes. For one thing, until IPv6 is implemented worldwide, there simply aren&#8217;t enough IP addresses for everyone. Network address translation (NAT) makes the computers inside the corporate network opaque to outsiders.</p>
<p>An even bigger challenge is the political one. Changing the Internet from a &#8220;network of networks&#8221; paradigm to a &#8220;unified network&#8221; approach would require far more coordination than most companies &#8212; and countries &#8212; would be willing to undertake.</p>
<p>But I agree that the presence of company firewalls in the first place is an unspoken assumption of mine. Maybe it should be item #3 in my Enterprise 2.0 distortion field?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Veryard</title>
		<link>http://www.infovark.com/2010/03/01/why-enterprise-2-0-will-fail/comment-page-1/#comment-895</link>
		<dc:creator>Richard Veryard</dc:creator>
		<pubDate>Sat, 13 Mar 2010 13:03:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.infovark.com/?p=1827#comment-895</guid>
		<description>I think the main problem with the case for &quot;E2.0 inside the firewall&quot; is the word &quot;firewall&quot;, which represents an outdated but still common attitude towards maintaining organizational boundaries. I wouldn&#039;t be at all surprised if an organization that relies on firewalls struggles to get the benefits from open distributed business and technology, including Enterprise 2.0.</description>
		<content:encoded><![CDATA[<p>I think the main problem with the case for &#8220;E2.0 inside the firewall&#8221; is the word &#8220;firewall&#8221;, which represents an outdated but still common attitude towards maintaining organizational boundaries. I wouldn&#8217;t be at all surprised if an organization that relies on firewalls struggles to get the benefits from open distributed business and technology, including Enterprise 2.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vanderwal</title>
		<link>http://www.infovark.com/2010/03/01/why-enterprise-2-0-will-fail/comment-page-1/#comment-890</link>
		<dc:creator>vanderwal</dc:creator>
		<pubDate>Fri, 12 Mar 2010 18:04:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.infovark.com/?p=1827#comment-890</guid>
		<description>I largely agree, but there is another reason why E2.0 is being brought in, which is many mid to larger firms moved to enterprise portals (enterprise CMS) to provide consistency, ease of management of information, and one stop interface to get to internal resources. The downside is so few people are trained well enough in these large systems very little information and resources make it into the services and tools. It has inhibited people from adding and modifying information as needed and there is no collective intelligence available. 

There is a balance of personal employee value and system organization focus needed with these tools and services. Sadly, much of the selling of the product is to people who only see the systems organization benefits, without any grasp that the tools will have limited adoption, long term engagement by employees, and therefore limited value to the organization if the employee value focus is not perceived. The employee value is much harder and complicated to grasp and the tools have to do a much better job at embracing how humans are social (their needs, fears, concerns, and various understandings of these dynamics as 1-to-1 social, small group, large group, and whole organization social interaction needs from the perspective of the person sharing information).</description>
		<content:encoded><![CDATA[<p>I largely agree, but there is another reason why E2.0 is being brought in, which is many mid to larger firms moved to enterprise portals (enterprise CMS) to provide consistency, ease of management of information, and one stop interface to get to internal resources. The downside is so few people are trained well enough in these large systems very little information and resources make it into the services and tools. It has inhibited people from adding and modifying information as needed and there is no collective intelligence available. </p>
<p>There is a balance of personal employee value and system organization focus needed with these tools and services. Sadly, much of the selling of the product is to people who only see the systems organization benefits, without any grasp that the tools will have limited adoption, long term engagement by employees, and therefore limited value to the organization if the employee value focus is not perceived. The employee value is much harder and complicated to grasp and the tools have to do a much better job at embracing how humans are social (their needs, fears, concerns, and various understandings of these dynamics as 1-to-1 social, small group, large group, and whole organization social interaction needs from the perspective of the person sharing information).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: You get what (someone else) paid for &#124; Infovark</title>
		<link>http://www.infovark.com/2010/03/01/why-enterprise-2-0-will-fail/comment-page-1/#comment-889</link>
		<dc:creator>You get what (someone else) paid for &#124; Infovark</dc:creator>
		<pubDate>Fri, 12 Mar 2010 17:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.infovark.com/?p=1827#comment-889</guid>
		<description>[...] post about the impending failure of Enterprise 2.0 got me thinking a lot about the strange nature of selling enterprise software, and of selling [...]</description>
		<content:encoded><![CDATA[<p>[...] post about the impending failure of Enterprise 2.0 got me thinking a lot about the strange nature of selling enterprise software, and of selling [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
