Product strategy roadmap

A product strategy roadmap is the time phased expression of one product’s strategy: what you intend to achieve, in what order, and roughly when. It is a statement of intent and sequence, not a backlog, a release calendar or a list of features.

A digital product strategy names which products matter and where the company is betting. The roadmap is that strategy laid on a calendar, so somebody can tell whether the bet is being made this quarter or next year.

Everything useful about a roadmap comes from what it leaves out. A list of everything anybody requested is a backlog — a roadmap is the subset you are prepared to defend in public.

It also sits below the portfolio question. Deciding that a product deserves funding at all happens elsewhere; this document assumes the answer was yes and sequences what follows from it.

Key takeaways

• A product strategy roadmap sequences one product’s strategy over time: outcomes first, dates second.
• Organise it by the problem being solved, not by the features that might solve the problem.
• Name the confidence level of each horizon, because the far end of any roadmap is a hypothesis.
• If removing an item causes no argument anywhere, it was never strategy in the first place.

How it works

A product strategy roadmap works in horizons. Near term items are committed and dated, middle items are intended with a quarter attached, and far items are directions carrying no date at all. Confidence drops as the horizon stretches, and the document should say so.

The not doing row does more work than the rest of the table. It is the only part a stakeholder cannot read as a quiet yes — which is why it is the row most often deleted before the deck goes out.

Sequence is the argument, not the artwork. Two teams can agree on every item on a roadmap and still disagree about which one comes first — and that disagreement is the only conversation worth having.

A roadmap is worth little without a stated measure beside each outcome. Write down what would count as the item having worked, and the quarterly review becomes a comparison rather than a presentation.

Each item should arrive carrying evidence. A product discovery framework supplies that evidence, and federal design guidance treats discovery and design as separate phases of the work, each with its own concept guide and operations guide.

The roadmap also has to say who it is aimed at. A competitive positioning framework settles which buyer you are winning and against whom, and a roadmap that quietly contradicts it will be ignored by the sales team.

Publishing goals and then reporting against them is a discipline that some organisations are held to by statute.

Performance.gov exists because the Government Performance and Results Act (GPRA) Modernization Act of 2010 required a central reporting portal, and every agency page shows priority goals alongside strategic and performance plans.

Examples

Roadmaps look different by product type, and the differences are mostly about how far ahead the sequence can honestly be seen, and how much of the plan belongs to the customer rather than to engineering.

Enterprise software vendors publish a roadmap a year out and keep a private one behind it. The public version carries themes and quarters. The private version carries the dates that sales has already promised to three named accounts.

Regulated products sequence around dates nobody controls. A payments product in Europe plans around its compliance deadline first and arranges everything else around that, which produces a roadmap with one fixed post and the rest movable.

Services firms run the same exercise on their offering strategy, where the roadmap holds new service lines and the retirement of tired ones.

A product led growth strategy changes the sequence again, pushing onboarding, pricing pages and self serve work to the front of the plan.

Marketplaces sequence by side of the market. Supply has to arrive before demand can be served, so the first two quarters usually read as a supply plan even when the revenue target is written on the demand side.

Related terms

• Digital product strategy: the strategy itself; the roadmap is that strategy expressed as a sequence over time.
• Product discovery framework: the evidence pipeline that earns an item its place on the roadmap.
• Competitive positioning framework: the claim about which buyer you win, which the roadmap has to serve.
• Product marketing framework: how the roadmap’s output is launched, priced and explained to the market.
• Corporate strategy playbook: the company level strategy a single product roadmap has to fit inside.

FAQ

What is the difference between a product strategy roadmap and a release plan?

A roadmap states intent and sequence. A release plan states dates and contents. One survives a change of plan — the other is the plan, and it gets rewritten every time.

How far ahead should a roadmap go?

Four quarters is enough for most products. Beyond that you are writing directions rather than plans, which is still useful, as long as nobody in the room reads them as commitments. Mark the far horizon as a direction in the document itself.

Should a roadmap carry dates?

Dates on the near horizon, quarters on the middle one, nothing on the far one. Attaching a firm date to an item nobody has scoped is the fastest way to lose a stakeholder’s trust.

Who owns the roadmap?

The product team accountable for the outcome, not the committee that reviews it. Ownership that stops at presenting the slides is not ownership. The committee’s job is to challenge the sequence, not to write it.

How is it different from a program roadmap?

A product strategy roadmap covers one product over time. A program roadmap sequences many related projects toward one outcome and lives or dies on the dependencies between them.

Find product design and engineering partners who can deliver against a sequence you have already set at Outsource Accelerator.