<?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: There’s more to Open Innovation than Open Source</title>
	<atom:link href="http://dw2blog.com/2008/08/13/there%e2%80%99s-more-to-open-innovation-than-open-source/feed/" rel="self" type="application/rss+xml" />
	<link>http://dw2blog.com/2008/08/13/there%e2%80%99s-more-to-open-innovation-than-open-source/</link>
	<description>Eclectic thoughts on technologies, markets, innovation, openness, collaboration, disruption, risks, and solutions</description>
	<lastBuildDate>Mon, 06 Feb 2012 09:17:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Joel West</title>
		<link>http://dw2blog.com/2008/08/13/there%e2%80%99s-more-to-open-innovation-than-open-source/#comment-62</link>
		<dc:creator><![CDATA[Joel West]]></dc:creator>
		<pubDate>Thu, 21 Aug 2008 19:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://dw2blog.com/2008/08/13/there%e2%80%99s-more-to-open-innovation-than-open-source/#comment-62</guid>
		<description><![CDATA[&lt;i&gt;(What’s more, “Open Innovation” and “Open Source” share the prefix “Open”!)&lt;/i&gt;&lt;br/&gt;&lt;br/&gt;I couldn’t agree more. &lt;a HREF=&quot;http://www.openinnovation.net/Book/NewParadigm/Chapters/05.pdf&quot; REL=&quot;nofollow&quot;&gt;There is an overlap&lt;/a&gt; but they are not the same — orthogonal concepts or at best correlated (See Fig 5.1).&lt;br/&gt;&lt;br/&gt;Firms that want to make money off of open source need a revenue model — a point that Chesbrough makes and that so many companies either ignore or underestimate. Will a big company cross-subsidize an open source effort indefinitely? Sun pulled out of Mozilla pretty quickly, and while IBM is a major player in Linux and Apache they‘re not carrying the whole load.&lt;br/&gt;&lt;br/&gt;I think open source has succeeded wildly as a way to commoditize software or to let (very smart) users share their solutions. As a business model, the jury is still out.]]></description>
		<content:encoded><![CDATA[<p><i>(What’s more, “Open Innovation” and “Open Source” share the prefix “Open”!)</i></p>
<p>I couldn’t agree more. <a HREF="http://www.openinnovation.net/Book/NewParadigm/Chapters/05.pdf" REL="nofollow">There is an overlap</a> but they are not the same — orthogonal concepts or at best correlated (See Fig 5.1).</p>
<p>Firms that want to make money off of open source need a revenue model — a point that Chesbrough makes and that so many companies either ignore or underestimate. Will a big company cross-subsidize an open source effort indefinitely? Sun pulled out of Mozilla pretty quickly, and while IBM is a major player in Linux and Apache they‘re not carrying the whole load.</p>
<p>I think open source has succeeded wildly as a way to commoditize software or to let (very smart) users share their solutions. As a business model, the jury is still out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Wood</title>
		<link>http://dw2blog.com/2008/08/13/there%e2%80%99s-more-to-open-innovation-than-open-source/#comment-55</link>
		<dc:creator><![CDATA[David Wood]]></dc:creator>
		<pubDate>Thu, 14 Aug 2008 12:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://dw2blog.com/2008/08/13/there%e2%80%99s-more-to-open-innovation-than-open-source/#comment-55</guid>
		<description><![CDATA[Harry,&lt;br/&gt;&lt;br/&gt;Many thanks for your insightful comments.  I particularly agree with the following:&lt;br/&gt;&lt;br/&gt;&lt;i&gt;&gt;Symbian’s experience in the broad field of eco-system management is a given. That said the community stewardship challenges are complex and the situation (with any community) always in flux; what worked yesterday, therefore, may not work as well today.&lt;br/&gt; &lt;br/&gt;Getting this right is going to be of mission critical importance for many software companies. A new breed of leaders is going to emerge with a skill-set focused on the stewardship of external resource communities, with much of the deep expertise needed to handle the more complex issues passing into the hands of the specialists.&lt;/i&gt;&lt;br/&gt;&lt;br/&gt;I look forward to further exploring the essence of this emerging new skill-set.&lt;br/&gt;&lt;br/&gt;// dw2-0]]></description>
		<content:encoded><![CDATA[<p>Harry,</p>
<p>Many thanks for your insightful comments.  I particularly agree with the following:</p>
<p><i>&gt;Symbian’s experience in the broad field of eco-system management is a given. That said the community stewardship challenges are complex and the situation (with any community) always in flux; what worked yesterday, therefore, may not work as well today.</p>
<p>Getting this right is going to be of mission critical importance for many software companies. A new breed of leaders is going to emerge with a skill-set focused on the stewardship of external resource communities, with much of the deep expertise needed to handle the more complex issues passing into the hands of the specialists.</i></p>
<p>I look forward to further exploring the essence of this emerging new skill-set.</p>
<p>// dw2-0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry Wilson</title>
		<link>http://dw2blog.com/2008/08/13/there%e2%80%99s-more-to-open-innovation-than-open-source/#comment-54</link>
		<dc:creator><![CDATA[Harry Wilson]]></dc:creator>
		<pubDate>Thu, 14 Aug 2008 09:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://dw2blog.com/2008/08/13/there%e2%80%99s-more-to-open-innovation-than-open-source/#comment-54</guid>
		<description><![CDATA[Beyond Open Innovation…&lt;br/&gt;&lt;br/&gt;There’s more to open innovation than open source.  I would agree.  I see open source broadly as a means to an end, not an end in itself (for Symbian and others).    Moving to open source does reduce the entry barriers and should lead to more users and external developers experimenting with the system, as you say.  Having more people experimenting with the system helps, but this is not sufficient in itself to qualify as an end objective of course.  Nor do I believe in fact, that it is sufficient to target to successfully stimulate “Open Innovation”, difficult as that is to realise in practical terms as you point out.&lt;br/&gt;&lt;br/&gt;I think to get the roadmap right you have to look to the likely shape and form of successful software companies in the future, and here I envisage a blurring of the lines of distinction between internal and external resources with both factions empowered to influence the direction of the new “corporate organism” – I make no apologies for the use of the biological term as I think this best captures the likely scale of the leadership and change management challenges which confront us going forward.&lt;br/&gt;&lt;br/&gt;If we use this simple “corporate organism model” as a lamp to illuminate the darkness, several things become evident (building on Henry Chesbrough’s open innovation mindset thinking):&lt;br/&gt;&lt;br/&gt;• Most of the really smart people don’t work for us.&lt;br/&gt;• Companies that leverage the external as well as the internal might survive.  Companies which do not adequately leverage the external will not survive.&lt;br/&gt;• Companies that are “best in class” at leveraging the external will win.&lt;br/&gt;&lt;br/&gt;That there are issues with both the incorporation of external innovations and with motivating the external contributors I would also agree.  With regard to the latter point I have observed that even the issue of responding to external innovations proves challenging for some in the open-source space!  &lt;br/&gt;&lt;br/&gt;Part of the problem lies with the very concept of “product”.  Go back to the time of the Austin 10, and it was black, no other colours were offered (so I’m told, before my time I’m afraid!).    With a product (read one size fits all) mentality one tends to push back on user/external innovations, preferring instead to lean purely on internal thought leaders for direction on product specification etc.  Coming from a services background myself, I’m more inclined to think in terms of solutions; the customer gets what he requires to meet a business need.&lt;br/&gt;&lt;br/&gt;Moving to the point of encouraging external innovation, and then putting in place the infrastructure to enable that innovation, will require a quantum leap in thinking for some organisations, and I suspect for many the chasm will be just too wide.&lt;br/&gt;&lt;br/&gt;To get it right you certainly need the mix of education and evangelism, the active listening, the platform flexibility and the rewards systems which you have mentioned.&lt;br/&gt;&lt;br/&gt;I would formalise this by saying that:&lt;br/&gt;• You need to create an “environment” for external/internal collaboration, in the broadest sense of the word.  There are many facets to this.&lt;br/&gt;• You need strategies to motivate a stream of people to get involved with your evolving corporate organism in the first place.  Clearly it is not enough to simply nurture new developers; you need to create a strong “pull” to attract star players away from the competition.&lt;br/&gt;• You need strategies to motivate people to innovate around the issues on a day to day basis i.e. to actively engage once involved.&lt;br/&gt;• You need to provide elements of vision/leadership (direction) and operational management befitting the culture of your external community.  This is important. Taking “open” to the point of abdicating responsibility for providing “direction” (as some appear to) is unlikely to produce optimal results.&lt;br/&gt;• You need to provide a clear reward infrastructure (whatever the mix) which works reliably and in a timely manner.&lt;br/&gt;Symbian’s experience in the broad field of eco-system management is a given.  That said the community stewardship challenges are complex and the situation (with any community) always in flux; what worked yesterday, therefore, may not work as well today. &lt;br/&gt;Getting this right is going to be of mission critical importance for many software companies.  A new breed of leaders is going to emerge with a skill-set focused on the stewardship of external resource communities, with much of the deep expertise needed to handle the more complex issues passing into the hands of the specialists. &lt;br/&gt;In the meantime developers looking for a good return on their investment would be well advised to keep a close eye on the Symbian Foundation’s activities over the coming months, I suspect.  &lt;br/&gt;&lt;br/&gt;Harry Wilson&lt;br/&gt;Managing Partner&lt;br/&gt;Greenflash Consulting&lt;br/&gt;greenflash@in2euro.com&lt;br/&gt;14th August 2008]]></description>
		<content:encoded><![CDATA[<p>Beyond Open Innovation…</p>
<p>There’s more to open innovation than open source.  I would agree.  I see open source broadly as a means to an end, not an end in itself (for Symbian and others).    Moving to open source does reduce the entry barriers and should lead to more users and external developers experimenting with the system, as you say.  Having more people experimenting with the system helps, but this is not sufficient in itself to qualify as an end objective of course.  Nor do I believe in fact, that it is sufficient to target to successfully stimulate “Open Innovation”, difficult as that is to realise in practical terms as you point out.</p>
<p>I think to get the roadmap right you have to look to the likely shape and form of successful software companies in the future, and here I envisage a blurring of the lines of distinction between internal and external resources with both factions empowered to influence the direction of the new “corporate organism” – I make no apologies for the use of the biological term as I think this best captures the likely scale of the leadership and change management challenges which confront us going forward.</p>
<p>If we use this simple “corporate organism model” as a lamp to illuminate the darkness, several things become evident (building on Henry Chesbrough’s open innovation mindset thinking):</p>
<p>• Most of the really smart people don’t work for us.<br />• Companies that leverage the external as well as the internal might survive.  Companies which do not adequately leverage the external will not survive.<br />• Companies that are “best in class” at leveraging the external will win.</p>
<p>That there are issues with both the incorporation of external innovations and with motivating the external contributors I would also agree.  With regard to the latter point I have observed that even the issue of responding to external innovations proves challenging for some in the open-source space!  </p>
<p>Part of the problem lies with the very concept of “product”.  Go back to the time of the Austin 10, and it was black, no other colours were offered (so I’m told, before my time I’m afraid!).    With a product (read one size fits all) mentality one tends to push back on user/external innovations, preferring instead to lean purely on internal thought leaders for direction on product specification etc.  Coming from a services background myself, I’m more inclined to think in terms of solutions; the customer gets what he requires to meet a business need.</p>
<p>Moving to the point of encouraging external innovation, and then putting in place the infrastructure to enable that innovation, will require a quantum leap in thinking for some organisations, and I suspect for many the chasm will be just too wide.</p>
<p>To get it right you certainly need the mix of education and evangelism, the active listening, the platform flexibility and the rewards systems which you have mentioned.</p>
<p>I would formalise this by saying that:<br />• You need to create an “environment” for external/internal collaboration, in the broadest sense of the word.  There are many facets to this.<br />• You need strategies to motivate a stream of people to get involved with your evolving corporate organism in the first place.  Clearly it is not enough to simply nurture new developers; you need to create a strong “pull” to attract star players away from the competition.<br />• You need strategies to motivate people to innovate around the issues on a day to day basis i.e. to actively engage once involved.<br />• You need to provide elements of vision/leadership (direction) and operational management befitting the culture of your external community.  This is important. Taking “open” to the point of abdicating responsibility for providing “direction” (as some appear to) is unlikely to produce optimal results.<br />• You need to provide a clear reward infrastructure (whatever the mix) which works reliably and in a timely manner.<br />Symbian’s experience in the broad field of eco-system management is a given.  That said the community stewardship challenges are complex and the situation (with any community) always in flux; what worked yesterday, therefore, may not work as well today. <br />Getting this right is going to be of mission critical importance for many software companies.  A new breed of leaders is going to emerge with a skill-set focused on the stewardship of external resource communities, with much of the deep expertise needed to handle the more complex issues passing into the hands of the specialists. <br />In the meantime developers looking for a good return on their investment would be well advised to keep a close eye on the Symbian Foundation’s activities over the coming months, I suspect.  </p>
<p>Harry Wilson<br />Managing Partner<br />Greenflash Consulting<br /><a href="mailto:greenflash@in2euro.com">greenflash@in2euro.com</a><br />14th August 2008</p>
]]></content:encoded>
	</item>
</channel>
</rss>

