Managing External Innovation: The Case of Platform Extensions

Managing External Innovation: The Case of Platform Extensions Managing External Innovation: The Case of Platform Extensions

www3.carleton.ca
from www3.carleton.ca More from this publisher
18.04.2014 Views

platform, information, and service (Hagiu, 2008). Although there might be a large number of developers willing to pay to gain access to the platform resource, platform owners are likely to exclude low-quality developers to protect the quality of the platform (Hagiu, 2009). Legal and contractual instruments Legal and contractual instruments are largely used to protect the contents of the platform and its components and reserve the rights of both platform owner and developers. Legal and contractual instruments are licensing and property rights and other traditional legal rules that are established between the platform owner and the third party developers to manage access to the platform, information, and services. An example is MySQL, which uses the Sun Contributor Agreement 1 . Platform architecture and design rules The platform architecture is a set of rules that define how platform modules communicate with each other and how to communicate with elements in the platform environment (e.g. applications, external components, etc). The platform owner defines the core design of the platform and the set interfaces that force boundaries among users and developers. The platform architecture enable the platform owners to define “an appropriate solution space” as von Hippel describes it, where the manufacturer (i.e. the platform owner) offers the user a certain degree of freedom to develop products within the production system 1 http://forge.mysql.com/wiki/Sun_Contributor_Agreement 21

(von Hippel, 2001). The platform architecture provides platform owners with a mean of virtually controlling the third party activities by imposing laws and design rules (Messerschmitt & Szyperski, 2003; Boudreau & Hagiu, 2009). User toolkits In the traditional product development model, the interface to the customer is the product prototype, and feedback on how well customer needs are met is only obtained late in the product development cycle. In the user innovation model of product development, the locus of innovation shifts from the company to the customer (Thomke & von Hippel, 2002). The new interface to the customer is now a platform that customers can adapt to create solutions to their needs (Thomke & von Hippel, 2002). The iterative experimentation needed to develop new products is now carried out by the customer. This results in significantly faster cycles and reduces cost. The creation of solutions is supported by a toolkit that allows users to carry out some of the product development tasks themselves. Toolkits present another form of software infrastructure that reduce the time and effort required to develop, provide, and operate applications, and contribute to quality of the product. Also the toolkits’ design plays an important role in increasing the opportunity to generate ideas in the community (Messerschmitt and Szyperski, 2003; Jeppesen, 2005). Mediating toolkits also play a significant role in ensuring quality, as identified by Rossi & Zamarian (2006). These toolkits crystallize effective solutions to recurring problems, and allow these "filtered" experiences to be shared. One motivation to use toolkits is the 22

(von Hippel, 2001). <strong>The</strong> platform architecture provides platform owners with a mean <strong>of</strong><br />

virtually controlling the third party activities by imposing laws and design rules<br />

(Messerschmitt & Szyperski, 2003; Boudreau & Hagiu, 2009).<br />

User toolkits<br />

In the traditional product development model, the interface to the customer is the product<br />

prototype, and feedback on how well customer needs are met is only obtained late in the<br />

product development cycle. In the user innovation model <strong>of</strong> product development, the<br />

locus <strong>of</strong> innovation shifts from the company to the customer (Thomke & von Hippel,<br />

2002). <strong>The</strong> new interface to the customer is now a platform that customers can adapt to<br />

create solutions to their needs (Thomke & von Hippel, 2002). <strong>The</strong> iterative<br />

experimentation needed to develop new products is now carried out by the customer. This<br />

results in significantly faster cycles and reduces cost. <strong>The</strong> creation <strong>of</strong> solutions is<br />

supported by a toolkit that allows users to carry out some <strong>of</strong> the product development<br />

tasks themselves. Toolkits present another form <strong>of</strong> s<strong>of</strong>tware infrastructure that reduce the<br />

time and effort required to develop, provide, and operate applications, and contribute to<br />

quality <strong>of</strong> the product. Also the toolkits’ design plays an important role in increasing the<br />

opportunity to generate ideas in the community (Messerschmitt and Szyperski, 2003;<br />

Jeppesen, 2005).<br />

Mediating toolkits also play a significant role in ensuring quality, as identified by Rossi<br />

& Zamarian (2006). <strong>The</strong>se toolkits crystallize effective solutions to recurring problems,<br />

and allow these "filtered" experiences to be shared. One motivation to use toolkits is the<br />

22

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!