many ways it is not different - all products need a strategy! • Hardware = Waterfall (has an ‘end’ date for delivery) • Software = Continuous development and learning. 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.
to communicate the 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
that align with the product/company vision (usually set by C-levels/heads of departments) 2. Cost of delay on initiatives (based on discovery) 3. Opport solution tree to look at solutions -> outcome 4. THEN you use framework to frame the conversation around the discovery you’ve done Discovery first, framework later.
really no easy answer to this one. • How well do you know your team? • How well do you know the industry? • How well do you know the product? • Who are you having the framing conversation with?