PRODUCT MANAGEMENT TEMPLATE
Product Roadmap Template
Living roadmap with narrative context, Now/Next/Later sequencing, shipped outcomes, and stakeholder review history.
Use this templateWhat's inside
Field | Details |
|---|---|
Product / Product Line | Name |
Roadmap Period | Q1 2025 / H1 2025 / FY 2025 |
Last Updated | |
Owner | PM or product leader |
Status | Active |
Roadmap Narrative
Explain the story behind this roadmap in plain language. A table of initiatives tells people WHAT — the narrative tells them WHY things are sequenced this way, what we learned that changed the plan, and where we are headed.
Answer these questions in 3-5 paragraphs:
What did we ship last cycle, and what did we learn from it? Did the results validate our direction or change it?
What is the single most important thing we need to accomplish this cycle, and why?
What are we deliberately NOT doing, and what would need to change for us to reconsider?
What are the biggest unknowns, and how will we resolve them?
North Star & Key Metrics
Define the metrics that this roadmap is designed to move. Every initiative on the roadmap should connect to one of these metrics. If it doesn't, question whether it belongs.
Metric | Current | End-of-Period Target | Why This Matters |
|---|---|---|---|
North star metric (the one number that best captures the value you deliver) | Explain the connection to user value and business health | ||
Leading indicator 1 (moves before the north star) | |||
Leading indicator 2 | |||
Guardrail metric (must not regress) | Must not regress |
What We Shipped
Before looking forward, ground the reader in what happened. This creates accountability, celebrates wins, and ensures the roadmap builds on real outcomes rather than assumptions.
Initiative | Outcome | Metric Impact | What We Learned |
|---|---|---|---|
Recently shipped initiative | Hit Target | Metric moved from X to Y | Insight that informs what comes next |
Recently shipped initiative | Missed Target | Why it missed, and how that changes the plan | |
Initiative that was cut or deprioritized | Cut | N/A | Why it was cut and whether it returns later |
Now: In Progress
These initiatives are committed and actively being worked on. They have staffed teams, defined scope, and expected delivery dates. Moving anything out of "Now" requires a stakeholder conversation.
Initiative | Why Now | Target Outcome | Owner | Target Date | Status |
|---|---|---|---|---|---|
Initiative name | What makes this the highest priority — the user pain, business need, or strategic bet | Metric we expect to move | PM / Eng lead | On Track | |
Initiative name | On Track | ||||
Initiative name | At Risk |
Next: Planned
These initiatives are planned for the next cycle. Scope is understood at a high level but not fully specified. They will move to "Now" when current work completes, unless priorities change based on what we learn.
Initiative | Why This Comes Next | Expected Impact | Open Questions | Confidence |
|---|---|---|---|---|
Initiative name | What needs to be true from "Now" work, or what market signal drives the sequencing | Unresolved decisions that affect scope or approach | High | |
Initiative name | Medium | |||
Initiative name | Medium |
Later: Exploring
These are directional bets and opportunities we are actively thinking about but have not committed to. They may require research, prototyping, or market validation before they move to "Next."
Initiative | Hypothesis | What We Need to Learn | How We Will Validate | Confidence |
|---|---|---|---|---|
Initiative name | We believe [X] will [Y] because [Z] | Key unknown that determines whether we invest | Research, prototype, data analysis, or experiment | Low |
Initiative name | Low |
Items in "Later" are not a backlog — they are strategic options. If this list grows beyond 5-7 items, you are collecting ideas instead of making choices. Prune ruthlessly.
What We Are NOT Doing
Every roadmap should have a "not doing" list. This prevents the roadmap from becoming a wish list and gives stakeholders a clear place to see that their request was heard, considered, and intentionally deprioritized.
Request / Opportunity | Source | Why Not Now | Revisit When |
|---|---|---|---|
Feature or initiative being deferred | Customer / sales / exec / internal | Does not align with current north star / insufficient evidence / capacity constraint | Condition that would change the decision |
Dependencies & Risks
What could derail the plan? Dependencies are things we need from others; risks are things that could go wrong. For each, define the impact on the roadmap if it materializes.
Item | Type | Affects | Likelihood | Roadmap Impact | Mitigation / Contingency |
|---|---|---|---|---|---|
Dependency or risk description | Dependency | Which initiative is affected | High | Delays X by Y weeks / blocks Z entirely | Fallback plan |
Risk | Medium |
Resource Allocation
Make the investment trade-offs visible. This is the bridge between the roadmap (what we want to do) and reality (what we can do with the team we have).
Category | % of Capacity | Headcount | Notes |
|---|---|---|---|
New feature development (Now + Next initiatives) | XX% | N engineers | |
Maintenance, bugs, and operational work | XX% | N | Target: keep below 25% |
Technical debt and platform health | XX% | N | |
Exploration and prototyping (Later items) | XX% | N |
Stakeholder Review Log
Track roadmap review conversations and the decisions that came out of them. This creates a history of why the roadmap changed over time.
Date | Audience | Key Decisions / Feedback | Changes Made |
|---|---|---|---|
Leadership / Board / All-hands | Summarize the key discussion points | What changed on the roadmap as a result | |
Other Product templates
-
A/B Test PlanDesign an experiment with hypothesis, variants, success metrics, and sample size requirements. -
Competitive AnalysisAnalyze competitors across features, pricing, positioning, and market strategy. -
Feature SpecificationDetail a specific feature with user stories, acceptance criteria, edge cases, and dependencies.