What should a product roadmap include?

Group work into three horizons — now, next, and later — and attach a goal, an owner, and a confidence level to each item. The roadmap communicates intent and priority, not precise delivery dates for distant work.

What is the difference between an agile roadmap and a timeline roadmap?

An agile roadmap commits to outcomes by horizon (now / next / later) rather than to dated features on a Gantt chart. It stays honest about uncertainty: the further out an item is, the less precise its timing, and that is stated openly.

Should a roadmap have dates?

Put dates only on the 'now' column, where you are committed. 'Next' and 'later' communicate sequence and intent. Dating distant work invites it to be read as a promise, and missed promises cost trust.

How often should I update the roadmap?

On a fixed cadence — monthly or per planning cycle — and in the open. Items move between horizons as you learn. Keeping the roadmap in a wiki with version history means anyone can see what changed and when.

Product Roadmap Template — Template

TL;DR. A product roadmap is three horizons — now, next, later — with a goal attached to every item. Dates live only in “now.” Copy the body of this page into a wiki page and keep it honest about how sure you are.

A roadmap communicates intent and priority. It is not a delivery contract. The most common failure is treating distant items as promises; the fix is to attach a confidence level to each item and to put dates only where you are actually committed.

What a product roadmap includes

Three horizons. Now (committed), next (likely), later (directional).
A goal per item. The outcome it serves, not just the feature name.
An owner. Who to ask.
A confidence level. How sure you are, stated plainly.

How to use this template

Copy the body below into a new wiki page in your space.
Sort work into now, next, and later. Resist dating next and later.
Attach a goal to every item. No goal, not on the roadmap.
Mark confidence and owner.
Review on a cadence and move items between horizons in the open.

The template — copy from here

Roadmap summary

Product: <Name>
Owner: <Name, role>
Last reviewed: <date>
Theme this period: <one line — the through-line for "now">

Now

Item	Goal it serves	Owner	Confidence
`<item>`	`<outcome>`	`<name>`	`<high / medium>`

Item	Goal it serves	Owner	Confidence
`<item>`	`<outcome>`	`<name>`	`<medium / low>`

Later

Item	Goal it serves	Confidence
`<directional bet>`	`<outcome>`	`<low>`

Recently shipped

<item — date> <one line on what changed for users>

Common questions

What should it include? Three horizons, a goal per item, an owner, and a confidence level.

Agile versus timeline roadmap? The agile shape commits to outcomes by horizon, not dated features.

Should it have dates? Only in “now.” Next and later communicate sequence.

Keep the roadmap in a wiki with version history so the changes between reviews are visible to everyone. Pair it with the Product Brief Template for the items in “now,” and browse the template library for strategy and launch templates.