Roadmap Planning

When to Use

• Building an annual or quarterly roadmap for your team
• Prioritizing competing initiatives when capacity is constrained
• Mapping cross-team dependencies for a planning cycle
• Preparing a roadmap presentation for leadership, stakeholders, or the team
• Re-evaluating priorities mid-cycle due to shifting business needs
• Translating company strategy into team-level initiatives

Roadmap Anatomy

A roadmap is not a feature list. It communicates what the team intends to accomplish, why, and in what sequence — at a level of abstraction appropriate for the audience.

Required Elements

What a Roadmap is NOT

• A Gantt chart with exact dates for every task
• A backlog sorted by priority
• A promise to stakeholders — it's a plan that evolves
• A list of features without outcomes

Planning Process

Step 1: Gather Inputs

Before planning, collect:

1. Company/org OKRs — What is the company betting on this quarter/year?
2. Customer feedback — Top pain points, feature requests, churn reasons
3. Tech debt inventory — What slows the team down? What's fragile?
4. Stakeholder requests — What do product, sales, support, and leadership need?
5. Team retro themes — Recurring process or tooling frustrations
6. Carry-over — Unfinished work from last cycle

Step 2: Generate Candidates

List all potential initiatives. For each, capture:

### Initiative: <Name>

- **Theme**: <which strategic area>
- **Problem**: <what problem does this solve>
- **Outcome**: <what measurable result>
- **Effort**: S / M / L / XL
- **Impact**: High / Medium / Low
- **Confidence**: High / Medium / Low
- **Dependencies**: <list any cross-team dependencies>
- **Requestor**: <who is asking for this>

Step 3: Prioritize

Use a structured framework. Do not priority-sort by gut feeling alone.

RICE Framework (adapted)

RICE Score = (Reach × Impact × Confidence) / Effort

Alternative: Value vs. Effort Matrix

For simpler prioritization, plot initiatives on a 2×2:

        High Value
            │
    DO FIRST│  PLAN CAREFULLY
   (quick   │  (high effort,
    wins)   │   high value)
────────────┼──────────────── Effort →
    FILL    │  AVOID / DEFER
   (low     │  (high effort,
    value,  │   low value)
    easy)   │
        Low Value

Step 4: Allocate Capacity

Split team capacity deliberately:

Document the allocation in your quarterly plan so the team and stakeholders share expectations.

Step 5: Sequence and Commit

Arrange initiatives into time horizons:

• Now (this sprint/month): Actively in progress, fully committed
• Next (this quarter): High confidence, planned but not yet started
• Later (future quarter): Lower confidence, directional

Only items in Now and Next should be broken into epics in your issue tracker. Later stays in the roadmap doc to signal direction.

Roadmap Artifacts

Quarterly Roadmap Brief

Create in your team's shared documentation tool (Confluence, Notion, Google Docs, etc.):

# Q[N] YYYY Roadmap — [Team Name]

## Strategy Alignment
How this quarter's work connects to company OKRs.

## Themes
1. Theme A — why this matters
2. Theme B — why this matters

## Committed Initiatives
| Initiative | Theme | Owner | Outcome | Effort | Dependencies |
|-----------|-------|-------|---------|--------|-------------|
| ... | ... | ... | ... | ... | ... |

## Stretch / Aspirational
Initiatives we'd take on if capacity allows.

## What We're NOT Doing (and Why)
Explicitly list deprioritized requests and the reasoning.

## Risks and Dependencies
| Risk | Mitigation | Owner |
|------|-----------|-------|

## Capacity Allocation
Pie chart or table showing planned split.

Roadmap Presentation (Leadership)

When presenting to leadership:

1. Lead with outcomes, not features — "Reduce onboarding time from 3 days to 3 hours" not "Build self-serve provisioning"
2. Show trade-offs — What you chose NOT to do and why
3. Quantify confidence — Don't present everything as a guarantee
4. Highlight dependencies and risks — Especially cross-team blockers
5. Keep it to one page — Executives skim; make it scannable

Anti-Patterns

Review Cadence