Product Roadmapping

Communicating direction and sequencing over time, without over-committing to dates that will be wrong.

What it is

A roadmap communicates product direction and rough sequencing to stakeholders — engineering, sales, leadership — without functioning as a delivery contract with fixed dates.

Key points

Theme-based over date-based: roadmaps organized around themes/outcomes ("improve onboarding conversion") age better than ones with hard ship dates, which are usually wrong by the time they're reached.
Now/Next/Later is a common format that communicates confidence level implicitly — "Now" is committed, "Later" is directional and expected to shift.
A roadmap is a communication tool, not a project plan — the detailed sequencing and estimation happens at the sprint/engineering level, not on the roadmap itself.
Roadmaps need periodic re-justification against current priorities — a roadmap that never changes is usually a sign it's not actually being used to make decisions.