information they need (and why) • Present OKRs, potential solutions at play, and projected numbers • Present your strategy (roadmap) + your execution plans (release plan)
- all products need a strategy! • Hardware = Waterfall (has an ‘end’ date for delivery) • Software = Continuous development and learning. Hardware vs Software - How are they different? It’s important to remember that just because a team is working in a waterfall/hardware product, it doesn’t mean they don’t need a strategic roadmap.
• Outcome-focused roadmaps help improve communication with customers • Soft launch vs Hard launch - not everything needs to be promoted the day it goes live What about coordinating with customer-facing teams?
vision (usually set by C-levels/heads of departments) Cost of delay on initiatives (based on discovery) Opport solution tree to look at solutions → outcome THEN you use framework to frame the conversation around the discovery you’ve done How do you prioritize the roadmap? Discovery first, framework later.
to, related to, duplicate of • Use emoji, tags, or linking feature • Use filters to narrow down view How do you show dependencies on an outcome-based roadmap?