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

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

Towards Holistic “Front Ends” In New Product Development

Anil Khurana, Stephen R. Rosenthal·1998·Journal of Product Innovation Management

Abstract

Any firm that hopes to compete on the basis of innovation clearly must be proficient in all phases of the new-product development (NPD) process. However, the real keys to success can be found in the activities that occur before management makes the go/no-go decision for any NPD project. In other words, the most significant benefits can be achieved through improvements in the performance of the front-end activities—product strategy formulation and communication, opportunity identification and assessment, idea generation, product definition, project planning, and executive reviews. Noting the inherent difficulty of managing the front end, Anil Khurana and Stephen R. Rosenthal discuss findings from in-depth case studies of the front-end practices in 18 business units from 12 U.S. and Japanese companies. They offer a process view of the activities that the front end comprises, and they discuss the insights that their case studies provide regarding key success factors for managing the front-end activities. The case studies involved companies in industries ranging from consumer packaged goods to electronics and industrial products. Foremost among the insights provided by the case studies is the notion that the greatest success comes to organizations that take a holistic approach to the front end. A successful approach to the front end effectively links business strategy, product strategy, and product-specific decisions. Forging these links requires a process that integrates such elements as product strategy, development portfolio, concept development, overall business justification, resource planning, core team roles, executive reviews, and decision mechanisms. The case studies suggest that firms employ two general approaches for achieving these links. Some companies rely on a formal process to lend some order and predictability to the front end. Other companies strive to foster a company-wide culture in which the key participants in front-end activities always remain focused on the following considerations: business vision, technical feasibility, customer focus, schedule, resources, and coordination. This cultural approach is more prevalent among the Japanese firms in the study; the U.S. firms tend to rely on formality of the front-end process. The case studies also suggest that the front-end approach must be compatible with the firm's product, market, and organizational contexts. For example, standardized approaches seem to work best for incremental innovations.

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(97)00066-0

Cites

2 of 2 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 2 references

Cited by

Metadata

Authors
Khurana, A., & Rosenthal, S. R.
Venue
Journal of Product Innovation Management
Publisher
Wiley
Published
1998-01-01
Volume
15
Issue
1
Pages
57-74
ISSN
0737-6782 (ISSN-L)
OpenAlex
W2127406985
Cited by
706
References
2
FWCI
12.58
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

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.