Premium
From experience: Capturing hard‐won NPD lessons in checklists
Author(s) -
Riek Raymond F.
Publication year - 2001
Publication title -
journal of product innovation management
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 2.646
H-Index - 144
eISSN - 1540-5885
pISSN - 0737-6782
DOI - 10.1111/1540-5885.1850301
Subject(s) - checklist , new product development , benchmarking , process management , process (computing) , project management , product (mathematics) , operations management , business , computer science , psychology , engineering , marketing , systems engineering , geometry , mathematics , cognitive psychology , operating system
The application of a good New Product Development (NPD) process is frequently limited by the experience of the user. Avoiding relatively minor errors and omissions that can lead to seriously flawed project results is still an art. Checklists for each stage of a development project can capture this art and their disciplined use can avoid many potentially critical omissions and errors. Development of checklists frequently comes from the hard experiences many of us have had in bringing new products to market. Consequently, benchmarking “trials and tribulations” rather than success stories can be more appropriate to developing a thoughtful checklist. This article is a partial accumulation of one practitioner's experiences of over three decades of executing, managing, directing and observing these projects. Fifteen NPD case histories are examined to develop learnings from these experiences. These cases are organized around three basic product development issues: managing technical risks, managing commercial risks, and managing NPD personnel. In these examples, NPD project problems have a common theme of poor technical or commercial risk management, as opposed to technical failure. Improved planning and a more disciplined management interface would have avoided many of the problems discussed in these case histories. Analysis of each of the case histories and learnings is provided from which suggested checklist items are derived. These checklist additions are presented by development stage to allow use by other NPD teams, with the intention of avoiding the repetition of similar problems.