Managing New Product Development Teams in a Globally Dispersed NPD Program
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Globalization is a major market trend today, one characterized by both increased international competition as well as extensive opportunities for firms to expand their operations beyond current boundaries. Effectively dealing with this important change, however, makes the management of global new product development (NPD) a major concern. To ensure success in this complex and competitive endeavor, companies must rely on global NPD teams that make use of the talents and knowledge available in different parts of the global organization. Thus, cohesive and well‐functioning global NPD teams become a critical capability by which firms can effectively leverage this much more diverse set of perspectives, experiences, and cultural sensitivities for the global NPD effort. The present research addresses the global NPD team and its impact on performance from both an antecedent and a contingency perspective. Using the resource‐based view (RBV) as a theoretical framework, the study clarifies how the internal, or behavioral, environment of the firm—specifically, resource commitment and senior management involvement—and the global NPD team are interrelated and contribute to global NPD program performance. In addition, the proposed performance relationships are viewed as being contingent on certain explicit, or strategic, factors. In particular, the degree of global dispersion of the firm's NPD effort is seen as influencing the management approach and thus altering the relationships among company background resources, team, and performance. For the empirical analysis, data are collected through a survey of 467 corporate global new product programs (North America and Europe, business‐to‐business). A structural model testing for the hypothesized effects was substantially supported. The results show that creating and effectively managing global NPD teams offers opportunities for leveraging a diverse but unique combination of talents and knowledge‐based resources, thereby enhancing the firm's ability to achieve a sustained competitive advantage in international markets. To function effectively, the global NPD team must be nested in a corporate environment in which there is a commitment of sufficient resources and where senior management plays an active role in leading, championing, and coordinating the global NPD effort. This need for commitment and global team integration becomes even more important for success as the NPD effort becomes more globally dispersed.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.006 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it