Roadmap Planner

┌─────────────────┬──────────────────┬──────────────────┐
│      NOW         │      NEXT        │      LATER       │
│  (This Quarter)  │ (Next Quarter)   │   (Future)       │
│  High Confidence │ Medium Confidence│ Low Confidence   │
├─────────────────┼──────────────────┼──────────────────┤
│ ■ Search         │ ○ Personalized   │ ◇ AI-powered     │
│   improvements   │   recommendations│   product search │
│                  │                  │                  │
│ ■ Checkout       │ ○ International  │ ◇ Subscription   │
│   optimization   │   payments       │   commerce       │
│                  │                  │                  │
│ ■ Mobile app     │ ○ Push           │ ◇ AR product     │
│   performance    │   notifications  │   previews       │
├─────────────────┼──────────────────┼──────────────────┤
│ Specific items   │ Themes and       │ Strategic bets   │
│ with acceptance  │ rough scope      │ and explorations │
│ criteria         │                  │                  │
└─────────────────┴──────────────────┴──────────────────┘

┌──────────────────────────────────────────────────────────────────┐
│ OUTCOME: Increase new user activation from 30% to 50%           │
├──────────────────────┬───────────────────┬──────────────────────┤
│ Q1                   │ Q2                │ Q3                   │
├──────────────────────┼───────────────────┼──────────────────────┤
│ Hypothesis: Simpli-  │ Hypothesis: Person│ Hypothesis: Social   │
│ fied onboarding will │ alized welcome    │ features will drive  │
│ increase activation  │ will increase     │ retention post-      │
│ by 10%               │ activation by 5%  │ activation           │
│                      │                   │                      │
│ Key Results:         │ Key Results:      │ Key Results:         │
│ - Time to first      │ - Welcome email   │ - 50% of new users   │
│   value < 3 min      │   CTR > 25%       │   connect with 3+    │
│ - Drop-off at step   │ - In-app guidance │   people in week 1   │
│   2 reduced by 40%   │   completion > 60%│                      │
│                      │                   │                      │
│ Initiatives:         │ Initiatives:      │ Initiatives:         │
│ - Redesign signup    │ - Segment-based   │ - Team invitation    │
│   flow               │   onboarding      │   flow               │
│ - Interactive        │ - Dynamic welcome │ - Activity feed      │
│   tutorial           │   dashboard       │                      │
└──────────────────────┴───────────────────┴──────────────────────┘

┌──────────────────────────────────────────────────────────────┐
│                    PRODUCT ROADMAP 2025                       │
├──────────────┬──────────┬──────────┬──────────┬─────────────┤
│ Theme        │ Q1       │ Q2       │ Q3       │ Q4          │
├──────────────┼──────────┼──────────┼──────────┼─────────────┤
│ Performance  │ ████████ │ ████     │          │             │
│ & Reliability│ DB optim │ CDN      │          │             │
│              │ Caching  │          │          │             │
├──────────────┼──────────┼──────────┼──────────┼─────────────┤
│ Growth &     │          │ ████████ │ ████████ │ ████        │
│ Acquisition  │          │ Referral │ SEO      │ Partnerships│
│              │          │ program  │ optimiz  │             │
├──────────────┼──────────┼──────────┼──────────┼─────────────┤
│ Enterprise   │ ████     │ ████     │ ████████ │ ████████    │
│ Features     │ SSO      │ Audit    │ RBAC     │ Compliance  │
│              │          │ logs     │          │ reporting   │
├──────────────┼──────────┼──────────┼──────────┼─────────────┤
│ Platform &   │ ██       │ ██       │ ██       │ ██          │
│ Tech Debt    │ (ongoing)│ (ongoing)│ (ongoing)│ (ongoing)   │
└──────────────┴──────────┴──────────┴──────────┴─────────────┘

Best used for: Fixed-deadline projects, compliance timelines, migration projects
Avoid for: Feature-based product development (creates false precision)

Jan        Feb        Mar        Apr        May        Jun
|----------|----------|----------|----------|----------|
[=== Phase 1: Foundation ===]
  [DB Migration]
  [API v2 Development]
           [=== Phase 2: Migration ===]
              [Service A Migration]
                       [Service B Migration]
                                 [=== Phase 3: Cutover ===]
                                    [Parallel Run]
                                              [Switch]
                                                      [Decom v1]

1. Technical Dependencies:
   - Service A must be deployed before Service B can integrate
   - Database migration must complete before new features can launch

2. Team Dependencies:
   - Platform team must deliver API before product team can build feature
   - Design must complete mockups before frontend development begins

3. External Dependencies:
   - Third-party API availability
   - Vendor contract negotiations
   - Regulatory approval

4. Data Dependencies:
   - Historical data migration required before new analytics features
   - Training data needed before ML model deployment

┌──────────┐     ┌──────────┐     ┌──────────┐
│ Auth     │────>│ User     │────>│ Team     │
│ Service  │     │ Profile  │     │ Features │
│ (Team A) │     │ (Team A) │     │ (Team B) │
└──────────┘     └──────────┘     └──────────┘
                       │
                       ▼
                 ┌──────────┐
                 │ Notific- │
                 │ ations   │
                 │ (Team C) │
                 └──────────┘

Critical Path: Auth → User Profile → Team Features
Risk: Team B is blocked until Team A delivers User Profile
Mitigation: Define API contract early, allow parallel development with mocks

Score = (Reach x Impact x Confidence) / Effort

Reach: How many users affected per quarter?
Impact: How much will it move the target metric? (3=Massive, 2=High, 1=Medium, 0.5=Low, 0.25=Minimal)
Confidence: How certain are we? (100%=High, 80%=Medium, 50%=Low)
Effort: Person-months of work required

Example:
┌──────────────────────┬───────┬────────┬──────┬────────┬───────┐
│ Initiative           │ Reach │ Impact │ Conf │ Effort │ RICE  │
├──────────────────────┼───────┼────────┼──────┼────────┼───────┤
│ Search improvements  │ 5000  │ 2      │ 80%  │ 3      │ 2667  │
│ Mobile notifications │ 8000  │ 1      │ 80%  │ 2      │ 3200  │
│ AI recommendations   │ 3000  │ 3      │ 50%  │ 6      │  750  │
│ Checkout redesign    │ 10000 │ 2      │ 90%  │ 4      │ 4500  │
└──────────────────────┴───────┴────────┴──────┴────────┴───────┘
Priority: Checkout > Notifications > Search > AI

Define criteria and weights:
- Business Value (30%)
- User Impact (25%)
- Strategic Alignment (20%)
- Technical Feasibility (15%)
- Risk (10%)

Score each initiative 1-10 on each criterion, multiply by weight, sum.

┌────────────────┬───────┬───────┬────────┬─────────┬──────┬───────┐
│ Initiative     │ BizVal│ User  │ Strat  │ Tech    │ Risk │ Total │
│                │ (30%) │ (25%) │ (20%)  │ (15%)   │ (10%)│       │
├────────────────┼───────┼───────┼────────┼─────────┼──────┼───────┤
│ Feature A      │ 8/2.4 │ 7/1.75│ 9/1.8  │ 6/0.9   │ 7/0.7│  7.55 │
│ Feature B      │ 6/1.8 │ 9/2.25│ 5/1.0  │ 8/1.2   │ 8/0.8│  7.05 │
│ Feature C      │ 9/2.7 │ 5/1.25│ 8/1.6  │ 4/0.6   │ 3/0.3│  6.45 │
└────────────────┴───────┴───────┴────────┴─────────┴──────┴───────┘

Cost of Delay = Value of feature per week * Weeks of delay

Use to decide sequencing:
- Feature A: $10K/week value, 4 weeks to build
  Weighted Shortest Job First (WSJF) = 10/4 = 2.5
- Feature B: $20K/week value, 12 weeks to build
  WSJF = 20/12 = 1.67
- Feature C: $5K/week value, 1 week to build
  WSJF = 5/1 = 5.0

Build order: C → A → B (highest WSJF first)

Monthly Cadence:
Week 1: Product team updates roadmap based on new data/learnings
Week 2: Cross-functional review (engineering, design, data)
Week 3: Leadership review and alignment
Week 4: Communicate updates to broader organization

Quarterly Deep Dive:
- Full strategic review of roadmap direction
- Re-evaluate themes and priorities
- Update Now-Next-Later based on quarterly outcomes
- Adjust based on market changes and competitive landscape

┌─────────────────┬────────────────┬─────────────┬───────────────┐
│ Audience        │ Format         │ Frequency   │ Detail Level  │
├─────────────────┼────────────────┼─────────────┼───────────────┤
│ Board/C-Suite   │ Theme-based    │ Quarterly   │ Strategic     │
│                 │ 1-pager        │             │ outcomes only │
├─────────────────┼────────────────┼─────────────┼───────────────┤
│ VP/Directors    │ Outcome-based  │ Monthly     │ Themes +      │
│                 │ roadmap        │             │ key initiatives│
├─────────────────┼────────────────┼─────────────┼───────────────┤
│ Engineering     │ Now-Next-Later │ Bi-weekly   │ Initiatives + │
│ Teams           │ with details   │             │ dependencies  │
├─────────────────┼────────────────┼─────────────┼───────────────┤
│ Sales/CS        │ Feature-focused│ Monthly     │ What's coming │
│                 │ timeline       │             │ + customer    │
│                 │                │             │ impact        │
├─────────────────┼────────────────┼─────────────┼───────────────┤
│ Customers       │ High-level     │ Quarterly   │ Themes only,  │
│                 │ themes         │             │ no dates      │
└─────────────────┴────────────────┴─────────────┴───────────────┘

When a stakeholder asks for a specific feature:

1. Acknowledge: "I understand this is important for [their goal]"
2. Connect to outcomes: "How does this relate to [business outcome]?"
3. Contextualize: "Here's where it fits relative to current priorities"
4. Offer trade-offs: "We can do this if we deprioritize [X]. What do you think?"
5. Document: Record the request and the decision in the roadmap backlog

When leadership demands a fixed date:
1. Provide a range with confidence levels, not a single date
2. List assumptions and risks that could affect the timeline
3. Identify what would need to be true for the earliest date
4. Offer scope flexibility: "We can hit [date] if scope is limited to [subset]"

Pre-work (before workshop):
- Collect input from stakeholders (surveys, interviews)
- Gather data: usage metrics, customer feedback, competitive analysis
- Prepare current state assessment

Workshop Agenda:
1. (30 min) Vision and Strategy Recap
   - Where are we going? Why?
   - What does success look like in 12 months?

2. (45 min) Opportunity Brainstorming
   - What could we build/improve?
   - Organize by theme
   - Include customer requests, tech debt, innovation bets

3. (45 min) Prioritization Exercise
   - Apply RICE or weighted scoring
   - Discuss trade-offs openly
   - Identify the "must dos" vs "nice to haves"

4. (30 min) Dependency and Risk Review
   - Map dependencies between initiatives
   - Identify critical risks
   - Flag external dependencies

5. (30 min) Sequencing and Allocation
   - Place items into Now-Next-Later
   - Allocate team capacity across themes
   - Identify what is explicitly NOT on the roadmap

6. (15 min) Communication Plan
   - Who needs to see this?
   - What format for each audience?
   - When is the next review?