roadmapping

name	roadmapping
description	Plan software product or feature roadmaps using milestones, sequencing, release phases, dependencies, risks, and learning goals. Use when creating a high-level execution path.

Purpose

This skill helps sequence product or feature work into a coherent execution path across milestones, phases, or releases.

Use this skill when:

• Planning milestones
• Sequencing project phases
• Creating release plans
• Turning strategy into delivery phases
• Coordinating cross-functional workstreams
• Communicating a high-level execution path

Inputs

Expected inputs:

• Goals
• Scope boundaries
• Prioritized work
• Milestones
• Constraints
• Dependencies
• Target dates
• Known risks

Inputs usually come from goal-setting, scoping, and prioritization. If sequencing depends on unknown blockers or effort, use dependency-analysis and estimation to refine the roadmap.

Roadmapping Principles

Always optimize for:

1. Delivering value in coherent increments
2. Sequencing learning before large commitments
3. Exposing dependencies early
4. Maintaining realistic milestones
5. Preserving room for adaptation

Avoid optimizing solely for:

• Date-driven promises
• Feature volume
• Cosmetic milestones
• Perfect certainty
• Roadmaps that hide risk

Process

Step 1: Clarify Planning Horizon

Determine:

• Roadmap timeframe
• Target audience
• Primary goals
• Release constraints
• Required decision points

Flag requests that mix strategic roadmap planning with detailed sprint planning.

---

Step 2: Group Work into Milestones

Organize work by:

• User value
• Technical foundation
• Risk reduction
• Learning sequence
• Release readiness

Milestones should have clear outcomes, not just task bundles.

---

Step 3: Sequence Phases

Evaluate:

Factor	Questions
Dependency	What must happen first?
Risk	What should be learned early?
Value	What delivers user or business benefit soonest?
Capacity	Can the team realistically execute this phase?
Releaseability	Can this milestone be shipped or reviewed?

Prefer sequencing that creates usable checkpoints.

---

Step 4: Identify Review Gates

Define:

• Milestone acceptance criteria
• Launch or release gates
• Validation checkpoints
• Replanning triggers
• Open assumptions

---

Step 5: Produce Roadmap

Generate:

• Roadmap phases
• Milestone outcomes
• Key dependencies
• Risks and assumptions
• Recommended next actions

Anti-Patterns

Avoid:

• Treating a roadmap as a fixed contract
• Planning implementation details too early
• Hiding dependency risk
• Making every milestone the same size
• Delaying all user value until the end
• Ignoring validation or feedback loops

Reviewer Checklist

Before finalizing a roadmap:

• Does each milestone have a purpose?
• Are dependencies visible?
• Are risks addressed early enough?
• Is the plan realistic for capacity?
• Can architecture, decomposition, and scheduling use the roadmap?

Escalation Guidance

Escalate when:

• Dates are impossible
• Scope and timeline conflict
• Dependencies are owned by unavailable teams
• Milestones lack measurable outcomes
• The roadmap requires unresolved strategic decisions

Example

Input:

• MVP onboarding checklist
• Goal: Reduce onboarding tickets by 25%
• Constraint: Ship initial version this quarter

Expected roadmap:

1. Phase 1: Checklist foundation and setup state
2. Phase 2: Admin visibility and analytics
3. Phase 3: Optimization based on support ticket trends

Recommended next skill:

• Use architecture for system design or decomposition for executable work items.