<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Lessons learned from enterprise wikis</title>
	<atom:link href="http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/feed/" rel="self" type="application/rss+xml" />
	<link>http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/</link>
	<description>New and improved with just a hint of lemon</description>
	<lastBuildDate>Mon, 28 Dec 2009 20:05:05 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: alfred</title>
		<link>http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-73447</link>
		<dc:creator>alfred</dc:creator>
		<pubDate>Mon, 14 Dec 2009 17:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-73447</guid>
		<description>Wow this was potentially one of the most intelligent blurbs I&#039;ve had the chance to come across on the topic so far. I do not have any idea where you gather up all of your information but keep it coming! I am gunna send some people your way to read this. Fantastic, totally awesome. I&#039;m have just started getting into crafting articles myself, nothing remotely close to your writing skills (ha!) </description>
		<content:encoded><![CDATA[<p>Wow this was potentially one of the most intelligent blurbs I&#8217;ve had the chance to come across on the topic so far. I do not have any idea where you gather up all of your information but keep it coming! I am gunna send some people your way to read this. Fantastic, totally awesome. I&#8217;m have just started getting into crafting articles myself, nothing remotely close to your writing skills (ha!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Workplace Blog &#187; Blog Archive &#187; More Avenue A &#124; Razorfish wiki talk</title>
		<link>http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-71472</link>
		<dc:creator>The Workplace Blog &#187; Blog Archive &#187; More Avenue A &#124; Razorfish wiki talk</dc:creator>
		<pubDate>Wed, 27 Feb 2008 19:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-71472</guid>
		<description>[...] his blog, David Strom highlighted a conversation he had with Ray Velez about the Avenue A &#124; Razorfish wiki. [...]</description>
		<content:encoded><![CDATA[<p>[...] his blog, David Strom highlighted a conversation he had with Ray Velez about the Avenue A | Razorfish wiki. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is Mediawiki an Enterprise Wiki? &#171; Radiowalker: Tech Business Beat</title>
		<link>http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-57063</link>
		<dc:creator>Is Mediawiki an Enterprise Wiki? &#171; Radiowalker: Tech Business Beat</dc:creator>
		<pubDate>Wed, 17 Oct 2007 12:10:29 +0000</pubDate>
		<guid isPermaLink="false">http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-57063</guid>
		<description>[...] description of what is entailed in making Mediawiki into an enterprise wiki, David Strom reports useful, practical information for anyone evaluating enterprise wikis. Harvard Business School professor Andrew McAfee&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] description of what is entailed in making Mediawiki into an enterprise wiki, David Strom reports useful, practical information for anyone evaluating enterprise wikis. Harvard Business School professor Andrew McAfee&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray Velez</title>
		<link>http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-7407</link>
		<dc:creator>Ray Velez</dc:creator>
		<pubDate>Sun, 25 Feb 2007 00:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-7407</guid>
		<description>There&#039;s a couple of points I would like to add to this thread.

One thing is that a technology architect/developer is needed regardless of the solutions, whether saas, commercial in-house or open source in-house. Someone will need to invest time to install, configure, connect to active directory, etc. When a new version comes along or when active directory stops connecting after an upgrade are all examples of when a technologist is needed. There are lots of scenarios that require technology support.
The second piece which wasn&#039;t clear in the discussion I had with David was that the intern and part-time technologists supporting the wiki were also helping add content and format the wiki. Sometimes I would give the intern a directory full of documents that I was getting tired of sending around and ask them to upload. A time consuming activity regardless of which tool is being used. The intern would also help support people with activities such as, where do I click the edit tab, how do I rollback content, etc. 
Lastly, a lot of the work invested was installing and configuring plug-ins. For example, we&#039;ve added a plug-in that allows people to protect content. The nice part of working with a tool like mediawiki is that there are lots of plug-ins being added on a periodic basis.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a couple of points I would like to add to this thread.</p>
<p>One thing is that a technology architect/developer is needed regardless of the solutions, whether saas, commercial in-house or open source in-house. Someone will need to invest time to install, configure, connect to active directory, etc. When a new version comes along or when active directory stops connecting after an upgrade are all examples of when a technologist is needed. There are lots of scenarios that require technology support.<br />
The second piece which wasn&#8217;t clear in the discussion I had with David was that the intern and part-time technologists supporting the wiki were also helping add content and format the wiki. Sometimes I would give the intern a directory full of documents that I was getting tired of sending around and ask them to upload. A time consuming activity regardless of which tool is being used. The intern would also help support people with activities such as, where do I click the edit tab, how do I rollback content, etc.<br />
Lastly, a lot of the work invested was installing and configuring plug-ins. For example, we&#8217;ve added a plug-in that allows people to protect content. The nice part of working with a tool like mediawiki is that there are lots of plug-ins being added on a periodic basis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: radiowalker</title>
		<link>http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-7349</link>
		<dc:creator>radiowalker</dc:creator>
		<pubDate>Fri, 16 Feb 2007 04:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://strom.wordpress.com/2007/02/13/lessons-learned-from-enterprise-wikis/#comment-7349</guid>
		<description>This is a practical report on what it takes to make Mediawiki work in a sophistcated enterprise setting. No surprise. Andrew  McAfee in my mind missed these key points, although he shows that Razorfish seems to have done an excellent job at implementation. I would expect that from a design agency. I thought your lessons highlight what choosing an open source wiki really means for an enterprise: it&#039;s not an enterprise wiki until you make it one. Thanks for the basis for my blog today at wwww.radiowalker.com -- Jeffrey</description>
		<content:encoded><![CDATA[<p>This is a practical report on what it takes to make Mediawiki work in a sophistcated enterprise setting. No surprise. Andrew  McAfee in my mind missed these key points, although he shows that Razorfish seems to have done an excellent job at implementation. I would expect that from a design agency. I thought your lessons highlight what choosing an open source wiki really means for an enterprise: it&#8217;s not an enterprise wiki until you make it one. Thanks for the basis for my blog today at wwww.radiowalker.com &#8212; Jeffrey</p>
]]></content:encoded>
	</item>
</channel>
</rss>
