startthat.work home

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.

Project forwardEvidence: UnconfirmedPrimary technique, runs in step 5.3Strongest statement: describe

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

PropertyRequirement typeRequirement
Unit of analysisAlways appliesrequires=topic
Appraises source credibilityApplies in some casesno

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 materialA goal, a horizon, a set of layers, and public roadmaps or announced release dates.
Additional sources needednone
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 techniquePrimary technique, runs in step 5.3
Phase taganalyse
Other phase tagsreport
Kind of findinggap; risk
Question answeredwhat next; which option
Strongest statement it supportsdescribe
Needs as input
Makes as output
Must exist firstNone
Loop targetreturn 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.

StakesCheckPerson involvedCounts as a different method
exploratoryassumption and limitation statementnoneno
decision-informingassumption and limitation statementnoneno
decision-informingsource-span citationnoneno
decision-informingexpert reviewneeded; left out below high stakesno
high-stakesassumption and limitation statementnoneno
high-stakessource-span citationnoneno
high-stakesexpert reviewneededno
high-stakesindependent reviewneededno
high-stakesprovenance lognoneno

Failure modes and limits

Model suitabilityhuman judgement required
Typical model failureShows dates with no owners or dependencies and treats announced dates as forecasts.
Error sourcesinput data; source selection; expert opinion
Certainty limitsConfidence drops when dates come from announcements with no delivery record (indirectness) or when dependencies are not tied to a named owner (inconsistency).

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.