<?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: Geting users onboard the Enterprise 2.0 train</title>
	<atom:link href="http://www.bluethots.com/2009/04/06/geting-users-onboard-the-enterprise-20-train/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bluethots.com/2009/04/06/geting-users-onboard-the-enterprise-20-train/</link>
	<description>Synergising People and Technology</description>
	<lastBuildDate>Sun, 09 Oct 2011 08:37:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Sean Lew</title>
		<link>http://www.bluethots.com/2009/04/06/geting-users-onboard-the-enterprise-20-train/comment-page-1/#comment-4577</link>
		<dc:creator>Sean Lew</dc:creator>
		<pubDate>Mon, 06 Apr 2009 10:37:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluethots.com/?p=459#comment-4577</guid>
		<description>I feel that projects is the best place to start using wikis. Reason being, there is a task at hand and in the initial stages of a project there is generally alot of unknowns and Wikis allow people to collaborate and share information efficiently. 

Wouldn&#039;t it be great if the content of a book can be found in only one place? I would like to see all the information in the Wiki and not some in the wiki and some in a document and other in a powerpoint pack. 

I have personally used wikis to develop a almost 300 page document and it was extremely successful. 

Yes, there are rubbish around that needs to be clean and that is an issue organisations have to look into. 

All I am saying in this post is how to increase user adoption and some of the stuff non-E2 users think through. Wikis are great but they must be strategically planned and implemented. Can&#039;t just leave it and see what happens. Adoption is key to the success of it.</description>
		<content:encoded><![CDATA[<p>I feel that projects is the best place to start using wikis. Reason being, there is a task at hand and in the initial stages of a project there is generally alot of unknowns and Wikis allow people to collaborate and share information efficiently. </p>
<p>Wouldn&#8217;t it be great if the content of a book can be found in only one place? I would like to see all the information in the Wiki and not some in the wiki and some in a document and other in a powerpoint pack. </p>
<p>I have personally used wikis to develop a almost 300 page document and it was extremely successful. </p>
<p>Yes, there are rubbish around that needs to be clean and that is an issue organisations have to look into. </p>
<p>All I am saying in this post is how to increase user adoption and some of the stuff non-E2 users think through. Wikis are great but they must be strategically planned and implemented. Can&#8217;t just leave it and see what happens. Adoption is key to the success of it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jo Jordan</title>
		<link>http://www.bluethots.com/2009/04/06/geting-users-onboard-the-enterprise-20-train/comment-page-1/#comment-4575</link>
		<dc:creator>Jo Jordan</dc:creator>
		<pubDate>Mon, 06 Apr 2009 09:45:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.bluethots.com/?p=459#comment-4575</guid>
		<description>Sean, Wikis have another value.  They are a place to store projects in their early stages. All those flash in the pan ideas that seem great.

Set up a wiki, store, and see if anyone goes back to it.

In short you article begs the questions of what wikis are for.  You seem to have set up a unspoken criterion that they should be a quickly written book.  Bringing criteria from the past?

Use them to store scraps.  Have lots.  

They are are also useful for writing long documents.  Each section can be broken down to a page so the job becomes manageable and they can be private or public depending on a person&#039;s temperament.

Mess is part of the internet.  Personally, I am tired of the debris and trying to clean up my parts - so perhaps that&#039;s IT&#039;s job. Make sure the &#039;park&#039; is available for us to &#039;play in the sun&#039; and also the rubbish bins so we can clean up after each other.  And then maybe a lost property section to store stuff that seems abandoned.</description>
		<content:encoded><![CDATA[<p>Sean, Wikis have another value.  They are a place to store projects in their early stages. All those flash in the pan ideas that seem great.</p>
<p>Set up a wiki, store, and see if anyone goes back to it.</p>
<p>In short you article begs the questions of what wikis are for.  You seem to have set up a unspoken criterion that they should be a quickly written book.  Bringing criteria from the past?</p>
<p>Use them to store scraps.  Have lots.  </p>
<p>They are are also useful for writing long documents.  Each section can be broken down to a page so the job becomes manageable and they can be private or public depending on a person&#8217;s temperament.</p>
<p>Mess is part of the internet.  Personally, I am tired of the debris and trying to clean up my parts &#8211; so perhaps that&#8217;s IT&#8217;s job. Make sure the &#8216;park&#8217; is available for us to &#8216;play in the sun&#8217; and also the rubbish bins so we can clean up after each other.  And then maybe a lost property section to store stuff that seems abandoned.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

