Product roadmap template: 3 formats with examples
Free product roadmap templates in three formats: now-next-later, quarterly by theme, and timeline with dependencies. Examples, audiences, and common mistakes.
The roadmap in the quarterly deck says "SSO: Q2." Engineering's plan says Q3, because a dependency slipped. Sales told two customers May. Three versions of the same roadmap, all in use, none the same.
The fix is usually fewer, clearer roadmaps, each made for one audience. This guide gives three formats and when to use each, drawing on Atlassian's product roadmap guide, checked on 16 November 2026.
What a roadmap is for
Atlassian defines a product roadmap as a shared source of truth for the vision, direction, priorities, and progress of a product over time. It notes that showing why matters as much as showing what: every item should link to strategy and goals.
It isn't a delivery plan. Atlassian recommends development teams keep a separate delivery plan, often organized by sprints, that maps back to the roadmap.
Pick the format by audience
| Audience | Format | Dates? |
|---|---|---|
| Product and engineering | Now-next-later | No |
| Executives | Quarterly by theme or goal | Quarters |
| Delivery planning | Timeline with dependencies | Months or sprints |
| Sales | Now-next-later, benefits-focused | No hard dates |
| Customers | High-level themes | No |
Template 1: Now-next-later
The most flexible format, and a good default.
| Now | Next | Later | |
|---|---|---|---|
| Goal: reduce churn in enterprise accounts | SSO with Okta and Azure AD | Admin audit log | Custom roles |
| Goal: grow self-serve signups | New onboarding checklist | Template gallery | Referral program |
| Goal: platform reliability | Move jobs to queue | Multi-region read replicas |
- Now: in progress or committed
- Next: starts when Now finishes; fairly confident
- Later: being considered; may change or drop
Rows are goals, so every item shows why it's there.
Template 2: Quarterly by theme
For leadership, who want progress against goals rather than features.
| Theme | Q1 | Q2 | Q3 | Q4 |
|---|---|---|---|---|
| Enterprise readiness | SSO | Audit log | Custom roles | Data residency |
| Self-serve growth | Onboarding checklist | Template gallery | Referrals | |
| Reliability | Job queue | Read replicas | ||
| Success metric | Churn under 2%/mo | Signups +20% |
Atlassian notes executive roadmaps are often organized by month or quarter and include less story-level detail.
Template 3: Timeline with dependencies
For delivery planning, where order and dependencies matter.
| Item | Owner | Start | End | Depends on | Status |
|---|---|---|---|---|---|
| SSO (Okta, Azure AD) | Arjun | Jan | Mar | Auth service refactor | On track |
| Auth service refactor | Mei | Dec | Feb | At risk | |
| Admin audit log | Sam | Apr | May | SSO | Not started |
| Custom roles | Arjun | Jun | Aug | Audit log | Not started |
The Depends on column is the reason this format exists. A slip in the auth refactor shows up as risk to three later items.
How to build one
- Start from goals, not a feature list. Two to four goals for the period.
- Phrase items as problems or outcomes where you can: "admins can see who accessed what" rather than "audit log v2."
- Pick the format for the audience.
- Name an owner for each item.
- Review it with engineering and design before sharing widely. Atlassian describes roadmaps as the result of ongoing collaboration across product, engineering, design, and marketing.
- Set an update cadence and stick to it.
Mistakes that break trust
- Dates on the sales roadmap. Atlassian specifically warns against hard dates there.
- A feature list with no goals. Nobody can tell what to cut when something slips.
- One roadmap for every audience. Executives get lost in detail; engineers lack it.
- No owner for updates. Copies multiply and drift.
- Treating Later as a promise. Say plainly that Later can change.
The decisions behind the roadmap
Every move on a roadmap is a decision: SSO before the audit log, data residency pushed to Q4, referrals cut. The roadmap shows the result, not the reason or who decided. When someone asks in June why custom roles slipped, the answer is in a meeting nobody wrote down.
Where Lockstep fits
Lockstep records those decisions where they're made, in PRDs, Slack, and pull requests, routes each to its owner for approval, and keeps the reason with the decision. Engineers and Claude Code sessions are briefed on the ones that apply to their work, so a re-prioritization reaches the people building.
See Lockstep for product teams.
Sources checked 16 November 2026
Related reading
For prioritizing what goes on the roadmap, see product decision-making frameworks and the decision matrix template. For pitching a new item, see the product one-pager template. For planning each sprint, see sprint planning with AI. For setting the goals a roadmap serves, see the OKR template. For understanding the market behind a roadmap, see the competitive analysis template. For announcing what shipped, see the release notes template. For shipping roadmap items, see the launch checklist.
Frequently asked questions
- What is a product roadmap?
- Atlassian describes it as a shared source of truth that outlines the vision, direction, priorities, and progress of a product over time. It shows what the team plans to build and, just as importantly, why, with items linked to product strategy and goals.
- What should a product roadmap include?
- The goal or theme each item serves, the items themselves as problems or outcomes, a time frame (exact dates, quarters, or now-next-later), an owner, and a status. Delivery detail such as sprints and tasks belongs in a separate delivery plan that maps back to the roadmap.
- What is a now-next-later roadmap?
- A roadmap with three columns instead of dates: Now for work in progress, Next for what's coming once that's done, and Later for ideas being considered. It communicates priority without committing to dates the team may not hit.
- Should a product roadmap have dates?
- Depends on the audience. Delivery plans and executive roadmaps often use months or quarters. Atlassian advises leaving hard dates out of sales roadmaps so teams aren't tied to unrealistic commitments, and external roadmaps usually stay high level.
- How often should I update a product roadmap?
- Whenever priorities change, and on a regular cadence, such as monthly or at each planning cycle. A roadmap that isn't updated stops being trusted and people start keeping their own versions.
Keep reading