​
Product Roadmap Template

Product: [Product Name] Time Period: [Q1 2026, 2026, etc.] Owner: Chief Product Officer Last Updated: [Date]

​
Vision & Strategy

​
Product Vision

[One paragraph describing where we’re headed long-term] Example:
To become the most productive wealth management platform that empowers advisors to focus on client relationships instead of administrative tasks.

​
Strategic Priorities

[Top 3-5 themes guiding this roadmap period]
  1. [Priority 1: e.g., Advisor Productivity] - Reduce time spent on administrative tasks by 50%
  2. [Priority 2: e.g., Client Experience] - Deliver world-class digital client experience
  3. [Priority 3: e.g., Compliance Excellence] - Maintain zero compliance violations

​
Key Metrics

  • North Star Metric: [Primary success metric]
  • Supporting Metrics: [2-3 key metrics to track]

​
Roadmap Overview

​
Timeline View

Q1 2026          Q2 2026          Q3 2026          Q4 2026
───────────────  ───────────────  ───────────────  ───────────────
Theme 1          Theme 1          Theme 2          Theme 3
- Feature A      - Feature B      - Feature D      - Feature F
- Feature C      - Feature E      - Feature G      - Feature H

Theme 2
- Feature X

​
Confidence Levels

  • Now (0-3 months): High confidence, committed
  • Next (3-6 months): Medium confidence, planned
  • Later (6-12 months): Low confidence, exploring
  • Future (12+ months): Vision, not committed

​
Now (Current Quarter)

​
Theme 1: [Theme Name]

Goal: [What we’re trying to achieve] Success Metrics:
  • [Metric 1]
  • [Metric 2]
Features:

​
Feature A: [Feature Name]

  • Status: In Development
  • Timeline: [Start date] - [Launch date]
  • Owner: [Name]
  • RICE Score: [Score]
  • Description: [Brief description]
  • Success Criteria:
    • [Criterion 1]
    • [Criterion 2]
  • Dependencies: [Any blockers or dependencies]
  • PRD: [Link to PRD]

​
Feature C: [Feature Name]

[Same structure as above]

​
Theme 2: [Theme Name]

[Same structure as Theme 1]

​
Next (Next Quarter)

​
Theme 1: [Continuing Theme]

Features:

​
Feature B: [Feature Name]

  • Status: Planned
  • Timeline: [Estimated quarter]
  • Owner: [Name]
  • RICE Score: [Score]
  • Description: [Brief description]
  • Discovery Status: [Not started | In progress | Complete]

​
Later (6-12 months)

​
Exploratory Initiatives

​
Initiative: [Name]

  • Why: [Problem or opportunity]
  • What: [High-level concept]
  • Impact: [Expected outcome]
  • Status: Exploring
  • Next Steps: [What needs to happen to validate this]

​
Future (12+ months)

​
Long-term Vision

[Describe major strategic initiatives or platform changes on the horizon]
  • [Initiative 1] - [Vision statement]
  • [Initiative 2] - [Vision statement]

​
Themes Deep Dive

​
Theme 1: [Theme Name]

Problem Statement: [What customer problem does this theme address?] Target Users: [Who benefits from this?] Business Impact: [What business outcomes do we expect?] Key Features:
  1. [Feature 1] - [Status]
  2. [Feature 2] - [Status]
  3. [Feature 3] - [Status]
Success Metrics:
  • [Metric 1]
  • [Metric 2]
  • [Metric 3]
Dependencies:
  • [Technical dependencies]
  • [Team dependencies]
  • [External dependencies]

​
Theme 2: [Theme Name]

[Same structure as Theme 1]

​
Prioritization Framework

​
How We Prioritize

We use RICE scoring to prioritise features:
  • Reach: Users impacted per quarter
  • Impact: 0.25-3 score
  • Confidence: Percentage
  • Effort: Person-months
Features with RICE > 500 are high priority. See full framework: /frameworks/prioritisation.md

​
Strategic Considerations

Features may be prioritised higher if they:
  • Address regulatory/compliance requirements
  • Solve critical customer pain points
  • Enable competitive differentiation
  • Unblock other high-value features
  • Support strategic partnerships

​
Feature Backlog

​
High Priority (RICE > 500)

FeatureRICEThemeStatus
[Feature 1]650[Theme]Planned for Q2
[Feature 2]580[Theme]In discovery

​
Medium Priority (RICE 100-500)

FeatureRICEThemeStatus
[Feature 3]350[Theme]Backlog
[Feature 4]280[Theme]Backlog

​
Low Priority (RICE < 100)

[List of lower priority items for reference]

​
Recently Shipped

​
[Last Quarter]

FeatureLaunch DateStatusImpact
[Feature X][Date]✅ Shipped[Key metric improved by X%]
[Feature Y][Date]✅ Shipped[Adoption at X%]
[Feature Z][Date]🔄 Measuring[Too early for data]

​
What We’re Not Doing

[Explicitly call out what’s NOT on the roadmap and why]
  • [Feature/Request] - Not aligned with strategy, deferred indefinitely
  • [Feature/Request] - Low ROI, considering removal from backlog
  • [Feature/Request] - Timing not right, revisit in 12 months
Why this matters: Being clear about what we’re not doing helps manage expectations and focus the team.

​
Risks & Dependencies

​
Risks

RiskImpactMitigationOwner
[Risk 1]High[Mitigation strategy][Name]
[Risk 2]Medium[Mitigation strategy][Name]

​
Cross-Team Dependencies

FeatureDepends OnTeamStatus
[Feature A][Dependency]EngineeringOn track
[Feature B][Dependency]ComplianceBlocked

​
Resource Allocation

​
Team Capacity

Current Quarter:
  • Product: [X person-months available]
  • Engineering: [X person-months available]
  • Design: [X person-months available]
Allocation:
  • Theme 1: [X%]
  • Theme 2: [X%]
  • Tech Debt: [X%]
  • Bug Fixes: [X%]

​
Hiring Needs

[Any team expansion needed to deliver roadmap]
  • [Role 1]: [Why needed, when]
  • [Role 2]: [Why needed, when]

​
Stakeholder Communication

​
Internal

Weekly:
  • Product team standup with status updates
Monthly:
  • Leadership team roadmap review
  • All-hands product update
Quarterly:
  • Board presentation
  • Major roadmap planning session

​
External

Quarterly:
  • Customer advisory board roadmap preview
  • Public roadmap update (high-level themes only)
As Needed:
  • Major feature announcements
  • Response to competitive moves

​
Feedback & Input

How to influence this roadmap:
  • Submit feature requests: [Process/link]
  • Share customer feedback: [Channel]
  • Propose new initiatives: [Process]
Roadmap Review Meetings:
  • Schedule: [Frequency]
  • Participants: [Who should attend]
  • Process: [How to prepare and participate]

​
Appendix

​
A. Supporting Documents

  • Product vision document: [Link]
  • OKRs: [Link]
  • Prioritization framework: /frameworks/prioritisation.md
  • Discovery process: /frameworks/discovery.md

​
B. Customer Research

  • [Link to research reports]
  • [Link to customer interviews]
  • [Link to usage analytics]

​
C. Competitive Analysis

  • [Link to competitive landscape]
  • [Link to feature comparison]

​
D. Technical Strategy

  • [Link to technical roadmap]
  • [Link to architecture decisions]

​
Version History

VersionDateChangesAuthor
1.0[Date]Initial roadmap for [period][Name]
1.1[Date][What changed][Name]