Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

PDMA Success Measurement Project: Recommended Measures for Product Development Success and Failure

PDMA Success Measurement Project: Recommended Measures for Product Development Success and Failure Success is not just elusive; it is also multifaceted and difficult to measure. A firm can assess the success or failure of a development project in any (or all) of many terms, including customer satisfaction, financial return, and technical advantage. To complicate matters, success may be measured not only at the level of the individual project, but also at the program level. With so many variables to consider and so many stakeholders involved, managers face a difficult challenge just deciding which measures are useful for measuring product development success. Recognizing that no single measure suffices for gauging the success of every product development project, Abbie Griffin and Albert L. Page hypothesize that the most appropriate set of measures for assessing project‐level success depends on the project strategy. For example, the objectives (and thus, the success criteria) for a new product that creates an entirely new market will differ from those of a project that extends an existing product line. Similarly, they hypothesize that the appropriate measures of a product development program's overall success depend on the firm's innovation strategy. For example, a firm that values being first to market will measure success in different terms from those used by a firm that focuses on maintaining a secure market niche. To test these hypotheses, product development professionals were presented with six project strategy scenarios and four business strategy scenarios. For each project strategy scenario, participants were asked to select the four most useful measures of project success. For each business strategy scenario, participants were asked to choose the set of four measures that would provide the most useful overall assessment of product development success. The responses strongly support the idea that the most appropriate measures of project‐level and program‐level success depend on the firm's project strategy and business strategy, respectively. For example, customer satisfaction and customer acceptance were among the most useful customer‐based measures of success for several project strategies, but market share was cited as the most useful customer‐based measure for projects involving new‐to‐the‐company products or line extensions. At the program level, firms with a business strategy that places little emphasis on innovation need to focus on measuring the efficiency of their product development program, while innovative firms need to assess the program's contribution to company growth. http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png The Journal of Product Innovation Management Wiley

PDMA Success Measurement Project: Recommended Measures for Product Development Success and Failure

Download PDF
19 pages

Loading next page...
 
/lp/wiley/pdma-success-measurement-project-recommended-measures-for-product-Tvind6PXyg

References (22)

Publisher
Wiley
Copyright
© 1996 Elsevier Science Inc.
ISSN
0737-6782
eISSN
1540-5885
DOI
10.1111/1540-5885.1360478
Publisher site
See Article on Publisher Site

Abstract

Success is not just elusive; it is also multifaceted and difficult to measure. A firm can assess the success or failure of a development project in any (or all) of many terms, including customer satisfaction, financial return, and technical advantage. To complicate matters, success may be measured not only at the level of the individual project, but also at the program level. With so many variables to consider and so many stakeholders involved, managers face a difficult challenge just deciding which measures are useful for measuring product development success. Recognizing that no single measure suffices for gauging the success of every product development project, Abbie Griffin and Albert L. Page hypothesize that the most appropriate set of measures for assessing project‐level success depends on the project strategy. For example, the objectives (and thus, the success criteria) for a new product that creates an entirely new market will differ from those of a project that extends an existing product line. Similarly, they hypothesize that the appropriate measures of a product development program's overall success depend on the firm's innovation strategy. For example, a firm that values being first to market will measure success in different terms from those used by a firm that focuses on maintaining a secure market niche. To test these hypotheses, product development professionals were presented with six project strategy scenarios and four business strategy scenarios. For each project strategy scenario, participants were asked to select the four most useful measures of project success. For each business strategy scenario, participants were asked to choose the set of four measures that would provide the most useful overall assessment of product development success. The responses strongly support the idea that the most appropriate measures of project‐level and program‐level success depend on the firm's project strategy and business strategy, respectively. For example, customer satisfaction and customer acceptance were among the most useful customer‐based measures of success for several project strategies, but market share was cited as the most useful customer‐based measure for projects involving new‐to‐the‐company products or line extensions. At the program level, firms with a business strategy that places little emphasis on innovation need to focus on measuring the efficiency of their product development program, while innovative firms need to assess the program's contribution to company growth.

Journal

The Journal of Product Innovation Management – Wiley

Published: Nov 1, 1996

There are no references for this article.