<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Assembla Blog: Category Innovation</title>
    <link>http://andy.blogs.assembla.com/articles/category/innovation</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Wetware - Men among the Machines, by Andy Singleton</description>
    <item>
      <title>Build an online game in 7 days?</title>
      <description>&lt;p&gt;&lt;a href="http://www.gamasutra.com/features/20051026/gabler_pfv.htm"&gt;This article on Gamasutra&lt;/a&gt; provides a variety of &amp;#8220;juicy&amp;#8221; hints and examples from &amp;#8220;4 Grad Students Who Made Over 50 Games in 1 Semester.&amp;#8221;|&lt;/p&gt;


	&lt;p&gt;My last article on Hyper-agile product development focused on managing a complex project for minimum time to market &amp;#8211; a sort of top-down approach for managers and teams.  This article is a great follow-on for the individuals involved, a bottom-up approach to prototyping and testing individual features.&lt;/p&gt;</description>
      <pubDate>Sat, 27 Jan 2007 11:34:29 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:1a1f35ac90ab976ebd0d6e6563a1413f</guid>
      <author>andy@assembla.com</author>
      <link>http://andy.blogs.assembla.com/articles/2007/01/27/build-an-online-game-in-7-days</link>
      <category>Agile Development</category>
      <category>Innovation</category>
      <trackback:ping>http://andy.blogs.assembla.com/articles/trackback/36</trackback:ping>
    </item>
    <item>
      <title>Jon Udell Podcast: - A conversation with Andy Singleton about building global teams</title>
      <description>&lt;p&gt;&lt;a href="http://weblog.infoworld.com/udell/"&gt;Jon Udell&lt;/a&gt; included me in his Friday podcast series this week with &lt;a href="http://weblog.infoworld.com/udell/2006/05/19.html"&gt;a conversation with Andy Singleton about building global teams&lt;/a&gt; . Jon has been putting up with me since 1993, when he edited some freelance articles that I wrote for Byte magazine.  In 2003 he coined the term &amp;#8220;dynamic development&amp;#8221; to describe the work I was doing.  He has recently been commenting on user innovation and the power of human networks to do work beyond open source sofware.  In this conversation, he turns me on to Yochai Benkler&amp;#8217;s &lt;a href="http://www.benkler.org/wealth_of_networks/index.php?title=Main_Page"&gt;The Wealth of Networks&lt;/a&gt;, and he cautions against a &amp;#8220;walled garden&amp;#8221;.  Maybe we&amp;#8217;ll be able to work together on a universally portable user profile.&lt;/p&gt;</description>
      <pubDate>Sat, 20 May 2006 22:53:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:8e9c6a35f9c18220b813a3c8678e5f1b</guid>
      <author>andy@assembla.com</author>
      <link>http://andy.blogs.assembla.com/articles/2006/05/20/jon-udell-podcast-a-conversation-with-andy-singleton-about-building-global-teams</link>
      <category>Agile Development</category>
      <category>Open Source</category>
      <category>Breakout Development</category>
      <category>Innovation</category>
      <trackback:ping>http://andy.blogs.assembla.com/articles/trackback/24</trackback:ping>
    </item>
    <item>
      <title>Ancient Greek Craftsmanship for Software Teams</title>
      <description>&lt;p&gt;I have been reading a book called &lt;i&gt;&lt;b&gt;The Greek Commonwealth&lt;/b&gt; &#226;&#8364;&#8220; Politics and Economics in Fifth Century Athens&lt;/i&gt;.  Originally published in 1911, it&#226;&#8364;&#8482;s not out of date.  According to the author, &#226;&#8364;&#339;it is natural for human beings to enjoy using their own best faculties.  Men never felt that enjoyment so keenly, or put so much high effort into its attainment, as in the workshops of ancient Greece.  If you seek a proof, go look through the shelves of our Greek museums.  There is hardly an object that they made, however rude, but bears on it, sometimes faintly, sometimes with speaking clearness, the touch of the spirit of Art.&#226;&#8364;?  How can we bring that spirit to our work, every day?&lt;/p&gt;&lt;p&gt;This author (Alfred Zimmerman) also writes:
&#226;&#8364;&#339;Our modern industrial system, with an ingenuity so wicked that one might believe it to be deliberate, has contrived to take the joy out of craftsmanship, and so to choke up the very springs of art.  It has replaced, wherever possible, the delicate skill of the human hand by inhuman machinery, and the independent thought of the human brain by soulless organization.  It has removed the maker or producer from all association with the public for whom he works, and substituted a deadening cash-nexus for the old personal relationship or sense of effort in a corporate cause.  Above all, it has taken from him his liberty, and forced him to work for a master who is no artist.&#226;&#8364;?&lt;/p&gt;


	&lt;p&gt;Alfred Zimmerman, a long-dead Oxford don, could lead a workshop on how to build modern, high-performing software teams and startups.  Here are some of his observations about the craftsmen of ancient Greece:&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;When the Greek city states hired craftsmen, the foreman and the well-know artists received the same rate of pay as all of the other men on the crew, including the slaves.  This rate was set for a long time at one drachma per day.  There were no social barriers at work.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;ul&gt;
	&lt;li&gt;The most talented competed not for money, but for honors, which in Athens included a golden crown.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;ul&gt;
	&lt;li&gt;Competing craftsman clustered together, sharing their clientele, their stories, and their knowledge.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;ul&gt;
	&lt;li&gt;They had enough leisure time for stories, and aspired also to be citizens and soldiers.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;ul&gt;
	&lt;li&gt;Greek workshops tended to be small &#226;&#8364;&#8220; a craftsman and several apprentices &#226;&#8364;&#8220; and they were never bigger than 20 people.  The master was always an artist, not a manager.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;p&gt;Like many before me, I believe that the pre-Christian philosophy of the ancient Greeks gives us vision of what a man can achieve on Earth, as a citizen and father.  I draw inspiration from Odyssyus, the ultimate survivor.  I am often amused by the goofy anecdotes of Herodotus.  Sometimes I read the endless political debates of the democrats, demogogues, and tyrants, learning how great nations can be hijacked by small-minded men, and how the small-minded can eventually be cast off.  That sounds relevant to my reading of the daily news.&lt;/p&gt;


What American cannot be inspired by the story of the war against Persia?  The Greek citizens came out of their stone huts and small towns, and stood against the army of the greatest and wealthiest imperial power on the face of the earth.  There was the last stand of the 300 Spartans, the desperate evacuation of Athens, the high-stakes maneuvering at Salamis.  Then came victory, the Parthenon, and science as we know it.  2000 years later the minutemen had this very story on their minds as redcoats marched into Concord.&lt;br/&gt;  Emerson gives us the scene:&lt;br/&gt;
&lt;blockquote&gt;
By the rude bridge that arched the flood,&lt;br/&gt;
Their flag to April&amp;#8217;s breeze unfurled,&lt;br/&gt; 
Here once the embattled farmers stood,&lt;br/&gt; 
And fired the shot heard round the world.
&lt;/blockquote&gt;</description>
      <pubDate>Sat, 20 May 2006 21:16:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:c778c5961a0750dd5551701f04e9e3d3</guid>
      <author>andy@assembla.com</author>
      <link>http://andy.blogs.assembla.com/articles/2006/05/20/ancient-greek-craftsmanship-for-software-teams</link>
      <category>Agile Development</category>
      <category>Innovation</category>
      <trackback:ping>http://andy.blogs.assembla.com/articles/trackback/23</trackback:ping>
    </item>
    <item>
      <title>What a turnaround! Software is now a terrific business</title>
      <description>&lt;p&gt;Less than a year ago I wrote an article titled &#226;&#8364;&#339;&lt;a href="http://andy.blogs.assembla.com/articles/2005/05/19/is-the-enterprise-software-licensing-business-dying"&gt;Is the Enterprise Software Licensing Business Dying&lt;/a&gt;&#226;&#8364;?.  It was originally posted on &lt;span class="caps"&gt;IT &lt;/span&gt;Managers Journal, but it got picked up by Slashdot and various bloggers and podcasters.  It pointed out that enterprise buyers had stopped buying software licenses &#226;&#8364;&#8220; the mainstay of the software industry.  This caused years of misery for software professionals, years during which software was a bad business to be in.  But the light at the end of the tunnel was apparent even then, in the form of new packaging and revenue models.  Faster than I imagined, the prospects for the software industry have been transformed. We now have a wonderful alignment of good fundamentals &#226;&#8364;&#8220; increasing demand, declining costs, and rapid innovation.&lt;/p&gt;&lt;p&gt;Any industry with increasing demand, declining costs, and rapid innovation has got to be a great place to invest time and money.&lt;/p&gt;


	&lt;p&gt;&lt;b&gt;&lt;span class="caps"&gt;INCREASING DEMAND&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;


	&lt;p&gt;I recently did some research into market size for Assembla&#226;&#8364;&#8482;s business plan, and what I was interested in was &#226;&#8364;&#339;on-demand software&#226;&#8364;? or &#226;&#8364;&#339;software as a service&#226;&#8364;? &amp;#8211; traditional enterprise applications packaged as subscription online service.  Almost every company that I looked at was growing at more that 50% per year.  This accounted for more than $3B in revenue.  So while the overall enterprise software market may be flat, there are big categories inside it where business is better than ever &#226;&#8364;&#8220; better than in the 90&#226;&#8364;&#8482;s boom.  Revenue is actually growing faster, from a bigger base.  That&#226;&#8364;&#8482;s the macro view.  The micro view is that globalization has doubled the pool of available programmers in five years, and we&#226;&#8364;&#8482;re already running out of them.&lt;/p&gt;


	&lt;p&gt;&lt;b&gt;&lt;span class="caps"&gt;DECLINING COSTS&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;


	&lt;p&gt;At a presentation about social software at Harvard Business School, one of the questions the presenter asked was &#226;&#8364;&#339;why now?&#226;&#8364;?  Why are we seeing big, free social wikis, networking sites, blogging sites, classified markets, spaces?  Why now and not 5 years ago?  His answer was: because the basic costs are a lot lower now.  The servers, server software, and network bandwidth are cheap enough to give away.  That&#226;&#8364;&#8482;s why people can support bigger communities.  That&#226;&#8364;&#8482;s why businesses give away free online services instead of hiring salespeople.  It&#226;&#8364;&#8482;s cheaper.&lt;/p&gt;


	&lt;p&gt;The cost of making the applications to run on this platform has declined even more.  I estimate that my cost of building and launching an application is about 25% of what it was six years ago.  Labor is much less expensive because we now shop globally.  The &lt;a href="http://andy.blogs.assembla.com/articles/2006/02/13/the-rise-of-dynamic-languages-programmer-productivity"&gt;productivity of that labor rises continuously&lt;/a&gt; as we adopt better tools and processes.  We have more open source components to draw on, which has a big impact because studies show that &lt;a href="http://andy.blogs.assembla.com/articles/2005/07/25/reuse-reuse-reuse"&gt;code re-use&lt;/a&gt; is the single biggest contributor to increasing developer productivity.&lt;/p&gt;


	&lt;p&gt;Inside established software companies, lower costs mean higher margins.  The margins rise faster if companies take a pro-active approach to moving customers to lower cost software as a service platforms &#226;&#8364;&#8220; or as a friend of mine dubs it, &#226;&#8364;&#339;lift, shift, and maximize&#226;&#8364;?.   Software investors have some challenges and some opportunities.  One opportunity is to look at software as a cash producing business, doing &lt;span class="caps"&gt;LBO&lt;/span&gt;&#226;&#8364;&#8482;s, giving up on growth, and paying down debt and dividends with the cash not spent on new sales, marketing, and launch activities.  A new generation of entrepreneurs is figuring that out.  A challenge for software VC&#226;&#8364;&#8482;s is to figure out how to participate in a market with shrinking deal sizes.  In theory, that means they can do more deals, and give another bump to innovation.&lt;/p&gt;


	&lt;p&gt;&lt;b&gt;&lt;span class="caps"&gt;RAPID INNOVATION&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;


	&lt;p&gt;We&#226;&#8364;&#8482;re in the middle of a rapid burst of innovation that I call Wetware.  Wetware is open source, globalization, Web 2.0, and user-generated-content.  It&#226;&#8364;&#8482;s the smart node in the stupid network.  It&#226;&#8364;&#8482;s people working together.  Inevitably, they will accomplish great things.&lt;/p&gt;


	&lt;p&gt;Wetware is a relatively obscure burst of innovation because it is new.  We used to follow Hardware.  When computers first became big business, we measured innovation by the rate of new hardware introduction.  Software was an obscure component.  Then came software.  We created Moore&#226;&#8364;&#8482;s law for hardware, and software became a more interesting business.  We followed platform launches and browser wars and client server and software as a service.  We&#226;&#8364;&#8482;re still in that phase.  Here comes Wetware.  We can&#226;&#8364;&#8482;t measure units of human innovation, and we don&#226;&#8364;&#8482;t measure the speed of organizational reconfiguration.  But we should, and we will.  It&#226;&#8364;&#8482;s coming fast.&lt;/p&gt;


	&lt;p&gt;Max Planck said &#226;&#8364;&#339;science advances one funeral at a time,&#226;&#8364;? and so it is with this innovation.  Today&#226;&#8364;&#8482;s teenagers live their life in global networks, and spend a lot less time hanging out in parking lots than my contemporaries did.  They&#226;&#8364;&#8482;re going to take over the workforce, one retirement at a time.&lt;/p&gt;</description>
      <pubDate>Sat, 15 Apr 2006 13:22:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:4cc944de6c5ebf49e5da1ce873a02982</guid>
      <author>andy@assembla.com</author>
      <link>http://andy.blogs.assembla.com/articles/2006/04/15/what-a-turnaround-software-is-now-a-terrific-business</link>
      <category>Software Business</category>
      <category>Innovation</category>
    </item>
    <item>
      <title>Where&#8217;s the innovation?  Where should we place our bets?</title>
      <description>&lt;p&gt;Houston, we have a problem.  Innovation in aerospace stalled out and started losing altitude around 1970.  Instead of jet packs and vacations on Mars, we have foam falling off the 30-year old space shuttle.  Our life today isn&amp;#8217;t anything like the twenty-first century life we imagined in &amp;#8230;&lt;/p&gt;&lt;p&gt;Houston, we have a problem.  Innovation in aerospace stalled out and started losing altitude around 1970.  Instead of jet packs and vacations on Mars, we have foam falling off the 30-year old space shuttle.  Our life today isn&amp;#8217;t anything like the twenty-first century life we imagined in 1970, extrapolating from the previous 35 years (1935-1970) of rapid change.  It&amp;#8217;s clear that innovation has slowed in many areas of industrial technology that are important for our daily lives.&lt;/p&gt;
&lt;p&gt;This fact is going to be highlighted in a &lt;a href="http://www.newscientist.com/article.ns?id=dn7616" target="_blank"&gt;rumored article from Jonathan Huebner&lt;/a&gt;.  You have probably already heard about it.  Huebner counted major technological innovations, and found that the rate of innovation is declining, and the rate of innovation per person is rapidly declining.  By this count, the rate of per-capita innovation peaked in 1873, and has now declined to the level that it was at in 1600.&lt;/p&gt;
&lt;p&gt;Many do not agree.  Clearly, a lot of discovery, both scientific and technological, is going on in the world.  There have been a lot of rebuttals.&lt;/p&gt;
&lt;p&gt;I personally believe that innovation is a fractal process.  Each burst of innovation is likely to have an S curve of output (a bell curve of innovation rates, as noted by Huebner).  So, any given space of innovation is bounded and runs out of steam.  However, the bursts can be of any size, and start at unpredictable times.  We are certainly coming to the end of the industrial revolution, but we may soon start an evolution revolution.  Innovation has dropped off in aerospace, but it&amp;#8217;s increasing in biotechnology.  We need to keep changing our focus and placing our bets.&lt;/p&gt;
&lt;p&gt;Evidence that innovation accelerates and decelerates comes from the oldest record of innovation we have- biological evolution.  There was a huge burst of evolution / innovation at the time of the &amp;#8220;Cambrian explosion&amp;#8221; about 570 million years ago.  This then tapered off into a very different kind of incremental evolution.&lt;/p&gt;
&lt;p&gt;Whether you believe that the overall rate of innovation is decreasing, the fact that the rate of innovation does decrease and has decreased in many major industries has a practical applications for investors.  We&amp;#8217;re all investing in technology somehow &amp;#8211; through our day job, through our education, or for some of us, through substantial portfolios of financial assets.&lt;/p&gt;
&lt;p&gt;If you can figure out what industries will have increasing innovation, you can buy a diversified selection of participants, watch them grow and consolidate, and make a tremendous profit from the winners.  If you catch one of the really big, Kondratieff-style, 50-year waves like oil, electricity, or computing, you can surf that wave for a lifetime.&lt;/p&gt;
&lt;p&gt;What if we could figure out the difference between industries with increasing returns to innovation, and industries with decreasing returns to innovation?  What if there were some essential indicators that would show the direction &amp;#8211; increasing productivity driven by innovation, or decreasing productivity in spite of innovation? &lt;/p&gt;
&lt;p&gt;I think these indicators exist.&lt;/p&gt;
&lt;p&gt;Let&amp;#8217;s consider one obvious factor &amp;#8211; an increasing or decreasing size of the space of target solutions.  You might be working on a problem for which each successful solution reduces the number of possible new solutions.  This seems to be the case for drug discovery.  There are a limited number of &amp;#8220;targets&amp;#8221; in a human body, and each time you find one, you reduce the number left.  This leads to declining productivity of innovation.  &lt;/p&gt;
&lt;p&gt;On the other hand, you might be working on a problem for which a successful solution increases the number of possible solutions, or even the number of related problems, each with an increasing number of solutions.  This is true if, instead of improving the health or efficiency of an existing system, you are actually constructing new things that have new uses.  Each of those new uses opens up new opportunities for innovation.  You make a microprocessor chip to go in a calculator, and then someone puts it in a personal computer, a telephone, etc.  If you can use the personal computer to design new chips, you get another round of increasing returns.&lt;/p&gt;
&lt;p&gt;The size of the solution space controls the return on innovation, even if innovation is rapid.  I think of the impact of computing power on video games.  The early video games, such as pong and space invaders, were fun.  Modern video games have thousands of times more speed, memory, and resolution, and are only a little bit more fun. Computing capacity has diminishing returns if measured in terms of fun.  This observation goes a long way toward derailing Ray Kurzweil&amp;#8217;s hypothesis that, because computing power is rapidly increasing, we will all one day live in a computer-supported nirvana.  That particular technology, no matter how good, has limits of applicability for humans&lt;/p&gt;
&lt;p&gt;This is the problem with drug discovery.  It doesn&amp;#8217;t matter how much innovation gets thrown into the drug discover process.  Vast amounts of new technology and ingenuity are being brought to bear.  Yet, the drug discovery process gets less productive and more expensive every year.&lt;/p&gt;
&lt;p&gt;Looking at biotechnology, we need to separate the dynamics of the inputs from the dynamics of the outputs.  The input, biotechnology, is experiencing tremendous innovation, probably with increasing returns.  The output, drug discovery, is experiencing little innovation and decreasing returns.&lt;/p&gt;
&lt;p&gt;What about software?  I think we have reached a point of saturation for most of the kinds of software that I work on.  It&amp;#8217;s like video games.  Most of it is designed to improve the efficiency of humans and businesses, which gives it declining marginal returns.  On the other hand, there are sure to be new domains where software essentially interacts with software.  For instance, if we can make evolved software (genetic programming) we can apply that process to itself and get increasing returns.&lt;/p&gt;
&lt;p&gt;By this measure, drug discovery is a loser.  However, biotechnologies which actually construct new things, such as &lt;span class="caps"&gt;GMO&lt;/span&gt;&amp;#8217;s, or synthetic biology, are likely to have increasing returns.  I&amp;#8217;m placing my bets with synthetic biology.&lt;/p&gt;</description>
      <pubDate>Tue, 23 Aug 2005 14:09:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:a235d058bceedbac7e71529d3a94a53b</guid>
      <author>andy</author>
      <link>http://andy.blogs.assembla.com/articles/2005/08/23/where%E2%80%99s-the-innovation-where-should-we-place-our-bets</link>
      <category>Innovation</category>
    </item>
    <item>
      <title>Democratizing Innovation shows how to make big breakthroughs</title>
      <description>&lt;p&gt;User innovation, in the form of open source software, is one of the most powerful forces in the software business today.  Will this force propel the software industry to yet another phase of bold innovation?  Or, will it cripple commercial R&amp;#38;D organizations and lead to a future of stagnant, commoditized software?&lt;/p&gt;&lt;p&gt;In his book &lt;a href="http://web.mit.edu/evhippel/www/democ.htm" target="_blank"&gt;&lt;i&gt;Democratizing Innovation&lt;/i&gt; (available online)&lt;/a&gt;, Sloan School professor Eric Von Hippel shows user innovation at work in many industries, including sporting goods, surgical equipment, electronics manufacturing, and the 18th century mines of Cornwall.  His finding is that innovations from users are often more lasting and important than innovations from vendors.  Hippel finds that while vendors focus on incremental improvements to known capabilities, users are more likely to come up with new capabilities that have important future uses.&lt;/p&gt;


	&lt;p&gt;Hippel focuses on &amp;#8220;lead users&amp;#8221; &amp;#8211; users with extreme needs that have not yet been encountered by most other users.  A lead user might be a surgeon practicing a new technique, a systems administrator under persistent network attack, or a mountain biker exploring new terrain.  Lead users are motivated to figure out how to build new things with existing products.  And, this book demonstrates, they often have the ability to make substantial progress.  A weekend kiteboarder might be an aerospace engineer during the week.  A surgeon might be able to raise funding to manufacture new equipment.  An electronics manufacturer certainly has the means to make extensive customizations to the equipment it uses on its primary assembly line.&lt;/p&gt;


	&lt;p&gt;In contrast, vendors doing market research for a new product typically focus on their mainstream users.  They make improvements in the speed, size, convenience, availability, usability, and reliability of their products, as typically used.  Each iteration of the vendor product is produced largely by the same engineers building the same product for the same customers, but in an improved version.  That&amp;#8217;s the groove or rut that I see most software companies climbing into.&lt;/p&gt;


	&lt;p&gt;Vendors also segment their users into just a few categories, hoping to simplify their product planning and production by making a high-quality, one-size-fits-all product.  In doing so, they miss what Hippel calls &amp;#8220;heterogeneity of need&amp;#8221;.  Users of a product often have many different needs.  In one survey of Apache Web server administrators, Hippel found that there were 92 different security related functions requested, and that there was no clustering or pattern in their requests.  Some of those requests come from lead users, but they are hard to identify in the vendors aggregate view.&lt;/p&gt;


	&lt;p&gt;The most eye-popping statistics in this book come from a study of product development at 3M, where certain product development teams were coached to use a &amp;#8220;lead user&amp;#8221; method for identifying new product opportunities.  They looked at emerging market trends, and then they identified users that were at the leading edge of those trends (the lead users) and went to them for ideas.  A different set of product development teams used traditional market research and R&amp;#38;D to design their products.  At the end of this study, the traditional teams had generated 41 incremental improvements and 1 major new product line, with forecast annual sales of $18M per product.  The &amp;#8220;lead user&amp;#8221; teams had generated zero incremental improvements and five major new product lines, with forecast annual sales of $146M per product.&lt;/p&gt;


	&lt;p&gt;The software business has both the motivation and the ability to advance with user innovation.  Heterogeneity of need is so high for large enterprise systems that virtually every installation is customized.  User communities have leading-edge collaboration techniques, and communities have substantial programming resources that often include vendor capabilities.&lt;/p&gt;


	&lt;p&gt;Hippel gives us a handy formula for figuring out the build/buy decision.  Assuming that either the vendor and the user can build a product or innovation for the same cost, a vendor spending 50% of non-sales expenses on R&amp;#38;D, with a 25% cost of sales, will need to sell 3 copies of a system before making any money.  If the market is smaller, users will need to pick up the development task.  At a 75% cost of sales, the vendor needs to sell 9 copies.  This calculation, along with the variation in needs, starts to explain why, as the cost of selling a new software license has risen to over 75% of revenue, users have shifted resources from packaged systems to building custom systems with offshore and open source building blocks.  This shifts resources toward user innovation.&lt;/p&gt;


	&lt;p&gt;In this situation, software producers must learn to take advantage of user innovation.  They can provide toolkits to users (for example, source code), so that users can add more value through innovation.  They can share the work of innovation.  They can create processes for bringing user modifications back into the mainline product.  In short, they can be more like open source communities.&lt;/p&gt;


	&lt;p&gt;User innovation works well, but is it in the interests of users or vendors to participate in an innovation community?  Why reveal and contribute code if it just helps the free riders who don&amp;#8217;t contribute?  In the open source world, there may be tens of thousands of users for every contributor.  What explains the increasing volume of commercial open source contributions?  Hippel approaches this question by observing that the &amp;#8220;free revealing&amp;#8221; of important commercial innovation is widespread in many industries.  He cites examples ranging from 18th century mining engineers who started a journal to share advances in steam engine technology, to &lt;span class="caps"&gt;IBM&lt;/span&gt;, which &amp;#8220;after a lag&amp;#8221; recently revealed its important copper interconnect chipmaking technology to competitors.  In most of these cases, free revealing &amp;#8220;is the only practical option.&amp;#8221;  Competitors can reproduce an innovation if they observe it, and patent protection is weak in most fields.  Furthermore, individuals (consultants and developers) often have a strong incentive to freely reveal innovations that advance their careers or their personal missions.  Free revealing increases the pace of innovation and benefits the mission of the innovator.  By controlling the timing and placement of freely revealed innovations, commercial organizations can build up their platforms, their industries, their customer and partner participation, and other types of competitive advantage.&lt;/p&gt;


	&lt;p&gt;Hippel concludes by observing that user innovation and free revealing lead to enhanced &amp;#8220;social welfare&amp;#8221;.  It can make everyone better off.  User innovation is a powerful force that can benefit both users and vendors.  This book helps you understand how it works so that you can make it work for you.&lt;/p&gt;


	&lt;p&gt;&lt;em&gt;This article also appeared in &lt;strong&gt;&lt;span class="caps"&gt;IT &lt;/span&gt;Managers Journal&lt;/strong&gt;.&lt;/em&gt;&lt;/p&gt;</description>
      <pubDate>Tue, 05 Jul 2005 17:43:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:f9eca423589db10fda39af68dea196b7</guid>
      <author>andy@assembla.com</author>
      <link>http://andy.blogs.assembla.com/articles/2005/07/05/democratizing-innovation-shows-how-to-make-big-breakthroughs</link>
      <category>Open Source</category>
      <category>Software Business</category>
      <category>Innovation</category>
    </item>
  </channel>
</rss>
