Product Roadmap Template
A Now/Next/Later product roadmap template with strategic themes, initiative tables, dependency tracking, and a changelog. Works for any product stage. Free to copy, download, and use. No signup required.
# Product Roadmap **Product:** [Product Name] **Owner:** [Product Manager] **Last Updated:** [Date] **Horizon:** [Q1–Q2 2025 / H1 2025 / 12-month] --- ## Vision & Strategy > **Product vision (1 sentence):** [Where this product is going in 2–3 years] **Strategic bets this year:** 1. [Theme 1 — e.g. "Own the onboarding experience for SMB teams"] 2. [Theme 2 — e.g. "Build the integrations layer competitors can't match"] 3. [Theme 3 — e.g. "Move upmarket with enterprise-grade security"] --- ## Now — Current Quarter (Q[X] [Year]) > **Theme:** [What this quarter is focused on and why] | Initiative | Outcome | Status | Owner | Notes | |---|---|---|---|---| | [Feature/Project] | [Measurable customer outcome] | In progress | [Name] | [Any context] | | [Feature/Project] | [Measurable customer outcome] | In design | [Name] | | | [Feature/Project] | [Measurable customer outcome] | Not started | [Name] | Blocked by [X] | --- ## Next — Q[X+1] [Year] > **Theme:** [What this quarter is focused on] | Initiative | Outcome | Confidence | Owner | Notes | |---|---|---|---|---| | [Feature/Project] | [Measurable outcome] | High | [Name] | | | [Feature/Project] | [Measurable outcome] | Medium | [Name] | Needs research | | [Feature/Project] | [Measurable outcome] | Low | [Name] | Exploring | --- ## Later — Q[X+2]+ / Future > Items here are directional — sequence and scope may change. | Initiative | Strategic Rationale | Rough Size | |---|---|---| | [Feature/Project] | [Why this matters to strategy] | S / M / L / XL | | [Feature/Project] | [Why this matters to strategy] | S / M / L / XL | | [Feature/Project] | [Why this matters to strategy] | S / M / L / XL | --- ## Not Doing (and Why) | Request | Why Not Now | |---|---| | [Requested feature] | [Out of scope / low priority / technical constraint] | | [Requested feature] | [Waiting for X / deferred to later] | --- ## Key Dependencies & Risks | Dependency / Risk | Type | Owner | Mitigation | |---|---|---|---| | [Dependency] | External / Internal | [Name] | [Plan] | | [Risk] | Technical / Market | [Name] | [Plan] | --- ## How to Read This Roadmap - **Now** = committed for this quarter - **Next** = planned, subject to learning from Now - **Later** = directional, not committed - Dates are intentionally absent — this is a direction document, not a delivery schedule - Confidence levels: **High** = validated, scoped; **Medium** = rough idea; **Low** = hypothesis --- ## Changelog | Date | Change | Author | |---|---|---| | [Date] | [What changed and why] | [Name] |
How to use this Roadmap template
Anchor on strategy first
Fill in the Vision and Strategic Bets section before listing any initiatives. Every item on the roadmap should connect to one of your bets — if it doesn't, question why it's there.
Use Now/Next/Later, not dates
Date-based roadmaps become liabilities the moment a date slips. Now/Next/Later communicates direction without creating false commitments. Add dates only for items where external parties (customers, partners) require them.
Lead with outcomes, not features
Replace 'Add dashboard export' with 'Reduce data export time from 30 min to 2 min'. Outcome-framing forces you to be honest about what success means.
Maintain the 'Not Doing' list
Every roadmap needs a 'Not Doing' section. It signals to stakeholders that requests were heard and deliberately deferred — which is very different from being ignored.
Want a Roadmap grounded in your actual customer data?
PMRead ingests your customer interviews, feedback, and Slack threads — and generates PRDs backed by real evidence, not guesses.
Frequently asked questions
What's the difference between a roadmap and a backlog?
A roadmap communicates direction and strategy to stakeholders — it's outward facing. A backlog is a prioritized list of work for engineering — it's inward facing. Roadmaps operate at the initiative or outcome level; backlogs operate at the feature or ticket level.
How often should I update the product roadmap?
Now items should be reviewed weekly. Next items should be reviewed before each quarter. Later items can be reviewed quarterly. A roadmap that's never updated is worse than no roadmap — it creates false expectations.
Should the roadmap include time estimates?
For external-facing roadmaps (customers, investors), avoid specific dates unless you're confident in them. For internal roadmaps, rough quarters are fine. The Now/Next/Later format deliberately avoids dates to prevent the roadmap from becoming a project plan.
How do I handle stakeholder requests that don't fit the roadmap?
Log them in the 'Not Doing' section with a reason. This converts a 'no' into a 'not now, because...' — which is much easier for stakeholders to accept. Review the Not Doing list at each quarterly planning cycle in case priorities have shifted.
Other free templates