Glossary · Product and planning
What is a product roadmap?
A product roadmap is a plan that shows where the major pieces of work sit over the coming months or quarters, and the dates other people depend on. It communicates direction and priority at the level of initiatives and milestones, not individual tasks, and it changes as the team learns. It answers what is next and roughly when.
Also called: Roadmap
Product roadmap, explained
A roadmap is a communication tool first. Engineers use it to see what is coming, sales uses it to know what to promise, and founders use it to explain the plan to investors. Each audience needs the same thing: a clear picture of the big bets and their order, without the noise of every ticket.
Roadmaps come in a few common forms. A timeline roadmap places initiatives as bars across months or quarters. A now, next, later roadmap avoids dates entirely and groups work by horizon, which is honest when timing is uncertain. An outcome roadmap organises work by the goal it serves rather than by feature. Many teams combine them: dated milestones where a commitment exists, looser horizons elsewhere.
The two classic mistakes pull in opposite directions. One is treating the roadmap as a promise, so every date becomes a deadline and every change a failure. The other is making it so vague it guides nothing. A useful roadmap is specific about the next few months, looser beyond, and updated whenever priorities actually change.
A roadmap also needs connection to the work. If initiatives are not linked to the projects and milestones that deliver them, the roadmap and reality drift apart, and nobody notices until a date is missed.
For example, a SaaS team's quarter shows three initiatives as bars: self-serve billing in October and November, a mobile app from November to January, and SSO in December. Inside the billing project, two milestones carry dates the finance team is waiting on: invoice export on 14 November and the tax update on 1 December.
How it works in Atrix
The Atrix roadmap shows initiatives as bars over months or quarters, with milestones as dated points inside projects. Everyone in the workspace can read it; moving things needs permission to manage products, checked again on every write. Saved views can be kept private or shared.
Read next
Related terms
- BacklogA backlog is the ordered list of work a team might do but has not yet committed to: features, fixes, improvements and ideas.
- OKR (objectives and key results)OKRs, objectives and key results, are a goal-setting method.
- PRD (product requirements document)A PRD, or product requirements document, describes what a product or feature must do and why, written before it is built.
- SprintA sprint is a fixed, short period, usually one to four weeks, in which a team commits to finishing a chosen set of work.