MétaCan
Menu
Back to cohort
Record W2091070000 · doi:10.1111/1467-9310.00225

Portfolio management for new product development: results of an industry practices study

2001· article· en· W2091070000 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueR and D Management · 2001
Typearticle
Languageen
FieldEconomics, Econometrics and Finance
TopicCapital Investment and Risk Analysis
Canadian institutionsMcMaster University
FundersMcMaster University
KeywordsPortfolioProject portfolio managementNew product developmentPopularityApplication portfolio managementProduct (mathematics)Rank (graph theory)Set (abstract data type)Modern portfolio theoryBusinessMarketingComputer scienceEconomicsProject managementFinanceManagement

Abstract

fetched live from OpenAlex

Portfolio management for product innovation – picking the right set of development projects – is critical to new product success. This article reports on the new product portfolio practices and performance of a large sample of firms in North America. Reasons why portfolio management is important are identified, followed by the relative popularity of the different portfolio techniques: financial methods are first, followed by business strategy methods, bubble diagrams and scoring models. Next, how the various portfolio methods fare in terms of six performance metrics is probed. Financial methods, although the most popular and rigorous, yield the worst results overall, while top performing firms rely more on non‐financial approaches – strategic and scoring methods. The details of how some of these more popular methods are employed by firms to rate and rank development projects are also provided. Finally, managerial implications, including suggestions for making portfolio management more effective in industry, are outlined.

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 imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.715
Threshold uncertainty score0.547

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.073
GPT teacher head0.286
Teacher spread0.214 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it