Free every Friday • No spam • Unsubscribe anytime
Strategy comes before the roadmap. Strategy defines where you will play, what outcomes matter, how you expect to create value, and which choices you will not pursue. The roadmap then communicates the evolving sequence of outcomes, bets, or product changes intended to move that strategy forward.
Discovery can precede both because a team may need evidence before it can form a credible strategy. Learning can also send you back: roadmap evidence may reveal that the strategy needs to change.
Strategy versus roadmap in one table
- Strategy answers: What are we trying to achieve, for whom, why should our approach work, and what trade-offs will we make?
- Roadmap answers: Which outcomes or initiatives will we pursue now, next, and later to test and execute that strategy?
- Backlog answers: What specific work might the team do next?
- Delivery plan answers: Who will do committed work, in what sequence, with which dependencies and dates?
Why strategy must come first
Without strategy, a roadmap becomes an ordered collection of requests. It may show activity while offering no principled way to decide which customer, problem, outcome, or opportunity deserves priority.
A strategy gives roadmap decisions a test. An initiative belongs when there is a credible explanation of how it advances the chosen outcome and why it is more important than competing uses of time and money.
What a useful product strategy contains
- A specific customer or user context.
- The important problem or change in behavior to address.
- The outcomes that indicate progress.
- A differentiated approach or set of strategic choices.
- Capabilities, constraints, and assumptions that shape the approach.
- Explicit trade-offs and areas the product will not prioritise.
A slogan is not enough. The strategy should help two reasonable people make similar prioritisation decisions without asking the executive team to settle every item.
What belongs on a roadmap
A roadmap should express intent while leaving room to learn. Depending on the audience, it can show outcomes, problems, experiments, initiatives, product iterations, dependencies, and confidence. Near-term items may be more specific; distant items should acknowledge greater uncertainty.
The GOV.UK Service Manual advises that roadmaps should move toward a vision in iterations, show value to users, make priorities clear, and remain easy to adjust. It explicitly describes a roadmap as capturing intent rather than fixed solutions.
A practical sequence
- Discover: understand users, the system, constraints, evidence, and alternative explanations.
- Set direction: define the vision or desired future state.
- Choose strategy: select the customer, problem, outcomes, approach, and trade-offs.
- Build the roadmap: order the outcomes and initiatives that best test or execute the strategy.
- Plan delivery: turn the near-term roadmap into committed work only when enough is known.
- Review: use outcome data and new evidence to revise the roadmap and, when necessary, the strategy.
Can a roadmap exist before the strategy?
A draft can. Teams often sketch possible sequences during discovery to expose dependencies, cost, or uncertainty. But it should be labelled as an exploration, not treated as an approved roadmap. Otherwise tentative ideas acquire false certainty and begin consuming capacity before strategic choices have been made.
Common failure modes
- The feature calendar: dates and outputs are presented without the outcome they are supposed to create.
- The strategy poster: broad ambitions do not create meaningful trade-offs.
- The fixed promise: distant roadmap items are communicated as commitments despite weak evidence.
- The disconnected backlog: teams deliver tickets that cannot be traced to roadmap priorities and strategy.
- The unreviewed roadmap: new learning arrives, but the plan remains unchanged to preserve appearances.
Quick test
Choose one roadmap item and ask: Which strategic outcome does this support? What assumption does it rely on? Why is it ahead of the alternatives? What evidence will determine whether to continue? If the team cannot answer, the item is not yet strategically grounded.