Roadmap Builder

Overview

The Roadmap Builder skill enables product managers to create clear, actionable product roadmaps that communicate strategy, align stakeholders, and guide execution. It combines prioritization frameworks, timeline planning, and dependency mapping.

When to Use This Skill

• Planning quarterly or annual product strategy
• Communicating product vision to stakeholders
• Prioritizing features and initiatives
• Managing dependencies across teams
• Aligning engineering, design, marketing resources
• Creating investor/executive presentations
• Managing stakeholder expectations

Roadmap Planning Framework

Roadmap Horizon Definitions

Immediate (Current Quarter - 0-12 weeks)

• Confirmed features with clear specifications
• Active development or about to start
• High confidence in timeline and scope
• Team committed to delivery
• Detail level: Very high (stories, tasks, owners)

Near-term (Quarters 2-3 - 3-6 months)

• Features with strong business case and customer demand
• Good understanding of requirements
• Medium confidence in timeline
• Provisional team allocation
• Detail level: High (features, rough effort estimates)

Medium-term (Quarters 4-5 - 6-9 months)

• Strategic initiatives aligned with roadmap
• Directional roadmap visibility
• Lower confidence due to market changes
• Broad theme-based planning
• Detail level: Medium (themes, business outcomes)

Long-term (6-12+ months)

• Vision and strategic directions
• Subject to significant change
• Focus on outcomes not features
• Annual planning context
• Detail level: Low (goals and themes)

Roadmap Themes Framework

Theme 1: Platform Performance

• Objective: Improve system speed and reliability
• Outcomes: Reduce page load by 40%, achieve 99.99% uptime
• Key features: Caching layer, database optimization, CDN expansion
• Estimated effort: 16 person-weeks

Theme 2: AI/ML Integration

• Objective: Enable intelligent automation of workflows
• Outcomes: 50% reduction in manual data entry, 35% productivity gain
• Key features: Automated categorization, smart recommendations, predictive analysis
• Estimated effort: 24 person-weeks

Theme 3: Enterprise Compliance

• Objective: Meet security and regulatory requirements
• Outcomes: SOC2 certification, ISO 27001 compliance
• Key features: SSO integration, audit logs, data residency options
• Estimated effort: 12 person-weeks

Theme 4: Developer Experience

• Objective: Make product more accessible to developers
• Outcomes: 500 API integrations, 100 third-party apps
• Key features: Comprehensive API docs, webhooks, SDK libraries
• Estimated effort: 20 person-weeks

Quarterly Roadmap Template

Q2 2024 Roadmap

Themes: [3-4 primary themes] Team Capacity: [X person-weeks available] Business Goals: [2-3 key outcomes]

Theme 1: Collaboration Features (8 person-weeks)

• Real-time co-editing

  • Status: In Progress
  • Owner: [Engineering lead]
  • Target completion: Week 6
  • Success metric: 60% of new projects use feature

• Activity feeds

  • Status: Planned
  • Owner: [Engineering lead]
  • Target completion: Week 10
  • Success metric: 40% of users weekly active

• Notification system

  • Status: Planned
  • Owner: [Engineering lead]
  • Target completion: Week 12
  • Success metric: 35% of delivered notifications opened

Theme 2: Mobile Expansion (6 person-weeks)

• iOS app redesign

  • Status: Planned
  • Owner: [Mobile lead]
  • Target completion: Week 8
  • Success metric: 4.5+ star rating

• Android feature parity

  • Status: Planned
  • Owner: [Mobile lead]
  • Target completion: Week 10
  • Success metric: 2K weekly active users

Theme 3: Data & Analytics (4 person-weeks)

• Advanced reporting

  • Status: Planned
  • Owner: [Data lead]
  • Target completion: Week 9
  • Success metric: 20% of projects using reports

• Usage analytics dashboard

  • Status: Planned
  • Owner: [Data lead]
  • Target completion: Week 11
  • Success metric: 30% of teams accessing analytics weekly

Unscheduled Capacity: 2 person-weeks (bug fixes, tech debt)

Feature Prioritization

Prioritization Matrix: Impact vs. Effort

         High Impact
              ↑
              │    [Quick Wins]    [Major Projects]
              │    Do first!       Plan carefully
              │
Effort ←──────●────────→
              │
              │   [Fill-ins]       [Avoid]
              │   Low priority     Deprioritize
              ↓
         Low Impact

Quadrant Placement:

Quick Wins (High impact, Low effort)

• Notification settings customization
• Dark mode support
• Search improvements
• Example: Real-time notifications (4 weeks, high user demand)

Major Projects (High impact, High effort)

• AI-powered recommendations
• Mobile app redesign
• Enterprise SSO integration
• Example: Real-time co-editing (12 weeks, strategic differentiator)

Fill-Ins (Low impact, Low effort)

• UI polish improvements
• Minor feature enhancements
• Bug fixes and technical debt
• Example: Additional export formats (2 weeks, low demand)

Avoid (Low impact, High effort)

• Requested but rarely used features
• Technical solutions to minor problems
• Complex integrations with low user count
• Example: Exotic compliance requirement with 2 users (10 weeks, rare need)

RICE Prioritization Application

Feature 1: Real-time Co-editing

• Reach: 5,000 users (potential monthly)
• Impact: 3x (massive workflow improvement)
• Confidence: 90% (strong customer data)
• Effort: 12 weeks
• RICE Score = (5000 × 3 × 0.9) / 12 = 1,125

Feature 2: Mobile App Redesign

• Reach: 3,000 users (monthly mobile users)
• Impact: 2x (improved experience)
• Confidence: 80% (user feedback + analytics)
• Effort: 10 weeks
• RICE Score = (3000 × 2 × 0.8) / 10 = 480

Feature 3: Dark Mode

• Reach: 6,000 users (many would use)
• Impact: 1x (nice to have)
• Confidence: 75% (requested feature)
• Effort: 3 weeks
• RICE Score = (6000 × 1 × 0.75) / 3 = 1,500

Prioritized Ranking: Dark Mode (1,500) > Real-time Co-editing (1,125) > Mobile Redesign (480)

Dependency Mapping

Dependency Types

Technical Dependencies (Feature A requires Feature B)

• Example: Real-time co-editing requires WebSocket infrastructure
• Impact: Cannot ship feature until dependency complete
• Planning: Build in sequence, allocate effort for both

Data Dependencies (Feature requires data or infrastructure)

• Example: Analytics dashboard requires data warehouse implementation
• Impact: Delays feature if data work behind schedule
• Planning: Start data work early, plan parallel streams

Organizational Dependencies (Cross-team coordination)

• Example: Mobile redesign requires design system alignment
• Impact: Requires coordination, possible schedule conflicts
• Planning: Plan kick-off together, regular syncs

External Dependencies (Third-party or customer)

• Example: Enterprise SSO requires customer IT approval
• Impact: Out of control, high risk
• Planning: Start early, have backup plans

Dependency Map Example

┌─────────────────────────────────────────────────┐
│         WebSocket Infrastructure (4w)           │
│              [Q2, Weeks 1-4]                    │
└──────────────────┬──────────────────────────────┘
                   │ Required by
    ┌──────────────┴──────────────┐
    │                             │
    v                             v
Real-time Updates (3w)    Co-editing Engine (6w)
[Q2, Weeks 5-7]           [Q2, Weeks 5-10]
    │                             │
    └──────────┬───────────────────┘
               v
        Activity Feed (2w)
       [Q2, Weeks 11-12]

Critical Path Analysis

Critical Path: Longest sequence of dependent activities

WebSocket (4w) → Co-editing Engine (6w) → Activity Feed (2w) = 12 weeks

Non-critical path:
WebSocket (4w) → Real-time Updates (3w) = 7 weeks (5-week float)

Project completion: 12 weeks minimum

**Implic