<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Adi Gaskell says... &#187; Knowledge Management</title>
	<atom:link href="http://www.adigaskell.org/blog/tag/knowledge-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adigaskell.org/blog</link>
	<description>The views and musings of me, myself and I</description>
	<lastBuildDate>Thu, 29 Jul 2010 14:53:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What would get employees talking to each other?</title>
		<link>http://www.adigaskell.org/blog/2009/11/20/what-would-get-employees-talking-to-each-other/</link>
		<comments>http://www.adigaskell.org/blog/2009/11/20/what-would-get-employees-talking-to-each-other/#comments</comments>
		<pubDate>Fri, 20 Nov 2009 15:20:36 +0000</pubDate>
		<dc:creator>adi</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[Community]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[km]]></category>
		<category><![CDATA[Knowledge Management]]></category>
		<category><![CDATA[LinkedIn]]></category>
		<category><![CDATA[Online Communities]]></category>
		<category><![CDATA[Social network]]></category>
		<category><![CDATA[Social network service]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.adigaskell.org/blog/?p=229</guid>
		<description><![CDATA[SalesForce released a new enterprise social networking service today called Chatter with the aim of encouraging people to do what they do on Facebook et al with their colleagues.
It&#8217;s one of those issues that&#8217;s considerably easier to suggest than to implement as the two environments are very, very different.  In community building there is [...]]]></description>
			<content:encoded><![CDATA[<p><a class="zem_slink" title="Salesforce" rel="homepage" href="http://www.salesforce.com/">SalesForce</a> released a new enterprise social networking service today called <em>Chatter</em> with the aim of encouraging people to do what they do on Facebook et al with their colleagues.</p>
<p>It&#8217;s one of those issues that&#8217;s considerably easier to suggest than to implement as the two environments are very, very different.  In community building there is an oft used rule of thumb that for every 100 people looking at a social community, 90 will just read, 9 will reply to topics and just 1 will start new discussions.  As with all rules of thumb this isn&#8217;t going to be the case every time but it&#8217;s worth considering that whereas Facebook, <a class="zem_slink" title="LinkedIn" rel="homepage" href="http://www.linkedin.com">LinkedIn</a> et al have the numbers to make this work, in your own internal network your numbers will likely be much less.</p>
<p>As with most things in life, it&#8217;s worth investigating what you wish to get out of this before you get started.</p>
<p>If it&#8217;s gaining a more social understanding of your employees then it&#8217;s probably safe to say that use of existing platforms such as Facebook is likely to yield better results.  There are already many &#8216;I work at &#8230;&#8217; style groups on Facebook so that would seem a good opportunity to mingle with your employees in their natural habitat.</p>
<p>If however you&#8217;re looking to improve your corporate knowledge base and encourage knowledge sharing then this offers much more potential.  Of course building a platform does not mean people will come, so here are a few steps you can take to encourage knowledge sharing within your company.</p>
<p><strong>Tips for encouraging knowledge sharing</strong></p>
<ol>
<li>Outline your vision for this.  You first need to create a culture of knowledge sharing so need to communicate the vision that this is a positive thing both for the individual and the company.</li>
<li>Reinforce through actions.  You then need to reinforce this vision through actions.  Reward positive behaviour, not just financially but through praise and recognition.</li>
<li>Start with the natives.  There will inevitably be people who will take to this like a duck to water.  Start with these people and get them sharing knowledge extensively.</li>
<li>Use success stories to cross the chasm.  Use any success stories that these early adaptors achieve to help sell it to the rest of your employees.</li>
<li>Lead by example.  You have to do what you&#8217;re asking people to do so you should be one of the main users of your internal network.</li>
<li>Embed into human processes.  If you can get these positive behaviours included within inductions for instance it will help reinforce behaviour and create the right kind of knowledge sharing culture.</li>
</ol>
<p><strong>Don&#8217;t forget to look outside as well as inside</strong></p>
<p>If you can get that far then you&#8217;ve done very well, but don&#8217;t restrict yourself to improving the knowledge sharing within your company walls.  There is a whole load of knowledge outside of your company.  Communities of practice exist in a vast array of areas that can see your employees tapping into the knowledge base of thousands of peers from around the world.  The CMI for instance is soon to launch a <a title="management community" href="http://www.managers.org.uk/social_media" target="_blank">management community</a> that will be a great place for managers to learn from others.  Look out for these kind of opportunities and encourage staff to learn from these communities.  This kind of social media is miles from the waste of time that Facebook et al can appear to be.</p>
<p>I&#8217;m a great believer in the power of communities and getting employees to talk to one another is a great thing.  It would be interesting to hear from people that have done this successfully.</p>
<div class="zemanta-pixie" style="margin-top: 10px; height: 15px;"><a class="zemanta-pixie-a" title="Reblog this post [with Zemanta]" href="http://reblog.zemanta.com/zemified/cda7f2a9-f564-4f89-bc99-dfc13633f398/"><img class="zemanta-pixie-img" style="border: medium none; float: right;" src="http://img.zemanta.com/reblog_e.png?x-id=cda7f2a9-f564-4f89-bc99-dfc13633f398" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script src="http://static.zemanta.com/readside/loader.js" type="text/javascript"></script></span></div>
]]></content:encoded>
			<wfw:commentRss>http://www.adigaskell.org/blog/2009/11/20/what-would-get-employees-talking-to-each-other/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How often do you hold project post-mortems?</title>
		<link>http://www.adigaskell.org/blog/2008/10/17/how-often-do-you-hold-project-post-mortems/</link>
		<comments>http://www.adigaskell.org/blog/2008/10/17/how-often-do-you-hold-project-post-mortems/#comments</comments>
		<pubDate>Fri, 17 Oct 2008 07:59:43 +0000</pubDate>
		<dc:creator>adi</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[Best practice]]></category>
		<category><![CDATA[Case study]]></category>
		<category><![CDATA[Education]]></category>
		<category><![CDATA[Employment]]></category>
		<category><![CDATA[improvement]]></category>
		<category><![CDATA[Knowledge Management]]></category>
		<category><![CDATA[mistakes]]></category>
		<category><![CDATA[training]]></category>

		<guid isPermaLink="false">http://www.adigaskell.org/blog/?p=46</guid>
		<description><![CDATA[I&#8217;m sure many of you have made mistakes in the workplace, or worked on projects that have failed for whatever reason.  But how many of you have subsequently conducted training on those mistakes, analysing what happened, why it happened and how the same mistakes can be prevented in future?
Obviously a key facet of knowledge management [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m sure many of you have made mistakes in the workplace, or worked on projects that have failed for whatever reason.  But how many of you have subsequently conducted training on those mistakes, analysing what happened, why it happened and how the same mistakes can be prevented in future?</p>
<p>Obviously a key facet of <a class="zem_slink" title="Knowledge Management" rel="wikipedia" href="http://en.wikipedia.org/wiki/Knowledge_Management">knowledge management</a> is the flow of information within an organisation, both good and bad.  Freedom of expression is key, but there seems to be a lack of regular dialogue concerning project failures, at least within the companies I have worked for.</p>
<p>As <a class="zem_slink" title="Albert Einstein" rel="wikipedia" href="http://en.wikipedia.org/wiki/Albert_Einstein">Einstein</a> said, insanity is &#8220;<em>doing the same thing</em> over and over again and <em>expecting different results</em>.&#8221;</p>
<p>The reason for this blog was a study I read last night concerning the training given to a bunch of firemen in America.  The researchers wanted to determine whether training that focused on the mistakes others had made in the past worked better at minimising errors than training that focused on best practice.  Two groups were given case study based training, with one group receiving case studies of failed missions, and the other receiving case studies of successful missions.  When the data was analysed it was found that the firemen that received the training on failure had improved judgement on missions than those that didn&#8217;t.</p>
<p>In a corporate environment this is often tricky because by pinpointing failures it can feel as though an employee is being picked upon.  Perhaps in an individual setting this can be intensified, but if the project team are given the opportunity to analyse performance collectively and improvements made then it could go a long way to stopping those failures occurring again.</p>
<p>It would be good to hear from you.  Does your organisation conduct training on failed projects as well as successful ones?</p>
<div class="zemanta-pixie" style="margin-top: 10px; height: 15px;"><a class="zemanta-pixie-a" title="Zemified by Zemanta" href="http://reblog.zemanta.com/zemified/9b326a6d-c1b1-4ee1-af98-d0996468d32e/"><img class="zemanta-pixie-img" style="border: medium none; float: right;" src="http://img.zemanta.com/reblog_e.png?x-id=9b326a6d-c1b1-4ee1-af98-d0996468d32e" alt="Reblog this post [with Zemanta]" /></a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.adigaskell.org/blog/2008/10/17/how-often-do-you-hold-project-post-mortems/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
