# Product Roadmap

A strategic communication artifact that connects product direction and desired outcomes to a changing sequence of investments.

- Type: artifact
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/product-roadmap/>)

## What it means

A product roadmap is a living view of how a product may advance its strategy over time. It communicates problems, outcomes, themes, or initiatives at an appropriate level of detail; it is not merely a dated feature list or a substitute for a delivery backlog.

## Why it matters

A useful roadmap makes priorities and tradeoffs discussable. It helps teams understand why work deserves investment, lets leaders compare direction with strategy, and gives partners enough context to coordinate without pretending that distant plans are certain.

## When to use it

Use a roadmap when several groups need a shared view of product direction, investment sequence, and current evidence. Tailor it for the audience and planning horizon, and revisit it when outcomes, constraints, assumptions, or learning materially change.

## How it works

1. Start with the product vision, strategic choices, target users, and measurable outcomes.
2. Group opportunities or initiatives by outcome, theme, or decision horizon rather than listing every backlog item.
3. Sequence investments using value, evidence, risk, dependencies, and available capacity.
4. Express timing with only the precision the evidence supports, distinguishing targets from commitments.
5. Review the roadmap with delivery, design, commercial, operational, and governance partners.
6. Update the artifact as learning changes priorities, while recording meaningful decisions and their rationale.

## A practical example

A subscription service wants to reduce avoidable cancellations. Its roadmap first emphasizes understanding cancellation triggers, then improving plan flexibility and recovery journeys, and later exploring loyalty benefits. Each initiative names an expected retention outcome and evidence threshold; exact features remain open until discovery narrows the options.

## Where it breaks

A roadmap cannot guarantee delivery dates or remove uncertainty. It can become theater when leaders treat it as a fixed contract, overload it with detail, or omit the evidence behind choices. Different audiences may require separate views, but those views should share one underlying strategy.

## Common mistakes

- Treating the roadmap as a fixed feature schedule.
- Including work without linking it to strategy or outcomes.
- Showing false precision for distant or poorly understood initiatives.
- Updating presentation details without revisiting the underlying choices.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/product-roadmap/#visualization-product-roadmap>)

## Sources

1. [Product Roadmap Guide: What Is It and How to Create One](<https://www.atlassian.com/agile/product-management/product-roadmaps>) — Atlassian · Professional guide
2. [Guide: How to Build a Product Roadmap](<https://www.productboard.com/product-roadmap-guide/>) — Productboard · Product management guide

## Related topics

- [Outcome-Based Roadmap](<https://wiki.soroush.uk/topic/outcome-based-roadmap/>)
- [Product Vision](<https://wiki.soroush.uk/topic/product-vision/>)
- [Release Planning](<https://wiki.soroush.uk/topic/release-planning/>)
