Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 854

The DOI matches its OpenAlex record; 23 of the 23 references it cites were found in a registry or an index.

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

Abbie Griffin, Albert L. Page·1996·Journal of Product Innovation Management

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.

Overview

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

OpenAlex · 10.1016/s0737-6782(96)00052-5

Cites

23 of 23 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 23 references

Cited by

See all 854

Metadata

Authors
Griffin, A., & Page, A. L.
Venue
Journal of Product Innovation Management
Publisher
Wiley
Published
1996-11-01
Volume
13
Issue
6
Pages
478-496
ISSN
0737-6782 (ISSN-L)
OpenAlex
W2058473965
Cited by
854
References
23
FWCI
30.39
Type
journal article
Language
en
Open access
closed

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: PDMA Success Measurement Project: Recommended Measures for Product Development Success and Failure. https://app.cochat.ai/papers/10.1016/s0737-6782(96)00052-5
The paper
Griffin, A., & Page, A. L. (1996). PDMA Success Measurement Project: Recommended Measures for Product Development Success and Failure. Journal of Product Innovation Management. https://doi.org/10.1016/s0737-6782(96)00052-5

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.