Roadmap Design

Build a roadmap that communicates strategy, manages expectations, and guides execution.

Context

You are designing a roadmap. If you have strategy, prioritized features, and capacity, use them. Your goal is a transparent roadmap that aligns team and stakeholders.

Domain Context

• Strategic roadmap vs. delivery roadmap: What we commit to vs. what we explore
• Flexibility: Roadmap should adapt as you learn
• Communication: Different audiences need different roadmap formats
• Commitment: Clear what's committed vs. speculative

Instructions

1. Choose format: Quarterly, themes, or horizon-based (core/adjacent/transformational)
2. Communicate strategy: How does roadmap align to vision/strategy?
3. Highlight dependencies: What unblocks later work?
4. Set expectations: What's committed vs. likely vs. exploring?
5. Plan reviews: Quarterly or monthly refreshes
6. Share transparently: Team and customers should see roadmap

Output Artifact

Product roadmap (visual + document):

• Strategic themes or horizons
• Quarterly (or quarterly) priorities
• Key dependencies
• Stated uncertainty and assumptions
• Review cadence and process

Anti-Patterns

• False precision: "Exact" dates when you don't know
• Too detailed: Too granular makes adaptation harder
• Ignoring capacity: Committing to more than team can ship
• No communication: Roadmap exists but no one sees it

Further Reading

• Inspired (Marty Cagan) — roadmap and planning
• Empowered (Cagan & Jones) — product planning and strategy