Show simple item record

dc.contributor.advisorBrad Morrison.en_US
dc.contributor.authorManning, Jeffrey (Jeffrey W.)en_US
dc.contributor.otherSystem Design and Management Program.en_US
dc.date.accessioned2009-03-16T19:30:02Z
dc.date.available2009-03-16T19:30:02Z
dc.date.copyright2008en_US
dc.date.issued2008en_US
dc.identifier.urihttp://hdl.handle.net/1721.1/44691
dc.descriptionThesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2008.en_US
dc.descriptionVita.en_US
dc.descriptionIncludes bibliographical references.en_US
dc.description.abstractInnovation is a hot topic; innovation is happening everywhere. Innovation is "romantic", reaching for the stars, against all odds, solving the problem no one thought possible. Most CEOs would not characterize survival as "romantic". Innovate or perish; the mantra, the truth, plain, stark, cold and naked. It gets worse; the environment is rapidly changing. Sophisticated customers are demanding quick responses with low cost, high quality products. What once worked with brilliant success is now failing. If innovation is happening everywhere, it is increasingly not happening here. During the past two years, a multi-vendor government project consisting of two vendors geographically segregated across three regions has seen tremendous success followed by almost total collapse. Initial program status and progress indicate near exponential trajectory: ahead of schedule, under budget and all functionality present. However, collapse was not too far off. The integration effort was a complete failure. Key schedule milestone dates were continuously missed. The gap between functionality believed completed and really completed widened. The story reads like a classic runaway project. Worse, the budget was near exhaustion. The central contribution of the analysis is the identification of the innovation trap. The innovation trap identifies conflicting corporate objectives governing the innovation strategy for new business development and the product development strategy of existing programs in the product pipeline. This study examines the innovation trap by applying System Dynamics techniques to develop a set of heuristics not only to identify collapse conditions but also how to address the problem. The goal of this study is to develop a concept for an improved organization and structure for today's high technology product companies where innovation is crucial for corporate success.en_US
dc.description.statementofresponsibilityby Jeffrey Manning.en_US
dc.format.extent122 leavesen_US
dc.language.isoengen_US
dc.publisherMassachusetts Institute of Technologyen_US
dc.rightsM.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission.en_US
dc.rights.urihttp://dspace.mit.edu/handle/1721.1/7582en_US
dc.subjectSystem Design and Management Program.en_US
dc.titleInnovation trap : can your innovation strategy cripple your product development?en_US
dc.title.alternativeCan your innovation strategy cripple your product development?en_US
dc.typeThesisen_US
dc.description.degreeS.M.en_US
dc.contributor.departmentSystem Design and Management Program.en_US
dc.identifier.oclc297178006en_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record