roadmap-planning
Transform strategy into a sequenced, outcome-driven roadmap that aligns stakeholders and guides execution.
- Orchestrates five phases over 1-2 weeks: gather inputs (business goals, customer problems, technical constraints), define epics with hypotheses and success metrics, prioritize using frameworks like RICE, sequence by quarter with dependency mapping, and communicate with strategic narrative
- Emphasizes outcome-driven epics over feature lists, with each initiative tied to business metrics and customer problems rather than disconnected feature requests
- Includes stakeholder alignment throughout—gathering inputs from sales, marketing, CS, and execs upfront, then presenting for feedback rather than solo PM planning
- Provides roadmap templates in Now/Next/Later, quarterly, or theme-based formats; explicitly avoids waterfall thinking by framing roadmaps as strategic plans subject to change based on learning
Purpose
Guide product managers through strategic roadmap planning by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing skills into a structured process. Use this to move from disconnected feature requests to a cohesive, outcome-driven roadmap that aligns stakeholders, sequences work logically, and communicates strategic intent—avoiding "feature factory" roadmaps that lack strategic narrative or customer-centric framing.
This is not a Gantt chart—it's a strategic communication tool that shows what you're building, why it matters, and how it ladders up to business outcomes.
Key Concepts
What is Strategic Roadmap Planning?
Roadmap planning is the process of:
- Gathering inputs — Customer problems, business goals, technical constraints
- Defining initiatives — Epics with clear hypotheses and success metrics
- Prioritizing — Rank initiatives by impact, effort, strategic fit
- Sequencing — Organize into releases/quarters with logical dependencies
- Communicating — Present roadmap to stakeholders with strategic narrative
Types of Roadmaps
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1Kuser-story-mapping
Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.
1.1K