Product Roadmap Template: Three Copyable Formats With Examples
Three roadmap templates you can copy today, from the simplest to the most detailed, with worked examples and a pre-share checklist.
Use Now–Next–Later as your default roadmap template: it shows direction and order without dates. Use an outcome roadmap when results matter more than output, and a quarterly timeline only when other teams need dates, with confidence labels. Start with the goal, keep items few, and keep a “Not now” list.
- Which template should you use?
- Template 1: Now – Next – Later
- Template 2: Outcome roadmap
- Template 3: Quarterly timeline
- How to use these without them becoming shelfware
- Template 4: A one-page roadmap narrative
- Writing roadmap items that people understand
- Presenting it in ten minutes
- Before you share it, check
- Mistakes people make with templates
Nobody wants another lecture on roadmaps; they want something to copy. Below are three templates I would actually use, from the simplest to the most detailed, each with a filled-in example and notes on when to pick it. Copy the text into a doc or spreadsheet and replace the brackets. If you want the thinking behind them first, read the complete roadmap guide.
Which template should you use?
| Template | Use when | Effort |
|---|---|---|
| 1. Now – Next – Later | You want direction without dates. Best default. | Ten minutes |
| 2. Outcome roadmap | Your team is measured on results, not output. | An hour |
| 3. Quarterly timeline | You must coordinate with sales, marketing or partners. | Half a day |
Template 1: Now – Next – Later
The simplest useful format. Now is what the team is working on; Next is what is likely to follow if Now goes well; Later is what you are considering but have not committed to.
Product: [name] Owner: [you] Updated: [date]
Goal this period: [one outcome, e.g. raise week-4 retention]
NOW (in progress)
• [Initiative] — problem it solves: [ ] — metric: [ ]
• [Initiative] — problem: [ ] — metric: [ ]
NEXT (likely, depends on Now)
• [Initiative] — why: [ ]
• [Initiative] — why: [ ]
LATER (exploring, not committed)
• [Idea] — what we need to learn first: [ ]
NOT NOW (decided against, with reason)
• [Request] — reason: [ ]
The “Not now” list matters more than it looks. It shows requesters that their idea was heard and decided on, which saves you endless repeat conversations.
Filled-in example
Template 2: Outcome roadmap
Use this when leadership asks “what will change for users and the business”, not “what are you building”. Each row is an outcome, and the ideas sit underneath it.
Outcome 1: [what changes, for whom]
Target: [metric] from [x] to [y] by [date]
Why now: [evidence]
Bets we are trying:
1. [idea] — confidence: low / medium / high — cost: [ ]
2. [idea] — confidence: [ ] — cost: [ ]
What we will learn first: [riskiest assumption and test]
Outcome 2: [repeat the block]
Filled-in example
| Outcome | Target | Bets | First learning |
|---|---|---|---|
| Learners who start a course finish it | Completion 30% → 40% by Q2 | Split long exercises; reminder after lesson 2 | Does splitting exercise 3 lift progression? |
| Learners return in week two | Week-2 return 35% → 45% | Weekly progress summary; streak recovery | Do summaries get opened? |
Template 3: Quarterly timeline
The most detailed format, for when other teams genuinely need dates to plan around. Keep it to one quarter of firm items and the next quarter of tentative ones, and label confidence honestly so dates are not read as promises.
Quarter: [Q?] Theme: [ ]
| Month 1 | Month 2 | Month 3 |
| [Item] (confidence: high) | [Item] (confidence: medium) | [Item] (confidence: low) |
Dependencies: [team / system] needed by [date]
Risks: [risk] — mitigation: [ ]
Assumptions: [ ]
The confidence label is the whole trick. A “low confidence” item in month three tells everyone it may move, and saves you from being held to a date.
How to use these without them becoming shelfware
Start with the goal, never with the list of ideas. Keep three to five items in Now. Share it with two people and ask “what is missing or unclear?” before broader circulation. Review monthly and delete things: a roadmap that only grows is a graveyard.
Template 4: A one-page roadmap narrative
Sometimes the best roadmap is a page of prose. It is very good for executives and for anyone who will not open a spreadsheet.
Where we are: [two sentences on the product’s current state and the key number]
What we are focusing on: [the one or two outcomes and why they matter now]
What we are doing about it: [three bets, each in one sentence with the problem it solves]
What we are not doing, and why: [two or three deliberate exclusions]
What could change this plan: [the assumptions and dates that would make us revisit]
Writing this page forces clarity that a grid of boxes never does. If you cannot fill in “what we are not doing”, you probably have not prioritised yet.
Writing roadmap items that people understand
| Weak item | Strong item |
|---|---|
| Improve search | Help returning users find results faster (target: time to first result under 10 seconds) |
| Notifications v2 | Bring back learners who miss two days in a row (target: 20% return within 3 days) |
| Redesign profile | Reduce profile-setup drop-off (target: 60% to 75% completion) |
A strong item states the problem or the outcome and a target, not just the name of a thing to build. It also leaves the team free to find the best solution, which is exactly what you want from them.
Presenting it in ten minutes
- Minutes 0-2: the goal and the one metric that shows if we are winning
- Minutes 2-6: the three bets, each with the problem and the evidence
- Minutes 6-8: what we chose not to do, and the trade-off
- Minutes 8-10: risks, what could change the plan, and the ask
Ask for challenge, not approval: “what is the biggest thing you think I am wrong about?” Leaders remember the plan more clearly when they have argued with it.
Before you share it, check
- Does it start from an outcome, not a feature list?
- Can a new team member understand each item without asking me?
- Are dates avoided, or clearly marked as tentative?
- Is there a “Not now” list with reasons?
- Does each item state the problem it solves and how we will measure it?
- Have I shown the right version to each audience?
Related: how to write a PRD for the level below a roadmap, and how to prioritize to decide what earns a place in “Now”.
Mistakes people make with templates
Filling in every box because it is there. Adding an owner and a date to every item, which makes it a project plan by stealth. Listing twenty items. Skipping the “not now” list. Sharing the internal version externally. And never updating it after the first week, so it becomes a poster rather than a tool.
Frequently asked questions
What should a product roadmap template include?
A goal or outcome, the initiatives grouped by how committed they are, the problem each solves and how success is measured, plus dependencies, risks and a list of things deliberately not being done.
What is the easiest roadmap format to start with?
Now – Next – Later. It shows direction and order without dates, is quick to create and update, and avoids being read as a set of delivery promises.
Can I use a spreadsheet for a product roadmap?
Yes. A spreadsheet or simple document is enough for most teams. Choose a tool your stakeholders will actually open and keep updated.
How many items should be on a roadmap?
Three to five items in Now is typical for a small team. Long lists dilute focus and are usually wishlists, not roadmaps.
Want this sharpened for your specific situation?
I take on a small number of career calls and resume reviews each month.
See how we could work together