<?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: Tear Down These Walls!?!?</title>
	<atom:link href="http://andrewmcafee.org/2007/02/tear_down_these_walls/feed/" rel="self" type="application/rss+xml" />
	<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/</link>
	<description>The Business Impact of IT</description>
	<lastBuildDate>Fri, 12 Mar 2010 00:13:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: pixbook</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-18589</link>
		<dc:creator>pixbook</dc:creator>
		<pubDate>Fri, 31 Jul 2009 06:08:06 +0000</pubDate>
		<guid isPermaLink="false">#comment-18589</guid>
		<description>&lt;a href=&quot;http://www.101waystomakemoney.com&quot; rel=&quot;nofollow&quot;&gt;Ways to make money&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Great post. i do agree with your ideas.</description>
		<content:encoded><![CDATA[<p><a href="http://www.101waystomakemoney.com" rel="nofollow">Ways to make money</a></p>
<p>Great post. i do agree with your ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isis</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-14055</link>
		<dc:creator>Isis</dc:creator>
		<pubDate>Fri, 05 Jun 2009 15:02:42 +0000</pubDate>
		<guid isPermaLink="false">#comment-14055</guid>
		<description>Hey there, I agree too!&lt;br&gt;&lt;br&gt;Rina</description>
		<content:encoded><![CDATA[<p>Hey there, I agree too!</p>
<p>Rina</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: home repairs</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-11211</link>
		<dc:creator>home repairs</dc:creator>
		<pubDate>Sun, 12 Apr 2009 15:57:41 +0000</pubDate>
		<guid isPermaLink="false">#comment-11211</guid>
		<description>I agree with John Howard comment..what he trying to tell in his comment is such a valid point according to me..</description>
		<content:encoded><![CDATA[<p>I agree with John Howard comment..what he trying to tell in his comment is such a valid point according to me..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew McAfee: I know 2.0 when I see it &#8212; Informal Learning Blog</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-4629</link>
		<dc:creator>Andrew McAfee: I know 2.0 when I see it &#8212; Informal Learning Blog</dc:creator>
		<pubDate>Tue, 10 Feb 2009 15:20:23 +0000</pubDate>
		<guid isPermaLink="false">#comment-4629</guid>
		<description>[...] many small and mutually inaccessible environments, instead of one big one. The tendency to build walled gardens is evidently a deep-seated one, and one that should be questioned far more often than is currently [...]</description>
		<content:encoded><![CDATA[<p>[...] many small and mutually inaccessible environments, instead of one big one. The tendency to build walled gardens is evidently a deep-seated one, and one that should be questioned far more often than is currently [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marissa</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-3018</link>
		<dc:creator>Marissa</dc:creator>
		<pubDate>Wed, 07 Jan 2009 16:32:21 +0000</pubDate>
		<guid isPermaLink="false">#comment-3018</guid>
		<description>You ask...&quot;why would you post your problem only on the lab wiki when you could post it company-wide&quot;?

I think my very post illustrates why not. Who am i? what are my credentials?

Legal and medical topics on the internet illustrate this point. Yes, maybe John Doe knows why im hacking up blood or what my rights are during an illegal search, but wouldn&#039;t i be more likely to find the answer I&#039;m looking for by questioning just doctors or just lawyers? 

Sort of reminds me of dealing with my father-in-law. hes an &quot;expert&quot; on everything. sometimes i just prefer my doctors diagnosis instead of his.</description>
		<content:encoded><![CDATA[<p>You ask&#8230;&#8221;why would you post your problem only on the lab wiki when you could post it company-wide&#8221;?</p>
<p>I think my very post illustrates why not. Who am i? what are my credentials?</p>
<p>Legal and medical topics on the internet illustrate this point. Yes, maybe John Doe knows why im hacking up blood or what my rights are during an illegal search, but wouldn&#8217;t i be more likely to find the answer I&#8217;m looking for by questioning just doctors or just lawyers? </p>
<p>Sort of reminds me of dealing with my father-in-law. hes an &#8220;expert&#8221; on everything. sometimes i just prefer my doctors diagnosis instead of his.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lauren</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-3017</link>
		<dc:creator>lauren</dc:creator>
		<pubDate>Wed, 24 Sep 2008 14:23:23 +0000</pubDate>
		<guid isPermaLink="false">#comment-3017</guid>
		<description>Just to play devils advocate here, We recently set up a department wide wiki, and a few other wikis for other departments. The reason for doing it this way is because people naturally have a predisposition for nurturing their own &#039;babies&#039;. Our dept&#039;s wiki thrives because we&#039;re all actively involved and care about its success, for the benefit of our group. The other departments wikis aren&#039;t used, for whatever reason, i dont know. What i do know is that our wiki is just large enough to be useful and not too large that it cannot be conquered. Sometimes you have to take small steps, especially when each individual may only care about the success of him / herself, and not necessarily the benefit of the company as a whole. I suppose its why were capitalists and not communists.</description>
		<content:encoded><![CDATA[<p>Just to play devils advocate here, We recently set up a department wide wiki, and a few other wikis for other departments. The reason for doing it this way is because people naturally have a predisposition for nurturing their own &#8216;babies&#8217;. Our dept&#8217;s wiki thrives because we&#8217;re all actively involved and care about its success, for the benefit of our group. The other departments wikis aren&#8217;t used, for whatever reason, i dont know. What i do know is that our wiki is just large enough to be useful and not too large that it cannot be conquered. Sometimes you have to take small steps, especially when each individual may only care about the success of him / herself, and not necessarily the benefit of the company as a whole. I suppose its why were capitalists and not communists.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Iliff</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-3016</link>
		<dc:creator>Bob Iliff</dc:creator>
		<pubDate>Thu, 01 Mar 2007 15:51:28 +0000</pubDate>
		<guid isPermaLink="false">#comment-3016</guid>
		<description>I honstly thought the idea was that the workers (I&#039;ll include Management)were connected socially, so it&#039;s OK to have several small wikis, loosely joined. If everyone one has the power to invite others because they know the relevance of that person to the wiki&#039;s purpose, however they first connected one to one, what&#039;s the beef? I think this is how you avoid long tailed, pedestrian trafficed wikis, and maintain gardened gardens.</description>
		<content:encoded><![CDATA[<p>I honstly thought the idea was that the workers (I&#8217;ll include Management)were connected socially, so it&#8217;s OK to have several small wikis, loosely joined. If everyone one has the power to invite others because they know the relevance of that person to the wiki&#8217;s purpose, however they first connected one to one, what&#8217;s the beef? I think this is how you avoid long tailed, pedestrian trafficed wikis, and maintain gardened gardens.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Itamar Shamshins</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-3015</link>
		<dc:creator>Itamar Shamshins</dc:creator>
		<pubDate>Sat, 24 Feb 2007 21:15:32 +0000</pubDate>
		<guid isPermaLink="false">#comment-3015</guid>
		<description>John, thanks for clarifying this to me. I had a gut feeling that information workers  should/will adapt to the attention allocation issue during the run of business but wondered how one might explain it to managers in order to get support for implementing E2.0 in the first place. Your input is valuable to me. 

Would you say that organizations that have a large investment in customer care can benefit from E2.0 in the same way? I tend to think of several thousand Customer Service Representatives as an army of zombies that has a huge collective IQ that is very hard to tap. These guys are usually fed information with a spoon and their time expenditure is closely monitored. And yet they own a lot of knowledge regarding what customers want, how customers feel, what&#039;s working vs. what&#039;s not working etc. 

I can envision a CSR adding clarifications on a corporate wiki after finding out answers for a customer. I find it hard to envision anyone letting that same CSR editorial access to the knowledge management system in the first place.

I&#039;m wondering if and when managers will take the leap and implement E2.0 technologies for CSRs, bank clerks and others and whether accountability will help them make this decision (seeing as accountability is possible thanks to strong authentication within the corporate network). It&#039;s interesting to think that accountability can be a powerful tool for implementing E2.0 considering that it has a much smaller role in the proliferation of Web 2.0, though one is an offshoot of the other.

I&#039;m slightly off topic, so I think I&#039;ll stop here.</description>
		<content:encoded><![CDATA[<p>John, thanks for clarifying this to me. I had a gut feeling that information workers  should/will adapt to the attention allocation issue during the run of business but wondered how one might explain it to managers in order to get support for implementing E2.0 in the first place. Your input is valuable to me. </p>
<p>Would you say that organizations that have a large investment in customer care can benefit from E2.0 in the same way? I tend to think of several thousand Customer Service Representatives as an army of zombies that has a huge collective IQ that is very hard to tap. These guys are usually fed information with a spoon and their time expenditure is closely monitored. And yet they own a lot of knowledge regarding what customers want, how customers feel, what&#8217;s working vs. what&#8217;s not working etc. </p>
<p>I can envision a CSR adding clarifications on a corporate wiki after finding out answers for a customer. I find it hard to envision anyone letting that same CSR editorial access to the knowledge management system in the first place.</p>
<p>I&#8217;m wondering if and when managers will take the leap and implement E2.0 technologies for CSRs, bank clerks and others and whether accountability will help them make this decision (seeing as accountability is possible thanks to strong authentication within the corporate network). It&#8217;s interesting to think that accountability can be a powerful tool for implementing E2.0 considering that it has a much smaller role in the proliferation of Web 2.0, though one is an offshoot of the other.</p>
<p>I&#8217;m slightly off topic, so I think I&#8217;ll stop here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Howard</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-3014</link>
		<dc:creator>John Howard</dc:creator>
		<pubDate>Sat, 24 Feb 2007 10:38:34 +0000</pubDate>
		<guid isPermaLink="false">#comment-3014</guid>
		<description>There are some interesting nuggets here. Questions over attention, access and engagement. Firstly I have no axe to grind with corporate wide solutions, indeed this is the approach we took at the BBC. All the tools we put in were made available to every member of staff if they wished. However I don&#039;t believe that this makes a blind bit of difference to the walled garden problem. There is no substantial difference between running a closed wiki in a department and running a closed wiki space in a corporate system. We didn&#039;t solve the aggregation problem at the time because there were no web based solutions that provided authenticated RSS reading at that time, plus a load of other issues I won&#039;t go into now. But even so, public weblogs and wikis were spidered and returned as part of the search system we had. Private spaces? Well if you were a member or needed access you either knew already or discovered through your colleagues.

Itamar, as for attention allocation, I feel strongly that this fits into the normal run of business. In my experience, people didn&#039;t get side-tracked from their day job, they used their normal coffee, water-cooler, smoke break(!), waiting for edits to render, moments to dip into the Q&amp;A going on in our discussion system to catch Andrews &#039;Broadcast Searches&#039;. One of the most heated debates in our system came when someone accused all the other users of &#039;not doing their jobs because they were always in the discussion forums&#039;. This led to a spate of people adding their current activities to their postings, which revealed that they fitted their posting around their normal work. Remember also the lurkers to writers ratio that seems pretty common across all these sorts of systems, in my experience it seemed to hold true inside the organisation too. When it came to blogs and wikis, people are much more selective and will build their own information footpaths, optimising their own attention, either because they find a useful resource that helps them with their work, or because they find an interesting individual who writes about the business in a revealing way.

Andrew, I so wish you had trackback enabled :)</description>
		<content:encoded><![CDATA[<p>There are some interesting nuggets here. Questions over attention, access and engagement. Firstly I have no axe to grind with corporate wide solutions, indeed this is the approach we took at the BBC. All the tools we put in were made available to every member of staff if they wished. However I don&#8217;t believe that this makes a blind bit of difference to the walled garden problem. There is no substantial difference between running a closed wiki in a department and running a closed wiki space in a corporate system. We didn&#8217;t solve the aggregation problem at the time because there were no web based solutions that provided authenticated RSS reading at that time, plus a load of other issues I won&#8217;t go into now. But even so, public weblogs and wikis were spidered and returned as part of the search system we had. Private spaces? Well if you were a member or needed access you either knew already or discovered through your colleagues.</p>
<p>Itamar, as for attention allocation, I feel strongly that this fits into the normal run of business. In my experience, people didn&#8217;t get side-tracked from their day job, they used their normal coffee, water-cooler, smoke break(!), waiting for edits to render, moments to dip into the Q&#038;A going on in our discussion system to catch Andrews &#8216;Broadcast Searches&#8217;. One of the most heated debates in our system came when someone accused all the other users of &#8216;not doing their jobs because they were always in the discussion forums&#8217;. This led to a spate of people adding their current activities to their postings, which revealed that they fitted their posting around their normal work. Remember also the lurkers to writers ratio that seems pretty common across all these sorts of systems, in my experience it seemed to hold true inside the organisation too. When it came to blogs and wikis, people are much more selective and will build their own information footpaths, optimising their own attention, either because they find a useful resource that helps them with their work, or because they find an interesting individual who writes about the business in a revealing way.</p>
<p>Andrew, I so wish you had trackback enabled <img src='http://andrewmcafee.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Itamar Shamshins</title>
		<link>http://andrewmcafee.org/2007/02/tear_down_these_walls/comment-page-1/#comment-3013</link>
		<dc:creator>Itamar Shamshins</dc:creator>
		<pubDate>Fri, 23 Feb 2007 15:47:54 +0000</pubDate>
		<guid isPermaLink="false">#comment-3013</guid>
		<description>If you can access three &quot;distinct&quot; corporate wikis (as per your example) than they are not distinct. By definition, each wiki will allow the creation of links to the other wikis. You will get one big wiki that is hosted on three separate URLs. If only mutually exclusive access is given to users of those wikis, than RSS and browsers are of no use to close the gap. Am I missing something?

As I see it, the biggest question is of attention allocation. In order for broadcast search to be effective, you need many (all?) people to browse through all published searches. When does the collective time expenditure by employees on blogs wikis and the like reduce productivity to an unacceptable level? How do we optimize attention expenditure of E2.0 vs. &quot;traditional&quot; work (I recognize the fact that there are places where those two overlap)? I&#039;d love to have answers to those questionsÂ…</description>
		<content:encoded><![CDATA[<p>If you can access three &#8220;distinct&#8221; corporate wikis (as per your example) than they are not distinct. By definition, each wiki will allow the creation of links to the other wikis. You will get one big wiki that is hosted on three separate URLs. If only mutually exclusive access is given to users of those wikis, than RSS and browsers are of no use to close the gap. Am I missing something?</p>
<p>As I see it, the biggest question is of attention allocation. In order for broadcast search to be effective, you need many (all?) people to browse through all published searches. When does the collective time expenditure by employees on blogs wikis and the like reduce productivity to an unacceptable level? How do we optimize attention expenditure of E2.0 vs. &#8220;traditional&#8221; work (I recognize the fact that there are places where those two overlap)? I&#8217;d love to have answers to those questionsÂ…</p>
]]></content:encoded>
	</item>
</channel>
</rss>
