<?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: Success Factors in Knowledge Management</title>
	<atom:link href="http://www.pmhut.com/success-factors-in-knowledge-management/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/success-factors-in-knowledge-management</link>
	<description></description>
	<pubDate>Sun, 12 Feb 2012 02:19:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Shawn Ryan</title>
		<link>http://www.pmhut.com/success-factors-in-knowledge-management/comment-page-1#comment-1566</link>
		<dc:creator>Shawn Ryan</dc:creator>
		<pubDate>Tue, 12 May 2009 19:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3100#comment-1566</guid>
		<description>Great guide for project specific KM activities.

The next step to consider is ensuring you have a framework in place to transition from project based KM activities to ongoing activities. 

There are countless idle share drives, collaboration sites, and wiki's left as artifacts on corporate servers because there was little thought over who would be accountable for continuing to grow the knowledge base. 

A simple way I've found to avoid this problem is to put the KM strucutre in place at the start of any project, assign metrics, and owners.  

Then you have the entire duration of the project to build habits for the team members and the managers who will be responsible for these activities post implementation.

-Shawn</description>
		<content:encoded><![CDATA[<p>Great guide for project specific KM activities.</p>
<p>The next step to consider is ensuring you have a framework in place to transition from project based KM activities to ongoing activities. </p>
<p>There are countless idle share drives, collaboration sites, and wiki&#8217;s left as artifacts on corporate servers because there was little thought over who would be accountable for continuing to grow the knowledge base. </p>
<p>A simple way I&#8217;ve found to avoid this problem is to put the KM strucutre in place at the start of any project, assign metrics, and owners.  </p>
<p>Then you have the entire duration of the project to build habits for the team members and the managers who will be responsible for these activities post implementation.</p>
<p>-Shawn</p>
]]></content:encoded>
	</item>
</channel>
</rss>

