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

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

Implementing the lead user method in a high technology firm: A longitudinal study of intentions versus actions

Open access
Erik L. Olson, Geir Bakke·2001·Journal of Product Innovation Management

Abstract

The customer or user's role in the new product development process is limited or nonexistent in many high technology firms, despite evidence that suggests customers are frequently an excellent source for new product ideas with great market potential. This article examines the implementation of the Lead User method for gathering new product ideas from leading edge customers by an IT firm that had not previously done much customer research during their new product development efforts. This case study follows the decision-makers of the firm through the process, where the end result is the generation of a number of useful product concepts. Besides the ideas generated, management at the firm is also impressed with the way the method makes their new product development process more cross-functional and they plan to make it a part of their future new product development practices. Approximately one year later the firm is revisited to find out if the Lead User method has become a permanent part of their new product development process. The authors find, however, that the firm has abandoned research on the customer despite the fact that several of the lead-user derived product concepts had been successfully implemented. Management explanations for their return to a technology push process for developing new products include personnel turnover and lack of time. Using organizational learning theory to examine the case, the authors suggest that the nontechnology specific product concepts generated by the lead users were seen as ambiguous and hence overly simplistic and less valuable by the new product development personnel. The technical language spoken by the new product personnel also increased the inertia of old technology push development process by making it more prestigious and comfortable to plan new products with their technology suppliers. The fact that the firm was doing well throughout this process also decreased the pressure to change from their established new product development routine. The implications for these finding are that: 1) it is necessary to pressure or reward personnel in order to make permanent changes to established routines, and 2) researchers should be careful at taking managers at their word when asking them about their future intentions.

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(01)00111-4

Cites

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

Cited by

See all 247

Metadata

Authors
Olson, E. L., & Bakke, G.
Venue
Journal of Product Innovation Management
Publisher
Wiley
Published
2001-11-01
Volume
18
Issue
6
Pages
388-395
ISSN
0737-6782 (ISSN-L)
OpenAlex
W2070232732
Cited by
247
References
3
FWCI
15.44
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: Implementing the lead user method in a high technology firm: A longitudinal study of intentions versus actions. https://app.cochat.ai/papers/10.1016/s0737-6782(01)00111-4
The paper
Olson, E. L., & Bakke, G. (2001). Implementing the lead user method in a high technology firm: A longitudinal study of intentions versus actions. Journal of Product Innovation Management. https://doi.org/10.1016/s0737-6782(01)00111-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.