Developments in Practice XXIII: Creating and Evolving a Technology Roadmap
Bibliographic record
Abstract
The authors convened a focus group of senior IT managers from a variety of different companies/industries to explore current practice in terms of creating and evolving a technology roadmap. Starting with a definition of a technology roadmap, the paper outlines the benefits attributable to a well-crafted roadmap and presents a 7-step model for its creation. According to the focus group, companies without the guidance of a roadmap run the risk of making sub-optimal decisions - technology choices that make sense today but position the company poorly for the future. The focus group also argued that the exercise of developing a technology roadmap is valuable even if the actual roadmap that is developed is subject to frequent change. This paper represents a summary of the focus group discussion.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.037 | 0.035 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.008 | 0.009 |
| Scholarly communication | 0.012 | 0.015 |
| Open science | 0.002 | 0.011 |
| Research integrity | 0.004 | 0.005 |
| Insufficient payload (model declined to judge) | 0.005 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".