Templates & tools · Template

Free product roadmap
template

A good product roadmap template has three columns — Now, Next and Later — with each item framed as a problem or outcome rather than a feature, plus its goal metric, confidence level and owner. Now holds committed work, Next holds validated bets, and Later holds ideas still being explored. Review it monthly and share it widely, without fixed dates beyond the near term.

By , FounderUpdated 3 min read

Share

Quick answer: What should a product roadmap template include?

  1. Format — Now, Next, Later columns.
  2. Items — problems and outcomes, not just features.
  3. Fields — goal metric, confidence, owner, evidence.
  4. Dates — only for near-term commitments.
  5. Cadence — review monthly; share widely.

Key takeaways

  • A roadmap communicates strategy; it isn't a delivery schedule.
  • Outcome-framed items leave room for better solutions.
  • Confidence levels make uncertainty explicit and honest.
  • Fewer items with clear goals beat crowded timelines.
  • Tie every item to a product goal or OKR.

Most roadmaps fail in one of two ways. Either they're a Gantt chart of features with dates nobody believes, or they're so vague nobody can act on them. The Now–Next–Later format, popularised by ProdPad's Janna Bastow1, fixes both: it shows priorities honestly, by certainty rather than fake precision.

What should a product roadmap template include? At a glance: Format; Items; Fields; Dates; Cadence.
At a glance: What should a product roadmap template include?

The template

Now–Next–Later roadmap columns
ColumnWhat goes hereCertaintyDates?
NowProblems being solved this cycleHigh — committedYes, near term
NextValidated bets being shapedMediumRough
LaterProblems and ideas to exploreLowNo

Each card on the roadmap should carry:

Checklist: The template — Problem or outcome; Goal metric; Confidence; Owner; Link to the goal.
The template
  • Problem or outcome — "New users don't finish setup", not "Onboarding v2"
  • Goal metric — e.g. setup completion from 48% to 65%
  • Confidence — high, medium or low, with the evidence behind it
  • Owner — the person accountable
  • Link to the goal — which product goal or OKR it serves

A filled example for a fitness app

Example Now–Next–Later roadmap for a fitness app
NowNextLater
Lift week-1 retention: simplify first workout (owner: PM, confidence: high)Social challenges with friends (confidence: medium)Wearable integration (confidence: low)
Fix payment failures on UPI Autopay (owner: Eng lead)Personalised plans from user goalsCoach marketplace
Faster app start on low-end AndroidHindi and Tamil contentCorporate wellness offering

How to run it

Diagram of 6 steps for how to run it: 1. Start from goals; 2. Collect problems; 3. Prioritise; 4. Place by certainty; 5. Review monthly; 6. Share widely.
How to run it
  1. Start from goals — set OKRs or product goals first.
  2. Collect problems — from research, data, support and sales.
  3. Prioritise — use RICE or a similar method.
  4. Place by certainty — evidence-backed and committed go in Now.
  5. Review monthly — move items as evidence changes.
  6. Share widely — with a short narrative explaining the why.

Mistakes to avoid

Mistakes to avoid: Feature lists with dates; Everything in Now; No evidence; Roadmap as contract.
Mistakes to avoid

Feature lists with dates

Promise outcomes, not specific solutions a year out.

Everything in Now

If everything is a priority, nothing is.

No evidence

Every Now item should cite data or research.

Roadmap as contract

Atlassian's guide stresses roadmaps as communication tools that evolve2.

Marty Cagan argues for outcome-based alternatives to traditional feature roadmaps3 — the Now–Next–Later format is a practical step in that direction.

Key terms, defined

Product roadmap — a plan showing priorities and direction over time. Outcome — a measurable change in user or business behaviour. Backlog — the detailed list of work items. Confidence level — how sure you are an item will deliver its goal. Horizon — a time band such as Now, Next or Later.

Frequently asked questions

What is a Now–Next–Later roadmap?

A roadmap format that groups work by time horizon and certainty instead of fixed dates: Now (committed), Next (likely, being refined), and Later (ideas and problems to explore).

Should a roadmap have dates?

Use dates for near-term commitments and external deadlines. Further out, horizons communicate uncertainty more honestly than dates.

What's the difference between a roadmap and a backlog?

A roadmap shows strategic priorities and outcomes over time; a backlog is the detailed list of work items for the team.

Which tool should I use for a roadmap?

A spreadsheet, Notion, Jira Product Discovery, Productboard or a slide all work. Clarity matters more than the tool.

How often should a roadmap change?

Review monthly and update when evidence changes. Frequent small updates are healthy; constant reversals signal unclear strategy.

Who should see the roadmap?

The whole company, and a simplified version for customers or investors when helpful.

Sources

  1. ProdPad — The Now-Next-Later roadmap
  2. Atlassian — What is a product roadmap?
  3. Marty Cagan, SVPG — Alternatives to product roadmaps
  4. Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

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.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Templates help

Evidence helps more.

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.

Free certification

Turn what you know into a credential.

Free, test-based UX, UI and product certifications. Answer real product scenarios, graded on our server, and earn a founder-signed certificate anyone can verify and you can add to LinkedIn.

  • Credential ID
  • QR verification
  • LinkedIn-ready
Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy