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

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

The Effect of “Front‐Loading” Problem‐Solving on Product Development Performance

Open access
Stefan H. Thomke, Takahiro Fujimoto·2000·Journal of Product Innovation Management

Abstract

In recent years, there has been a growing interest in the link between problem-solving capabilities and product development performance. In this article, the authors apply a problem-solving perspective to the management of product development and suggest how shifting the identification and solving of problems—a concept that they define as front-loading—can reduce development time and cost and thus free up resources to be more innovative in the marketplace. The authors develop a framework of front-loading problem-solving and present related examples and case evidence from development practice. These examples include Boeing's and Chrysler's experience with the use of “digital mock-ups” to identify interference problems that are very costly to solve if identified further downstream—sometimes as late as during or—after first full-scale assembly. In the article, the authors propose that front-loading can be achieved using a number of different approaches, two of which are discussed in detail: (1) project-to-project knowledge transfer—leverage previous projects by transferring problem and solution-specific information to new projects; and (2) rapid problem-solving—leverage advanced technologies and methods to increase the overall rate at which development problems are identified and solved. Methods for improving project-to-project knowledge transfer include the effective use of “postmortems,” which are records of post-project learning and thus can be instrumental in carrying forward the knowledge from current and past projects. As the article suggests, rapid problem-solving can be achieved by optimally combining new technologies (such as computer simulation) that allow for faster problem-solving cycles with traditional technologies (such as late stage prototypes), which usually provide higher fidelity. A field study of front-loading at Toyota Motor Corporation shows how a systematic effort to front-load its development process has, in effect, shifted problem-identification and problem-solving to earlier stages of product development. They conclude the article with a discussion of other approaches to front-load problem-solving in product development and propose how a problem-solving perspective can help managers to build capabilities for higher development performance.

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(99)00031-4

Cites

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

Cited by

See all 515

Metadata

Authors
Thomke, S. H., & Fujimoto, T.
Venue
Journal of Product Innovation Management
Publisher
Wiley
Published
2000-03-01
Volume
17
Issue
2
Pages
128-142
ISSN
0737-6782 (ISSN-L)
OpenAlex
W2118527025
Cited by
515
References
1
FWCI
24.17
Type
journal article
Language
en
Open access
bronze

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: The Effect of “Front‐Loading” Problem‐Solving on Product Development Performance. https://app.cochat.ai/papers/10.1016/s0737-6782(99)00031-4
The paper
Thomke, S. H., & Fujimoto, T. (2000). The Effect of “Front‐Loading” Problem‐Solving on Product Development Performance. Journal of Product Innovation Management. https://doi.org/10.1016/s0737-6782(99)00031-4

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.