PJ-22 Technology roadmapping
Lay out how markets, products, technologies and resources are expected to evolve on a common time axis, giving a layered time chart with dependencies as a draft result.
What it does
Lays out how markets, products, technologies and resources are expected to evolve on a common time axis. Artefact: a layered time chart with dependencies; read milestones with no technology or resource milestone behind them.
When to use it
Use when you need to coordinate a plan across product, technology and resource layers and see what each milestone depends on.
When it does not fit
Dates are shown without owners or dependencies, or a plan is treated as a forecast.
Result format
The result is a layered chart on a common time axis, with separate layers for markets, products, technologies and resources and the dependencies between them marked. It names the milestones that have no technology or resource milestone behind them.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Unit of analysis | Always applies | requires=topic |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Structure, Content type, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | A goal, a horizon, a set of layers, and public roadmaps or announced release dates. |
|---|---|
| Additional sources needed | none |
| Not for (rules) | none |
| Not for (text) | Dates are shown without owners or dependencies, or a plan is treated as a forecast. |
Choosing and ordering
| Kind of technique | Primary technique, runs in step 5.3 |
|---|---|
| Phase tag | analyse |
| Other phase tags | report |
| Kind of finding | gap; risk |
| Question answered | what next; which option |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return to gather |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | assumption and limitation statement | none | no |
| decision-informing | assumption and limitation statement | none | no |
| decision-informing | source-span citation | none | no |
| decision-informing | expert review | needed; left out below high stakes | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | source-span citation | none | no |
| high-stakes | expert review | needed | no |
| high-stakes | independent review | needed | no |
| high-stakes | provenance log | none | no |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Shows dates with no owners or dependencies and treats announced dates as forecasts. |
| Error sources | input data; source selection; expert opinion |
| Certainty limits | Confidence drops when dates come from announcements with no delivery record (indirectness) or when dependencies are not tied to a named owner (inconsistency). |
Related techniques
- should follow PJ-23 Horizon scanning (environmental scanning): scanned signals show what to place on the chart
- pairs with DM-15 Wardley mapping: Wardley mapping shows the maturity of each component on the chart
Evidence and tag basis
Unconfirmed. Widely used per the note author; accuracy evidence not found; the usual framework reference was not opened.
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.