Open Innovation

Reading Open Innovation – a thesis evolved by Henry Chesbrough in 2003. I have also the follow up book published in 2006 which is a collaboration with other researchers going through his earlier thesis.

I’m researching this as I’m interested in what current literature exists that explains Open Source and why / how it works which is not from the Open Source domain. Books that emanate from the Open Source domain tend to be religious in nature and it is also true that most attacks against Open Source take it from the religious angle… so having literature that endorses the model which is not open source evangelicalism is very useful.

Previous to this I found a lot of value in The Diffusion of Innovations (originally published in 1962) by Everett Rogers.

Open Innovation and the Diffusion of Innovations separately explain quite a bit about why Open Source works, and I think I’ll post more about this as it becomes clearer in my head.

Chesbroughs thesis can be summed up in one quote

The Open Innovation paradigm treats R&D as an open system. Open Innovation suggests that valuable ideas can come from inside or outside the company and can go to market from inside or outside the company

Essentially it is the admission that any one company doesn’t have all the smart teams/people/ideas. So how about re-imagining innovation and release it from a so-called ‘vertical innovation’ model, where all the R&D is done inhouse and where IP (Intellectual Property) is jealously guarded, to a open model where innovation essentially comes through collaboration with orgs and individuals outside the company.

From an Open Source point of view this is a ‘duh’ moment… Open Source has long expounded this approach. But…I have never found it well explained…

So it is good to find this argument made elsewhere and in clearer terms…but unfortunately the Chesborough thesis was published in 2003 when Open Source was still very young. Consequently Chesbrough reads Open Source as a idealistic and altruistic movement… he doesn’t really consider open source projects to have a business model and a business model is central to his thesis. Its a pity as Open Source has moved on since then and there are a lot of very successful and interesting examples of Open Source business models. But if you sorta squint while you are reading, and blur out the dated-ness then there is a lot of stuff that could just be quoted verbatim that makes a strong argument for Open Source as seen through the lens of the Open Innovation thesis.

Thats pretty interesting as, combined with the Diffusion of Innovations, these two bodies of work explain the value (and consequently provide a rationale which does not come from the open source sector directly) of open source. Open Innovation explains why open source is a good idea if you are a company whose business requires software to function in its core offerings, and the Diffusion of Innovation theory helps us understand why open source can beat closed source software in the arena of adoption.

The point is, if you can combine the two you have a winner – a model that enables rapid adoption and innovates faster than closed alternatives/competitors. If you can marry successful commercial activity to this you have something very powerful that can potentially wipe out the existing proprietary offerings – which is what we need in the publishing sector. The aim of what we are now doing in Coko, in this post-foundational stage, is to seed the commercial activity around the very healthy core of community technologies we have built.

Anyways… here are some quotes I liked from some of the chapters….Some of the quotes come from this chapter by Joel West and Scott Gallagher

Open Innovation is the use of purposive inflows and outflows of knowledge to accelerate internal innovation, and expand the markets for external use of innovation, respectively. Open Innovation is a paradigm that assumes that firms can and should use external ideas as well as internal ideas, and internal and external paths to market, as they look to advance their technology. Open Innovation processes combine internal and external ideas into architectures and systems. They utilize business models to define the requirements for these architectures and systems. The business model utilizes both external and internal ideas to create value, while defining internal mechanisms to claim some portion of that value. Open Innovation assumes that internal ideas can also be taken to market through external channels, outside the current businesses of the firm, to generate additional value

…useful knowledge is scarce, hard to find, and hazardous to rely upon (a root cause of the NIH syndrome). In Open Innovation, useful knowledge is generally believed to be widely distributed, and of generally high quality

IP becomes a critical element of innovation, since IP flows in and out of the firm on a regular basis, and can facilitate the use of markets to exchange valuable knowledge. IP can sometimes even be given away through publication, or donation.

Recently, open source software has emerged as an important phenomenon that utilizes external knowledge in a network structure (Lerner and Tirole 2002; O’Mahoney 2003; Dedrick and West 2004; von Hippel 2005)

 Most software users would face significant switching costs in using some other software package, due to some combination of retraining user skills and converting data stored in proprietary file formats. As Arthur (1996) observes, software thus has tremendous positive returns to scale, generally allowing only one (or a small number) of winners to emerge.

These winners are tempted to extract rents from their customers by increasing prices and creating additional switching costs to protect those rents (Shapiro and Varian 1999). From these production economics, commercial software firms seek to build complete systems to meet a broad range of needs, in hopes of forestalling potential competitors and protecting high gross profit margins

In other cases, a system architecture will consist of various components. Some mature (or highly competitive) components may be highly commoditized, while other pieces are more rapidly changing or otherwise difficult to imitate and thus offer opportunities for capturing economic value. Two open source examples are the IBM’s WebSphere and Apple’s Safari browser…

…Customers access the WebSphere e-commerce software using standard web browsers, so IBM originally developed a proprietary httpd (web page) server. IBM later abandoned its server for the Apache httpd server, recognizing that it would be wasting resources trying to catch up to the better quality and larger market share enjoyed by Apache (West 2003). Today, IBM engineers are involved in the ongoing Apache innovation, both for the httpd server and also related projects hosted by the Apache Software Foundation ( website)

Book Sprints at Force11

If you are at Force11 in Montreal, make sure you attend this!

Barbara Rühling, CEO of Book Sprints will be presenting.

Scholarly communication regularly faces the challenge to communicate across the gap between the expertise of the subject-matter experts and that of their readers, students, other disciplines, or communities outside of academia. Collaborative writing sprints are a chance for scholars to engage their readers directly by making them co-authors in the writing process.

The Book Sprints methodology has been used for ten years to create collaborative publications; by professors, students, and learn design experts to write open textbooks; by representatives of different disciplines mapping and defining an interdisciplinary field in formation; by academics and community activists to formulate guidebooks and manifestos.

Guided by a Book Sprints facilitator, the scholars and practitioners with different backgrounds constantly check each others biases and jargon, and thus ensure a publication both reader-friendly and useful for the target audience. And because the target audience is already engaged, each contributor becomes a valuable multiplier in the dissemination of the publication. The contributors are supported by an online collaborative writing environment developed by the Collaborative Knowledge Foundation and a team of Book Sprints’ designers and copy-editors co-creating the book in a five-day sprint.

This session explores some of the learnings of the last ten years in collaborative scholarly writing and publishing.



Hard to believe, but there are some cool things about NZ 🙂 Like… the timezone means I communicate with colleagues in the US in the morning…then later in the evening when folks in Europe wake up I can ping them and work out work things. Which means in between…..



Hindawi launches its Journal system today built on Coko PubSweet tech!!!

This week, Hindawi is releasing a new peer review system that will debut on Bioinorganic Chemistry and Applications. The new platform is open source, developed as part of Hindawi’s collaboration with the Collaborative Knowledge Foundation (Coko). This release is a first step towards a network of open publishing infrastructure that Hindawi, Coko, and collaborating organisations will develop and share with the research community.

This is major news for the Coko Community.

Gett’n in the manuka

If you know anything about New Zealand, or about honey, then you know about the famous manuka honey. As it happens, there are some hives at my place in NZ which yield some pretty good manuka honey.


So I’m replanting some of the land with manuka bushes… Manuka, in case you haven’t seen it, has a beautiful flower and right now it’s spring so the manuka bushes are all in flower at the moment.


Its a beautiful thing. I also have some grass on my land that I’m trying to get rid of, so I ran across the harbor today to Ahipara and bought 75 saplings.


And my neighbor Patrick, who has been doing some work on my land, has been digging them in.


Most of the larger shrubs to the immediate left of Patrick are manuka bushes around 3-5 years old. You can see some flowers on them. The really big ones at the back left I think might be 15 years old or so. Manuka can get big, it sort of transforms from a nice bushy bush to a wild twisty tree when it gets older. They can get quite huge. Anyways, in 2 years or so I should have a little 3-4ft manuka forest out there 🙂