By Quick answer: What is a product roadmap and how do I make one?
- Purpose — connect strategy to work and align people.
- Format — now / next / later, by outcome or problem.
- Certainty fades — detail now, direction later.
- Not a release plan — keep committed dates separate.
- Living document — review monthly, revise quarterly.
Key takeaways
- Feature lists with dates create false certainty and erode trust when they slip.
- Framing items as problems or outcomes keeps teams free to find the best solution.
- Different audiences need different views — leadership, sales, the team.
- Saying what's not on the roadmap is as valuable as what is.
- A roadmap without a strategy behind it is just a backlog in a nicer format.
Roadmaps are the most political document in product management. Sales wants dates, leadership wants certainty, engineering wants focus, and customers want their feature. A roadmap that tries to please all of them becomes a promise list that breaks within a month. The fix is to change what a roadmap is for: not to predict the future, but to make the team's direction and priorities clear.
What a roadmap is — and isn't
| A roadmap is | A roadmap isn't |
|---|---|
| A view of direction and intended outcomes | A list of committed features with dates |
| Ordered by priority and confidence | A backlog |
| Linked to strategy and goals | A wishlist from every stakeholder |
| A living document | A contract |
Atlassian's guide covers roadmap types and audiences1; Marty Cagan has long argued for outcome-focused alternatives to feature roadmaps3.
Three common formats
Now – next – later
Popularised by Janna Bastow of ProdPad2. Detail now, direction later, no false dates.
Outcome-based
Rows are goals ("increase day-30 retention"), with problems and bets beneath each.
Timeline (use sparingly)
Quarters or months across the top. Useful for fixed external dates — regulations, events — but risky for everything else.
A now–next–later example
| Now (this quarter) | Next (1–2 quarters) | Later (exploring) | |
|---|---|---|---|
| Goal: activation | Shorten sign-up to under a minute | Personalised first-week plan | AI onboarding assistant |
| Goal: retention | Fix top three crash causes | Streaks and weekly summaries | Community features |
| Goal: revenue | Annual plan with UPI AutoPay | Family plan | Partner bundles |
The free template
1. Vision and strategy
One sentence on where the product is going; three goals for the year.
2. Outcomes
For each goal: the metric and target.
3. Now / next / later
Problems or bets under each outcome, with confidence (high, medium, low).
4. Not doing
Explicitly parked items, and why.
5. Dependencies and risks
What could change the plan.
6. Review cadence
When the roadmap will be revisited.
Presenting it
- Start with goals, not features.
- Show the why — evidence behind each item.
- Be explicit about confidence — more certain now, less later.
- Show what you're not doing and the trade-offs.
- Tailor the view — leadership sees outcomes; sales sees themes and timing ranges; the team sees detail.
To decide what goes in "now", see prioritisation frameworks; for committed items, write a PRD.
Key terms, defined
Roadmap — a plan of direction and intended outcomes. Release plan — committed near-term deliveries with dates. Outcome — a measurable change in user or business results. Now–next–later — a time-horizon roadmap format without fixed dates.
Frequently asked questions
What should a product roadmap include?
The product vision and goals, the problems or outcomes you plan to tackle, their rough sequence or time horizon, owners, and how you'll measure success. Avoid detailed feature specs and exact dates far into the future.
What is a now–next–later roadmap?
A format popularised by Janna Bastow of ProdPad that groups work into what you're doing now, what's next, and what's later, without fixed dates — reflecting that certainty decreases over time.
What's the difference between a roadmap and a release plan?
A roadmap communicates direction and intended outcomes. A release plan lists committed features with delivery dates for the near term. Mixing them leads to over-promising.
How often should a roadmap be updated?
Review it monthly and revise it quarterly, or whenever strategy or learning changes significantly. Communicate changes and the reasons for them.
What tools are used for product roadmaps?
Many teams use slides or docs; dedicated tools include Jira Product Discovery, Productboard, Aha! and ProdPad. The format and thinking matter more than the tool.
How do I present a roadmap to leadership?
Start with goals and strategy, show the outcomes you'll pursue and why, highlight trade-offs and what you're not doing, and be explicit about confidence levels.
Sources
- Atlassian — Product roadmaps
- ProdPad — Janna Bastow on inventing the now–next–later roadmap
- Marty Cagan, SVPG — Alternatives to product roadmaps
- Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Where to go from here
- Prioritisation frameworks — deciding what goes in 'now'
- PRD template — detail for the items you commit to
- Templates & toolsFree product roadmap template: the Now–Next–Later format, with examples and how to run itA free product roadmap template in the Now–Next–Later format, with a filled example for an app, how to tie items to outcomes, and mistakes to avoid.
- Career guidesProduct roadmapping skills employers want in 2027: outcome-based roadmaps, Now/Next/Later, links to strategy and OKRs, uncertainty and stakeholder alignmentProduct roadmapping skills employers want in 2027: outcome-based roadmaps, Now/Next/Later, OKR links, showing uncertainty and aligning stakeholders.
- Product managementPRD template: how to write a product requirements document your team will readA PRD template for product teams: problem, goals, users, solution, requirements, metrics, risks and decisions — plus a one-page version and writing tips.
- Product managementProduct manager resume: examples, bullet formulas and a template that gets interviewsWrite a product manager resume that gets interviews: an outcome-first bullet formula, before-and-after examples, a one-page template and tips.
- Templates & toolsRICE prioritization: the formula, a worked calculator table and how to score features honestlyRICE prioritization explained: the Reach × Impact × Confidence ÷ Effort formula, scoring scales, a worked calculator table for five features and common traps.
- UI/UX designUX case study template: the structure, an example, and how to tell the storyA UX case study template with a worked example: TL;DR, problem, constraints, research, options, decisions, testing, outcome and reflection.
Get the ideas, not the noise.
Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.
Bring evidence to your next roadmap debate.
A behavioral UX audit of your app or SaaS product: why users hesitate, stall and leave, and a prioritized fix list. Fixed price, 2–4 weeks.