keymodels
Menu
StrategyFramework / modelModelAccessible

Roadmap confidence horizons

How should roadmap specificity decrease as time horizon and uncertainty increase?

AccessibleOperationalTeam2 min read
Contents

A practical framework / model addressing this question: How should roadmap specificity decrease as time horizon and uncertainty increase?

The question it helps answer

Use the roadmap confidence horizons to organise the reasoning behind this question: How should roadmap specificity decrease as time horizon and uncertainty increase? The working view makes horizon bands, confidence thresholds, and allowed date precision visible so discussion can move from general opinion to a specific action or decision.

When to use it

Use the roadmap confidence horizons when people working on product strategy and roadmaps are using different mental models for horizon bands, confidence thresholds, and allowed date precision, and that difference is changing choices or coordination.

What it is

The roadmap confidence horizons is a set of connected concepts for examining one situation from several necessary angles. Its core working elements are horizon bands, confidence thresholds, allowed date precision, and evidence. Those elements belong together because each changes how the others should be interpreted or acted on.

Core elements

Horizon bands

Capture horizon bands only at the level needed to answer: How should roadmap specificity decrease as time horizon and uncertainty increase? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the roadmap confidence horizons, connect this entry to confidence thresholds so the relationship can be reviewed rather than inferred.

Confidence thresholds

Capture confidence thresholds only at the level needed to answer: How should roadmap specificity decrease as time horizon and uncertainty increase? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the roadmap confidence horizons, connect this entry to allowed date precision so the relationship can be reviewed rather than inferred.

Allowed date precision

Use a specific date or event, explain why it matters, and show dependencies that could change the timing. Within the roadmap confidence horizons, connect this entry to evidence so the relationship can be reviewed rather than inferred.

Evidence

Name the evidence, its date and owner, and any limitation that affects how confidently it can be used. Within the roadmap confidence horizons, connect this entry to commitment language so the relationship can be reviewed rather than inferred.

Commitment language

Test whether the responsible people understand the decision, can explain it consistently, and have accepted the actions that follow from it. Within the roadmap confidence horizons, connect this entry to review triggers so the relationship can be reviewed rather than inferred.

Review triggers

Record only the context that changes the work, separating verified facts from interpretations and assumptions. Within the roadmap confidence horizons, connect this entry to commitment language so the relationship can be reviewed rather than inferred.

Continue your preview

Read more of Roadmap confidence horizons.

Create a free account to continue this advanced article preview. Complete access is included in Pro and Team, so you can see the value before deciding to upgrade.

A longer article previewSaves, notes and reading progressNo card required