MétaCan
Menu
Back to cohort
Record W4415209453 · doi:10.1080/14479338.2025.2573101

When to respond to technological platform changes: empirical evidence from the video game industry

2025· article· en· W4415209453 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

VenueInnovation · 2025
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicDigital Platforms and Economics
Canadian institutionsHusky Injection Molding Systems (Canada)
Fundersnot available
KeywordsPerspective (graphical)Product (mathematics)Quality (philosophy)Empirical evidenceNew product developmentComplementary goodVideo game

Abstract

fetched live from OpenAlex

Generational platform innovations prompt complementors to adapt their product development strategies. This paper examines how the speed of response to such platform changes affects new product quality and how this relationship is shaped by the complementor’s prior experience. Adopting a contingency perspective on the strategy-by-doing literature, we differentiate between depth of experience (repeated NPD experience with the same platform generation) and breadth of experience (accumulation of NPD experience across different generations), and analyse their interplay with the radicalness of the platform innovation. Using panel data from 1,014 PC video games released by 378 developers between 1995 and 2014 in response to DirectX platform generations and updates, we find that faster responses lead to higher product quality for complementors with greater depth of experience in incremental platform innovation contexts. In contrast, for radical platform changes, faster responses are harmful for complementors with a greater breadth of experience, suggesting that translating and integrating diverse platform knowledge into effective responses requires more time. Our findings contribute to research on platform evolution and strategy-by-doing by clarifying when faster technology responses help (or hinder) product performance in generational platform contexts.

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.000
metaresearch head score (Gemma)0.001
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.445
Threshold uncertainty score0.709

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0000.000
Scholarly communication0.0010.002
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.116
GPT teacher head0.299
Teacher spread0.183 · 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