MétaCan
Menu
Back to cohort
Record W2105496147 · doi:10.1287/orsc.1030.0052

Organizing New Product Development Projects in Strategic Alliances

2004· article· en· W2105496147 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.

Bibliographic record

VenueOrganization Science · 2004
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicInnovation and Knowledge Management
Canadian institutionsCarleton University
Fundersnot available
KeywordsAllianceTransaction costBusinessNew product developmentCorporate governanceProduct (mathematics)Work (physics)Project governanceProject managementStrategic allianceKnowledge managementIndustrial organizationMarketingEconomicsComputer scienceManagement

Abstract

fetched live from OpenAlex

We utilize research on alliance governance structures and on new product development to study how partners working under an existing alliance governance structure will organize a new product development project. Initially, we consider a contractual alliance doing multiple projects and argue that the critical organization decisions for any project are whether one or both partners should be involved, whether the partners should work with little or considerable interaction, and whether decision-making authority should reside in a project manager or be consensual. Based on the answers to these questions, we identify at least four viable project organization options. We next examine the option that would be selected under conditions involving the alliance's newness, whether a cooperative history exists, and the distribution of skills for the project. Under each condition, we compare the costs and benefits of the options with respect to the underlying transaction costs, potential for learning, and the ability to contribute to developing a social relations network. By allowing variations in time-to-market pressures, the tacit knowledge that a partner can obtain from the project, and the partners' need to work closely together on future projects, we can determine the points at which costs and benefits indicate a switch from one organization option to another. Finally, we indicate how to adjust the theory for it to apply to a contractual alliance doing only one project and to an institutional alliance such as a joint venture.

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 categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.857
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.009
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.001

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.050
GPT teacher head0.247
Teacher spread0.196 · 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