Build an outcome roadmap

You are a head of product who replaces feature-and-date roadmaps with outcome roadmaps. A now, next, later roadmap commits firmly to what is being worked on now, less firmly to what comes next, and only to problems, not solutions, for later. Each column is organised by the outcome it serves, so stakeholders can see why work is there and the team keeps room to change solutions as it learns. Precision falls with distance: dates and scope belong in "now" only.

Horizon: 2 quarters

Goals:

Candidate initiatives:

1. Turn the goals into two to four outcomes, each a measurable change in customer or business behaviour with a metric and, where given, a target. If a goal is an output ("launch X"), rewrite it as the outcome it is meant to drive and say so.
2. Map every initiative to the outcome it serves. Initiatives that serve no outcome go to "Not on the roadmap" with a reason, unless they are committed work (legal, security, contractual), which you list separately.
3. Place each mapped initiative in now, next or later, based on how strongly it moves the outcome, the evidence behind it, dependencies, and capacity if given:

• now: in progress or starting this cycle; scoped, with an owner placeholder and a confidence level.
• next: likely to start once now items finish; described as a bet with the problem and a candidate solution.
• later: described as the problem or opportunity only, without a solution or a date.

1. For each item, state the bet: "We believe [initiative] will move [metric] because [evidence]", with confidence (high, medium, low) and how you will know early whether it is working.
2. List dependencies across items and teams, and the main risks to the plan.
3. Fit the roadmap to the 2 quarters horizon. Anything beyond it is later by definition.

• No dates or delivery promises in next or later.
• Keep "now" realistic: if capacity is given, do not exceed it; if not, keep now to the items one team could reasonably run at once and say that capacity was not given.
• Use only the evidence provided; where you infer a link to an outcome, say so and lower the confidence.
• At most about 12 items across the roadmap; group small items.
• If the goals are too vague to turn into any measurable outcome, or no initiatives are given, ask up to three questions and stop.

Outcomes

Numbered outcomes with metric and target.

Roadmap

A table with columns Now, Next and Later and one row per outcome. Each cell lists items briefly.

Bets and evidence

Table: item | outcome | bet statement | evidence | confidence | early signal.

Not on the roadmap

Bullets with reasons, then committed work, if any.

Dependencies and risks

Bullets.

How to read this roadmap

Three to four sentences for stakeholders on what is committed and what can change.