<?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>Managing Product Development &#187; knowledge management</title>
	<atom:link href="http://www.jrothman.com/blog/mpd/category/knowledge-management/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jrothman.com/blog/mpd</link>
	<description>Management, especially good management, is hard to do. This blog is for people who want to think about how they manage people, projects, and risk.</description>
	<lastBuildDate>Thu, 24 May 2012 13:28:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Competition and Knowledge-Sharing</title>
		<link>http://www.jrothman.com/blog/mpd/2008/08/competition-and-knowledge-sharing.html</link>
		<comments>http://www.jrothman.com/blog/mpd/2008/08/competition-and-knowledge-sharing.html#comments</comments>
		<pubDate>Wed, 27 Aug 2008 19:17:30 +0000</pubDate>
		<dc:creator>Johanna</dc:creator>
				<category><![CDATA[assessment]]></category>
		<category><![CDATA[knowledge management]]></category>
		<category><![CDATA[pay]]></category>
		<category><![CDATA[feedback]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[transparency]]></category>

		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8484</guid>
		<description><![CDATA[In Knowledge Management Needs to be Agile, Too, I said If you put people in competition with each other *in any way*, they will have dis-incentives to share their knowledge. John, in his comment on that post, said it seemed &#8230; <a href="http://www.jrothman.com/blog/mpd/2008/08/competition-and-knowledge-sharing.html">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>In <a href="../2008/07/knowledge-management-needs-to-be-agile-too.html">Knowledge Management Needs to be Agile, Too</a>, I said</p>
<blockquote><p>If you put people in competition with each other *in any way*, they will have dis-incentives to share their knowledge.</p></blockquote>
<p>John, in his comment on that post, said it seemed intuitive, but was having trouble articulating why. I&#8217;m here to help :-) Some of my reasons, which all go to how people are evaluated and compensated.</p>
<p>Managers evaluate and compensate people for their knowledge, rather than the results they provide. Sure, a company might say &#8220;We want you to work together and share your knowledge.&#8221; But as soon as they pay people for their <strong>knowledge</strong>, not their <strong>results</strong>, everyone is in competition with each other.</p>
<p>And, if an organization pays people individually (even though all the work we do in organizations is via some sort of team), knowledge sharing goes right out the window. If you and I are in competition for raises (and paying people individually after evaluating them means that we are in competition), why should I share what I know with you? That sharing can only hurt me.</p>
<p>The only way I know to enable knowledge sharing across an organization is to:</p>
<ul>
<li>Pay for results</li>
<li>Pay people &#8220;enough&#8221;so it doesn&#8217;t hurt them financially to cooperate with each other</li>
<li>Use open-book management so people know who&#8217;s making what.</li>
</ul>
<p>Sure, some people will share their knowledge because it enables the organization to do better, but those of us who know the company doesn&#8217;t love us are going to be much less altruistic. As soon as our sharing hurts us, we stop.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jrothman.com/blog/mpd/2008/08/competition-and-knowledge-sharing.html/feed</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Knowledge Management Needs to be Agile, Too</title>
		<link>http://www.jrothman.com/blog/mpd/2008/07/knowledge-management-needs-to-be-agile-too.html</link>
		<comments>http://www.jrothman.com/blog/mpd/2008/07/knowledge-management-needs-to-be-agile-too.html#comments</comments>
		<pubDate>Wed, 23 Jul 2008 20:44:16 +0000</pubDate>
		<dc:creator>Johanna</dc:creator>
				<category><![CDATA[knowledge management]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[timebox]]></category>

		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8467</guid>
		<description><![CDATA[I was speaking with a potential client about their approach to knowledge management. They think they need a senior person to organize a top-down appoach, and build a custom tool, so they know what knowledge they want to manage and &#8230; <a href="http://www.jrothman.com/blog/mpd/2008/07/knowledge-management-needs-to-be-agile-too.html">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I was speaking with a potential client about their approach to knowledge management. They think they need a senior person to organize a top-down appoach, and build a custom tool, so they know what knowledge they want to manage and have a place to put it.</p>
<p>I don&#8217;t think that&#8217;s going to work. That approach requires they know what kinds of knowledge they need to store and who will need access to it, and when. They don&#8217;t know any of that now.</p>
<p>Here&#8217;s what I know about knowledge management:</p>
<ul>
<li>You can&#8217;t create an electronic system until you understand what you&#8217;re trying to manage. That&#8217;s because the kind of information changes over time, not just the content.</li>
<li>The Dreyfus model of knowledge acquisition infers that electronic systems are fine for novices, advanced beginners, and maybe the competents. But the people who really make a difference in the organization are the proficient and expert folks. Those people cannot easily put their knowledge into an electronic system, nor can the other people acquire their knowledge that way. Knowledge has to be transferred one-on-one, within a team, inside groups, between groups, and company-wide as the very last step.</li>
<li>If you put people in competition with each other *in any way*, they will have dis-incentives to share their knowledge.</li>
</ul>
<p>Given all of that, it&#8217;s not clear to me a top-down approach to knowledge management can work at all. What I do see as necessary is to have the managers (or some person):</p>
<ul>
<li>See the pockets of knowledge</li>
<li>Plan some adaptive, people-based, timeboxed systems of knowledge management</li>
<li>Measure where the knowledge management systems are headed</li>
<li>And steer the people to do better</li>
</ul>
<p>To me, agile approaches would work well. You could try something for a short timebox and see if it&#8217;s working. If so, keep doing it until it doesn&#8217;t work or needs another storage mechanism. Now you&#8217;ve got some experience to know what you need.</p>
<p>Starting with a tool is backwards, if you really want the experts who have substantial intuition to impart their knowledge.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jrothman.com/blog/mpd/2008/07/knowledge-management-needs-to-be-agile-too.html/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

