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

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

Interdepartmental Integration: A Definition with Implications for Product Development Performance

Kenneth B. Kahn·1996·Journal of Product Innovation Management

Abstract

Improved interdepartmental integration yields improved product development performance. But what do we mean by interdepartmental integration? Is it increased interaction between the various departments involved in product development—in other words, more meetings and other formal information flows between R&D marketing and manufacturing? Or is the term integration another way of saying collaboration—that is, various departments working collectively toward common goals? Or are collaboration and interaction both important elements of interdepartmental integration? Kenneth B. Kahn presents the results of a study exploring how collaboration and interaction affect product development performance and product management (post-launch) performance. Survey respondents are marketing, manufacturing, and R&D department managers working for firms in the electronics industry. It is hypothesized that both collaboration and interaction between departments will positively influence product development performance and product management performance. It is further hypothesized that collaboration will have a stronger effect than interaction. The survey responses indicate that collaboration has a strong, positive effect on performance. (The only exception is the effect of manufacturing managers' collaboration with marketing on product development success; the effect of this variable is not statistically significant). However, interaction does not have a significant effect on product development performance or product management performance. In fact, the responses indicate negative effects for meetings and the exchange of documented information. The results support increased emphasis on company policies that facilitate collaboration between departments as opposed to those that only stress meetings and documented information exchange. Although a certain level of interaction is necessary throughout the product development process, such interaction doesn't lead to success; collaboration makes the difference between success and failure. To best manage interdepartmental integration, managers should first assess their firm's levels of interdepartmental collaboration and interaction. The scales presented in this study can be used for this benchmarking effort. The results of this assessment can be used for developing and implementing an action plan for improving interdepartmental integration. For example, a manager faced with a prevailing interaction philosophy might seek to reduce the number of meetings or the amount of paperwork flowing between departments.

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/0737-6782(95)00110-7

Cites

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

Cited by

See all 619

Metadata

Authors
Kahn, K. B.
Venue
Journal of Product Innovation Management
Publisher
Wiley
Published
1996-03-01
Volume
13
Issue
2
Pages
137-151
ISSN
0737-6782 (ISSN-L)
OpenAlex
W2099832821
Cited by
619
References
28
FWCI
14.63
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: Interdepartmental Integration: A Definition with Implications for Product Development Performance. https://app.cochat.ai/papers/10.1016/0737-6782(95)00110-7
The paper
Kahn, K. B. (1996). Interdepartmental Integration: A Definition with Implications for Product Development Performance. Journal of Product Innovation Management. https://doi.org/10.1016/0737-6782(95)00110-7

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.