個案總覽

From Apple to Merck to Wikipedia, more and more organizations are turning to crowds for help in solving their most vexing innovation and research questions, but managers remain understandably cautious. It seems risky and even unnatural to push problems out to vast groups of strangers distributed around the world, particularly for companies built on a history of internal innovation. How can intellectual property be protected? How can a crowdsourced solution be integrated into corporate operations? What about the costs? These concerns are all reasonable, the authors write, but excluding crowdsourcing from the corporate innovation tool kit means losing an opportunity. After a decade of study, they have identified when crowds tend to outperform internal organizations (or not). They outline four ways to tap into crowd-powered problem solving--contests, collaborative communities, complementors, and labor markets--and offer a system for picking the best one in a given situation. Contests, for example, are suited to highly challenging technical, analytical, and scientific problems; design problems; and creative or aesthetic projects. They are akin to running a series of independent experiments that generate multiple solutions--and if those solutions cluster at some extreme, a company can gain insight into where a problem's "technical frontier" lies. (Internal R&D may generate far less information.)

The case describes OpenIDEO, an online offshoot of IDEO, one of the world's leading product design firms. OpenIDEO leverages IDEO's innovative design process and an online community to create solutions for social issues. Emphasis is placed on comparing the IDEO and OpenlDEO processes using real-world project examples. For IDEO this includes the redesign of Air New Zealand's long haul flights. For OpenIDEO this includes increasing bone marrow donor registrations and improving personal sanitation in Ghana. In addition, the importance of fostering a collaborative online environment is explored.

TopCoder develops software for clients through online tournaments, drawing from a community of 275,000 people. The case provides an update on TopCoder's growth and resulting changes in its platform and business model. Specifically, its decision to virtualize the project management role. Issues related to the scalability, profitability and growth of this approach are explored.

InnoCentive.com enables clients to tap into internal and external solver networks to address various business issues. In 2008, InnoCentive introduced "InnoCentive@Work" (lC@W), which recognized clients' reluctance to share problems and solutions with an external network. Instead, IC@W enabled clients to foster open collaboration amongst its own employees. IC@W became the fastest growing product in InnoCentive's portfolio. In 2010, InnoCentive added "team project rooms" which allowed small groups of solvers from InnoCentive's community to openly add posts and discussion threads after agreeing to the confidentiality and IP transfer requirements of the client. The case raises the questions of how the team room concept could be improved and how clients could be convinced of its benefits.

InnoCentive.com enables clients to tap into internal and external solver networks to address various business issues. This case focuses on the outcome of InnoCentive's decision to post challenges related to environmental issues created by the Gulf Oil Spill. It reviews lessons learned from this experience and asks students to consider whether InnoCentive should post challenges in response to the nuclear crises resulting from the 2011 Japanese earthquake and tsunami.

This case presents the logic and execution underlying the launch of Data.gov, an instantiation of President Obama's initiative for transparency and open government. The process used by Vivek Kundra, the federal CIO, and his team to rapidly develop the website and to make available high-value data sets for reuse is highlighted. The case recounts Kundra's experience at the state and local government levels in developing open data initiatives and the application of that experience to the federal government. The case demonstrates the benefits of making government data available in terms of both engaged citizens and the potential for new innovations from the private sector. Potential drawbacks of open access including security and privacy issues are illustrated. Issues related to the role of government in releasing data and the balance between accountability and private-sector innovation are explored.      

This case presents the Myelin Repair Foundation's accelerated research collaboration model for drug discovery. It highlights the challenges of building a multi-disciplinary and multi-institutional research collaboration that is attempting to create a treatment for multiple sclerosis based on a novel scientific approach. The case provides details on how norms of academic research and intellectual property had to be updated to enable collaboration. The current dilemma facing the CEO and COO of the foundation relates to setting strategic priorities for research so that a treatment for MS can be ready in the next ten years. The strategic choices need to account for the complexities of drug discovery, the uncertainty of commercial partners' interest in the therapeutic approach and the constrained donor-based fundraising environment.

TopCoder's crowdsourcing-based business model, in which software is developed through online tournaments, is presented. The case highlights how TopCoder has created a unique two-sided innovation platform consisting of a global community of over 225,000 developers who compete to write software modules for its over 40 clients. Provides details of a unique innovation platform where complex software is developed through ongoing online competitions. By outlining the company's evolution, the challenges of building a community and refining a web-based competition platform are illustrated. Experiences and perspectives from TopCoder community members and clients help show what it means to work from within or in cooperation with an online community. In the case, the use of distributed innovation and its potential merits as a corporate problem solving mechanism is discussed. Issues related to TopCoder's scalability, profitability, and growth are also explored.

This is an MIT Sloan Management Review article. Companies are aware of the potential benefits of "open innovation"-relying on outsiders both as a source of ideas and as a means to commercialize them -but they have struggled with precisely how to open up their product development to the external world. For starters, many executives have little idea how to motivate and manage outside innovation. Specifically, should external innovators be organized as a collaborative community or as a competitive market? Collaborative communities are perhaps best known through Linux and other open-source software efforts that are governed loosely by social norms and "soft" rules to encourage open access to information, transparency, joint development and the sharing of intellectual property. Competitive markets are strikingly different. Rather than collaborating, external innovators in a market will develop multiple competing varieties of complementary goods, components or services. Customers then choose from among the different offerings, and this often results in fierce competition -and little cooperation -among the innovators. Because the dynamics of communities and markets are so dramatically different, companies need to consider carefully which approach makes the best sense for their objectives. From their research, the authors have identified three critical issues that managers should take into account when making that decision: 1) the type of innovation that will be shifted to external innovators, 2) the motivations of those individuals, and 3) the nature of the platform business model. An in-depth analysis of those issues reveals that the choice between communities and markets is not as obvious -nor as clear-cut -as it might first appear.

Business ecosystems require careful orchestration and strategic choices regarding make/buy/partner decisions and membership access. This case examines the strategic and technological issues related to managing SAP's thriving ecosystem of user communities, software vendors, integration partners and technology providers. It details how the ecosystem gets developed and the challenges in meeting the needs of the internal organization, large partners, and small up and coming firms. SAP executives, in this case, have to make a decision if a relatively small startup firm should be elevated to the highest strategic partnership level, normally reserved for very large firms.

InnoCentive.com, a firm connecting R&D labs of large organizations to diverse external solvers through innovation contests, has to decide if they will enable collaboration in their community. Case covers the basics of a distributed innovation system works and the advantages of having external R&D. Links how concepts of open source are applied to a non-software setting. Describes the rationale for participation by solvers in innovation contests and the benefits that accrue to firms. Raises the issue if a community can be shifted to collaboration when competition was the basis of prior interaction.

Cambrian House builds internet-based products and services by relying entirely on its user community for all aspects of its innovation and new product development process. Users suggest ideas for new products and services and also participate in a monthly voting process to select the best ideas. The company is now considering the deployment of a prediction market to deepen user involvement and commitment in its innovation; however, it is not sure if it is an appropriate strategy for its community.

In its eight quarters of operation, Google's internally developed prediction market has delivered accurate and decisive predictions about future events of interest to the company. Google must now determine how to increase participation in the market, and how to best use its predictions.

Your problem solvers could not only be out in the wider world, but also in the wide reaches of your own organization.