Roadmap planning

Roadmap Planning

Roadmap Framework Selection

Framework	Best For	Avoid When
Now/Next/Later	Early stage, fast-moving teams	Exec demands dates
Theme-based	Communicating strategy to stakeholders	Engineers need task-level detail
Outcome-based	Product-led orgs with clear metrics	Teams new to product thinking
Date-based (Gantt)	Regulatory commitments, hardware	Uncertain scope
Opportunity-based	Discovery-focused teams	Waterfall organizations

Now / Next / Later Roadmap

NOW (current quarter — committed)
├── Feature A: [1-line description] → Metric impact: X
├── Feature B: [1-line description] → Metric impact: Y
└── Bug fix sprint: [theme]

NEXT (next 1-2 quarters — planned)
├── Initiative C: [problem statement]
├── Initiative D: [problem statement]
└── Platform investment: [debt/infra]

LATER (6+ months — directional)
├── Big Bet E: [vision item]
└── Exploratory F: [research needed]

Rules:

• NOW items have assigned engineers and estimated completion
• NEXT items have rough sizing (S/M/L/XL) and owner
• LATER items have no dates, may never ship

Theme-Based Roadmap

Q1: Activation & Onboarding
  → Reduce time-to-value from 14 days to 3 days
  ├── Guided setup wizard
  ├── Template library (top 5 use cases)
  └── In-app onboarding checklist

Q2: Retention & Engagement
  → Improve 30-day retention from 40% to 55%
  ├── Daily digest email
  ├── Collaboration features
  └── Mobile app v1

Q3: Expansion Revenue
  → Grow NRR from 105% to 115%
  ├── Usage-based pricing
  ├── Team management
  └── Advanced analytics

Q4: Platform & Integrations
  → 10 new integrations, 30% API-first customers
  ├── Public API v2
  ├── Zapier/Make integration
  └── Webhook builder

Outcome-Based Roadmap

Map every initiative to a measurable outcome:

Outcome: Reduce churn from 5% to 3% monthly
├── Hypothesis A: Users who complete setup churn 60% less
│   └── Initiative: Improve setup completion rate to 80%
├── Hypothesis B: Missing integrations drive churn
│   └── Initiative: Build top 3 requested integrations
└── Hypothesis C: Users don't discover key features
    └── Initiative: In-app feature discovery tooltips

Prioritization Methods

RICE Scoring

RICE = (Reach × Impact × Confidence) / Effort

Reach: Users affected per quarter (raw number)
Impact: 3=massive, 2=high, 1=medium, 0.5=low, 0.25=minimal
Confidence: 100%=high, 80%=medium, 50%=low
Effort: Person-months

Example:
Feature X: (500 × 2 × 0.8) / 3 = 266
Feature Y: (1000 × 1 × 0.5) / 1 = 500  ← prioritize

Weighted Scoring Matrix

Initiative	Strategic Fit	User Value	Revenue	Effort	Total
Weight →	30%	30%	25%	15%
Feature A	4	5	3	4	4.0
Feature B	5	3	5	2	3.8
Feature C	2	4	2	5	3.1

Score 1-5 for value dimensions, 5=least effort for effort dimension.

Kano Model Classification

• Must-Have (Basic): Users expect this; absence causes dissatisfaction
• Performance: More = better satisfaction (speed, storage, seats)
• Delighter: Unexpected, creates delight; becomes must-have over time
• Indifferent: Users don't care either way
• Reverse: Some users prefer absence

Use survey: "If [feature] were present, how would you feel?" + "If absent?"

Stakeholder Alignment

Roadmap Review Cadence

Weekly: PM + Engineering lead sync (Now items only)
Monthly: Full team roadmap review (Now + Next)
Quarterly: Exec roadmap review (themes + outcomes)
Annually: Strategic planning (all horizons)

Handling Stakeholder Requests

1. Capture everything in a backlog (never say no immediately)
2. Understand the why: "What outcome are you trying to achieve?"
3. Score transparently using shared criteria
4. Show trade-offs: "Adding X means delaying Y by 6 weeks"
5. Commit to revisit: "We'll review in Q2 planning"

Saying No Professionally

"We've evaluated [feature] and scored it [score] vs our current 
top priorities. To include it, we'd need to deprioritize [X] which 
impacts [metric]. We're committing to revisit in [quarter]. 
I'd love to understand more about the impact so we can improve the score."

Roadmap Communication

For Engineers

• Include technical initiatives (infra, debt, testing)
• Show dependencies explicitly
• Provide 2-week sprint breakdown for NOW items
• Share WHY, not just WHAT

For Sales/CS

• Frame in customer benefits, not features
• Include launch dates only for NOW (±2 weeks)
• Share NEXT as "directional" with caveat
• Never share LATER as committed

For Executives

• Lead with outcomes and metrics
• Show bets and expected returns
• Highlight risks and mitigations
• One page maximum; link to detail

For Customers

• Never share internal roadmaps directly
• Use "we're working on improving X" language
• Reference outcomes, not features
• Provide feedback channels

Roadmap Anti-Patterns

• Feature factory: Shipping features without outcome tracking
• Date theater: Fake precision on uncertain items
• HiPPO-driven: Highest-paid person's opinion overrides data
• Customer-of-one: Building for one enterprise customer
• Shiny object syndrome: Pivoting to trends without evidence
• Overcommitting NOW: >80% capacity in committed work leaves no slack

Quarterly Planning Process

Week -4: Collect input
  - Customer feedback analysis
  - Sales lost deals analysis
  - Support ticket themes
  - Competitor launches
  - Team proposals

Week -3: Score and filter
  - RICE/weighted scoring
  - Capacity planning
  - Dependency mapping

Week -2: Draft roadmap
  - PM creates strawman
  - Engineering reviews feasibility
  - Design reviews design capacity

Week -1: Review and align
  - Exec review
  - Cross-functional review
  - Final adjustments

Week 0: Publish and communicate
  - Internal kickoff
  - Customer-facing version

Roadmap Health Metrics

• % NOW items shipped on time (target: >80%)
• % NEXT items that moved to NOW without major scope change
• % initiatives with measurable outcome defined
• Stakeholder satisfaction score (quarterly survey)