What’s Your Roadmap?
summary
A roadmap is not a release plan or Gantt chart but a strategy prototype built from five concrete parts: vision, objectives, timeframes, themes, disclaimer. Teams dump ideas into a single repo (example uses Zendesk), group by theme, score by value ÷ effort (add confidence, t‑shirt sizing) and prioritize into now/next/later and discovery vs delivery lanes with statuses like discover, ship, tweak. Public examples: Buffer and GitHub; the approach prevents wasted builds and aligns outcomes, not outputs.
AI-written summary · about
chapters (12)
- 0:00Introduction and roadmap struggles
- 3:55History of waste in development
- 9:15Lean, agile and product thinking
- 12:22Problem-solving vs feature-building
- 14:05What is product really?
- 16:32Roadmap components and vision
- 20:44Themes and hypotheses in roadmaps
- 23:56Discovery vs delivery
- 24:59Prioritizing roadmap items
- 27:27Roadmaps vs release plans
- 28:50Outcomes over outputs
- 30:13Activity vs outcome challenge
related talks
10mHow to Build a Robust Product Roadmap
50mDesign roadmaps for success
51mExperience Roadmaps
31mEverything's Coming Up Dilbert: Building Product in the Enterprise - Emily Tate
31mFrom funding to delivery: ensuring alignment from start to finish
25mWhy Designers & Developers Need a Common Language
41mMapping Experiences: From Insight To Action
41mLearning faster