​

Quarterly Roadmap Planning Process

​

Overview

​

Timeline (4 weeks before Q start)

​

Week 1: Data Gathering & Analysis

• Review previous quarter performance
• Analyze product metrics and trends
• Compile customer feedback and research insights
• Conduct competitive analysis update
• Review strategic goals and OKRs
• Assess team capacity and resources

• Metrics dashboard review
• Customer insights summary
• Competitive landscape update
• Capacity planning document

• Product metrics review (CPO + analysts)
• Customer feedback synthesis (CPO + CSM team)

​

Week 2: Opportunity Prioritization

• Review and score all opportunities using RICE
• Validate technical feasibility with CTO
• Assess design requirements with UX Designer
• Identify dependencies and risks
• Draft preliminary roadmap themes
• Estimate resource requirements

• RICE-scored opportunity backlog
• Draft roadmap themes
• Resource allocation estimate
• Risk assessment

• Product team prioritisation workshop (full day)
• Tech feasibility review (CPO + CTO)
• Design requirements review (CPO + UX Designer)

​

Week 3: Roadmap Drafting & Alignment

• Draft detailed quarterly roadmap
• Align with leadership team (CEO, CTO, CMO)
• Get technical architecture review approval
• Confirm go-to-market support from CMO
• Validate compliance requirements
• Adjust based on feedback
• Finalize resource allocation

• Draft quarterly roadmap
• Updated capacity plan
• Risk mitigation strategies
• Launch schedule

• Leadership team roadmap review (2 hours)
• Architecture review board (if applicable)
• Compliance review (for regulated features)

​

Week 4: Finalization & Communication

• Finalize roadmap document
• Create PRDs for Q1 features
• Get executive approval
• Prepare communication materials
• Schedule kickoff meetings
• Set up tracking dashboards

• Final quarterly roadmap
• Communication deck
• Feature PRDs (at least drafts)
• Success metrics dashboard

• Executive approval meeting
• All-hands roadmap presentation
• Team kickoff meetings

​

Roadmap Planning Framework

​

Strategic Inputs

• Annual strategic goals
• Company OKRs
• Market positioning
• Competitive threats and opportunities

• Product vision and strategy
• North Star Metric goals
• Product-market fit assessment
• Technical debt priorities

• Top customer requests
• User research findings
• Churn analysis
• Usage patterns and trends

• Competitive analysis
• Industry trends
• Regulatory changes
• Technology advancements

​

Capacity Planning

Available person-months = Team size × 3 months × Utilization rate

Example:
- Engineering: 5 people × 3 months × 0.7 = 10.5 person-months
- Design: 2 people × 3 months × 0.7 = 4.2 person-months
- Product: 1 person × 3 months × 0.7 = 2.1 person-months

• 0.7 = 70% on new features (30% for bugs, support, meetings, etc.)
• Adjust based on team maturity and context

• New Features: 60-70%
• Bug Fixes: 15-20%
• Tech Debt: 10-15%
• Innovation/Experimentation: 5-10%

​

Theme-Based Planning

• Goal: Reduce time on administrative tasks by 40%
• Features: Automated rebalancing, batch reporting, smart alerts
• Metrics: Time saved per task, tasks completed per day

• Goal: Increase client digital engagement by 50%
• Features: Client portal enhancements, mobile app, notifications
• Metrics: Client login frequency, feature adoption, NPS

• Goal: Zero compliance violations, reduce audit findings
• Features: Enhanced audit trails, automated compliance checks
• Metrics: Violations, audit findings, reporting accuracy

​

Prioritization Criteria

• Reach × Impact × Confidence / Effort

• Strategic importance (2x multiplier for strategic priorities)
• Regulatory requirements (must-have, schedule accordingly)
• Customer retention risk (high-value customer requests)
• Competitive threats (features needed to maintain parity)

​

Roadmap Structure

​

Committed (High Confidence)

• Clear scope and requirements
• Resources allocated
• Dependencies resolved
• 90%+ confidence

​

Stretch Goals (Medium Confidence)

• Scope defined but flexible
• Resources tentatively allocated
• Some dependencies unresolved
• 60-80% confidence

​

Under Exploration (Low Confidence)

• Scope still being refined
• Feasibility being validated
• Resource needs being assessed
• 30-50% confidence

​

Risk Management

​

Common Risks

• Mitigation: Clear PRDs, change control process
• Escalation: CPO approval required for scope changes

• Mitigation: Early tech spikes, architecture review
• Escalation: CTO involvement, timeline adjustment

• Mitigation: Identify dependencies early, weekly checkpoints
• Escalation: Remove dependencies or defer feature

• Mitigation: Buffer in capacity planning (70% utilization)
• Escalation: Hire contractors, defer lower-priority work

• Mitigation: Monitor regulatory landscape, build flexibility
• Escalation: Reprioritize roadmap, fast-track compliance work

​

Risk Review Cadence

​

Success Criteria

​

Planning Process

• Roadmap finalized 2 weeks before quarter start
• All stakeholders aligned on priorities
• PRDs drafted for Q1 features
• Resources allocated and committed
• Success metrics defined for each feature

​

Execution

• 80%+ of committed features delivered on time
• Success metrics met for shipped features
• No major surprises or unplanned work
• Team satisfaction with planning process

​

Outcomes

• Product metrics improving toward goals
• Customer satisfaction with new features
• Business impact visible and measurable
• Team aligned and motivated

​

Communication Plan

​

Internal Communication

• Weekly updates to leadership team
• Team-wide planning progress updates

• Leadership roadmap review meeting
• Feedback incorporation and iteration

• Executive approval presentation
• All-hands roadmap announcement
• Team kickoff sessions

• Weekly status updates in product review
• Monthly roadmap progress reports
• Adjustments as needed (documented)

​

External Communication

• Share roadmap themes (not specific dates)
• Gather feedback on priorities
• Build excitement for upcoming features

• Detailed roadmap walkthrough
• Sales enablement materials
• Competitive positioning

• Beta programme invitations
• Early access opportunities
• Feature preview sessions

• High-level roadmap themes only
• No specific dates or commitments
• Focus on vision and direction

​

Templates & Tools

• Roadmap template: /templates/roadmap-template.md
• RICE scoring sheet: /templates/rice-scoring-template.csv
• Capacity planning: /templates/capacity-planning-template.md

• All-hands deck template: /templates/roadmap-presentation-template.pptx
• Executive summary: /templates/roadmap-executive-summary.md

• Roadmap dashboard: [Link to dashboard]
• Success metrics: [Link to metrics dashboard]

​

Retrospective

• What did we commit to vs. what did we deliver?
• What went well in planning and execution?
• What could we improve?
• Were our estimates accurate?
• Did we focus on the right things?
• How effective was our prioritisation?

​

Related Processes

• Prioritization framework: /frameworks/prioritisation.md
• Product development lifecycle: /frameworks/product-lifecycle.md
• Weekly product review: /processes/weekly-product-review.md
• OKR framework: /frameworks/metrics.md#okr-framework