<?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: Not Invented Here</title>
	<atom:link href="http://qualityandinnovation.com/2009/06/19/not-invented-here/feed/" rel="self" type="application/rss+xml" />
	<link>http://qualityandinnovation.com/2009/06/19/not-invented-here/</link>
	<description>exploring quality, productivity &#38; innovation in socio-technical systems</description>
	<lastBuildDate>Mon, 06 Feb 2012 16:38:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Greg Zimmerman</title>
		<link>http://qualityandinnovation.com/2009/06/19/not-invented-here/#comment-283</link>
		<dc:creator><![CDATA[Greg Zimmerman]]></dc:creator>
		<pubDate>Thu, 25 Jun 2009 13:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://qualityandinnovation.com/?p=726#comment-283</guid>
		<description><![CDATA[The gap between what is occurring within an organization and the awareness or recognition of that activity or result is a common organizational issue, one that only gets bigger as organization size increases.  A friend who works for a major multi-national spent the better part of 2 years building &amp; managing a search tool that, in addition to finding existing applicable research outside the company, helped scientists within the company find relevant (or even duplicate) research from teams elsewhere in the organization that could help them shorten the product development cycle, solve problems, or innovate new products.

I think this is where some type of social network or knowledge mining tool can come in handy.  For example, Google requires their staff to maintain a profile of projects &amp; ideas they&#039;ve worked on or are currently investigating.  When an individual decides to take on a new project, their first step is to search the internal profile space for similar work, then begin collaborating with the folks who can contribute something of value to the effort.

It boils down to personal responsibility.  If it&#039;s important to you or your organization, stand up and ask the question:  Have we already started looking into this and who should we talk with to learn more?]]></description>
		<content:encoded><![CDATA[<p>The gap between what is occurring within an organization and the awareness or recognition of that activity or result is a common organizational issue, one that only gets bigger as organization size increases.  A friend who works for a major multi-national spent the better part of 2 years building &amp; managing a search tool that, in addition to finding existing applicable research outside the company, helped scientists within the company find relevant (or even duplicate) research from teams elsewhere in the organization that could help them shorten the product development cycle, solve problems, or innovate new products.</p>
<p>I think this is where some type of social network or knowledge mining tool can come in handy.  For example, Google requires their staff to maintain a profile of projects &amp; ideas they&#8217;ve worked on or are currently investigating.  When an individual decides to take on a new project, their first step is to search the internal profile space for similar work, then begin collaborating with the folks who can contribute something of value to the effort.</p>
<p>It boils down to personal responsibility.  If it&#8217;s important to you or your organization, stand up and ask the question:  Have we already started looking into this and who should we talk with to learn more?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curious Cat Management Improvement Blog &#187; Management Improvement Carnival #67</title>
		<link>http://qualityandinnovation.com/2009/06/19/not-invented-here/#comment-274</link>
		<dc:creator><![CDATA[Curious Cat Management Improvement Blog &#187; Management Improvement Carnival #67]]></dc:creator>
		<pubDate>Sun, 21 Jun 2009 18:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://qualityandinnovation.com/?p=726#comment-274</guid>
		<description><![CDATA[[...] Not Invented Here by Nicole Radziwill - &#8220;when a NIH culture is observed, perhaps the resources and opportunities that are available to a group or an organization that could use them are truly invisible.&#8221; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Not Invented Here by Nicole Radziwill &#8211; &#8220;when a NIH culture is observed, perhaps the resources and opportunities that are available to a group or an organization that could use them are truly invisible.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicole Radziwill</title>
		<link>http://qualityandinnovation.com/2009/06/19/not-invented-here/#comment-273</link>
		<dc:creator><![CDATA[Nicole Radziwill]]></dc:creator>
		<pubDate>Fri, 19 Jun 2009 14:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://qualityandinnovation.com/?p=726#comment-273</guid>
		<description><![CDATA[Hi John - I agree with you... the software developers who are the most competent *do not* have this issue, and are singularly focused on high quality results. Unless there is reinforcement within a team (managers + developers), continually encouraging one another to be aware of outside opportunities, there can be a risk of slipping into NIH mentality as a group. The key to me is... you have to pay attention to this process, and be committed to continuous learning (like you note).]]></description>
		<content:encoded><![CDATA[<p>Hi John &#8211; I agree with you&#8230; the software developers who are the most competent *do not* have this issue, and are singularly focused on high quality results. Unless there is reinforcement within a team (managers + developers), continually encouraging one another to be aware of outside opportunities, there can be a risk of slipping into NIH mentality as a group. The key to me is&#8230; you have to pay attention to this process, and be committed to continuous learning (like you note).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hunter</title>
		<link>http://qualityandinnovation.com/2009/06/19/not-invented-here/#comment-272</link>
		<dc:creator><![CDATA[John Hunter]]></dc:creator>
		<pubDate>Fri, 19 Jun 2009 13:15:41 +0000</pubDate>
		<guid isPermaLink="false">http://qualityandinnovation.com/?p=726#comment-272</guid>
		<description><![CDATA[I actual find software developers the least likely to fall into this problem.  They (in my experience) understand the benefit of learning.  And in learning you take from the successes of others to allow faster success.  There is no desire to not use calculus since it is outside knowledge.  I find it hard to understand how a software developer can be any good at their job if they are not constantly learning and taking from ideas not invented by them.  It is also required for managers but I see so many managers act that way that I can see how they can survive (the competition is not that great).

The focus on results (and critical analysis of why results are not better) is one thing I love about working with good software developers.]]></description>
		<content:encoded><![CDATA[<p>I actual find software developers the least likely to fall into this problem.  They (in my experience) understand the benefit of learning.  And in learning you take from the successes of others to allow faster success.  There is no desire to not use calculus since it is outside knowledge.  I find it hard to understand how a software developer can be any good at their job if they are not constantly learning and taking from ideas not invented by them.  It is also required for managers but I see so many managers act that way that I can see how they can survive (the competition is not that great).</p>
<p>The focus on results (and critical analysis of why results are not better) is one thing I love about working with good software developers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

