A roadmap looks like a sequence of things. Strategy is a set of choices about where to play, how to win, and what not to pursue. The confusion is understandable: both are usually printed in the same deck and presented by the same person.
But a roadmap is closer to a negotiation transcript. It records what a group currently believes it can promise without starting a small civil war.
What a roadmap is really carrying
Every item has at least three stories attached to it:
- The customer story: someone has a meaningful problem.
- The business story: solving it matters to the organisation.
- The confidence story: we know enough to make this bet now.
When those stories disagree, the roadmap becomes a compromise. “We’ll do it in Q3” often means “we are not ready to say no, but we are also not ready to say yes.”
The promise problem
Roadmaps create anxiety because people use them for different jobs. Customers want reassurance. Sales wants a conversation starter. Leadership wants a view of investment. Delivery teams want sequencing. Product teams want room to learn.
One artifact cannot perfectly satisfy all five. The first useful move is to name the job the roadmap is doing.
If it is a customer communication tool, use themes and outcomes. If it is an investment view, show bets and confidence. If it is a delivery plan, include dependencies and dates. Do not call a list of delivery dates “strategy” because the slide has a bold heading.
A better test
Take an item off the roadmap and ask: what decision does this item help us make?
If the answer is “it tells people what we are building,” you have a plan-shaped communication artifact. Useful, but not strategy.
If the answer is “it commits us to learning whether this opportunity can move metric X for segment Y,” you are closer to a strategic bet.
Strategy has to survive without the timeline
Roger Martin defines strategy as an integrated set of choices, including what an organisation will not do. Remove dates and initiative names from a roadmap and ask whether those choices remain visible.
Can someone identify the customer or situation receiving disproportionate attention? Can they explain the mechanism by which the company expects to win? Can they see which attractive opportunities fall outside the bet?
If not, the roadmap may still be a useful delivery or communication plan. It simply cannot substitute for the choices that give the plan meaning.
Why dates colonise the conversation
Dates are concrete, socially powerful and easy to repeat. Strategy contains uncertainty and conditional logic. In a cross-functional meeting, “Q3” travels faster than “we believe this segment is underserved because…”. Over time, the date becomes the commitment while the original reasoning fades.
This is especially risky when teams learn during delivery. New evidence should change confidence, scope or sequence, but a date without its assumptions looks like a moral obligation. The team protects punctuality by reducing discovery, quality or honesty.
The answer is not a roadmap without dates. Some decisions genuinely require deadlines. The answer is distinguishing different confidence levels and explaining what the date represents: a hard external constraint, a planning target, a forecast or an aspiration.
An outcome is not automatically strategy
Replacing features with outcomes improves many roadmaps, but it can create a more sophisticated ambiguity. “Increase retention” or “improve activation” still does not explain where to play or how to win. Every competent subscription product would like better retention.
An outcome becomes strategic when it is attached to a diagnosis and choice: improve first-month retention for small accounting teams by removing the reconciliation setup burden, while declining advanced customisation work this half. Now the outcome constrains the work and exposes a bet.
SVPG’s alternative to roadmaps centres empowered product teams on objectives and measurable results rather than feature lists. The important shift is giving teams a problem and outcome while preserving room to discover the solution. It works only if leadership also supplies the strategic context and accepts that learning may change the route.
Build three connected artifacts
Instead of forcing one roadmap to serve every audience, separate the jobs:
- Strategy: the diagnosis, choices and logic of advantage.
- Bets: the outcomes, assumptions, confidence and investment currently supported by that strategy.
- Delivery view: sequencing, dependencies, milestones and dates needed to coordinate execution.
Connect them, but do not collapse them. A delivery item should point to a bet; a bet should point to a strategic choice. When the strategy changes, teams can see which bets need reconsideration. When delivery slips, the strategic logic does not automatically disappear.
The roadmap review worth having
Spend less time asking whether every item is green and more time asking whether the portfolio still reflects the choices.
Which bet gained or lost confidence? What did the organisation learn? Where is capacity contradicting the stated strategy? Which item remains because nobody has the authority to stop it? What new constraint changes sequencing without changing the bet?
This review treats the roadmap as a living investment conversation, not a ceremonial reading of coloured boxes.
Questions to take back to your team
- If you removed initiative names and dates, could a new colleague infer your strategic choices?
- Which roadmap date is a hard constraint, which is a forecast and which is organisational wishful thinking?
- What attractive work is absent because of the strategy rather than because capacity ran out?
- Which item remains on the roadmap because nobody wants to reopen the negotiation?
- When evidence changes, does the roadmap update—or does the team hide the learning to protect the colour green?
Choose one roadmap item and trace it backwards: delivery milestone, current bet, strategic choice and diagnosed problem. Where does the chain break?
My take
The most honest roadmap has a visible section called What we are not doing yet. It is not there to be dramatic. It tells the organisation that prioritisation is a choice with a cost, not a magic trick where every stakeholder gets a feature.
The roadmap earns trust when it tells the truth about confidence. Not every item needs a date. Every item needs a reason.