A strategy for your product is not enough, you need to prioritise the sequence of actions for the execution to bring ideas to action. This sequence is also called product roadmap. šŗ
This post covers risk-based framework. Risks are the problems and assumptions that might make your product fail. š
š” The benefit of this framework is that if you test whether you can find a solution to those risks early, you can save time and money. Therefore it is important to make an assessment after every milestone in the roadmap. The assessment can result in 3 types of decisions: continue, pivot, stop development.
Here is an example of a roadmap (list of prioritised milestones) for a product I worked with before:
1ļøā£ Customer interviews (Risk 1: do customers really need a new solution?)
2ļøā£ Technical spike (Risk 2: is it technically feasible to build this product?)
3ļøā£ Onboarding two customers( Risk 3: Scalability: can the platform scale beyond the design customer?)
4ļøā£ Fine tuning and measuring value (Risk 4: Return on investment: it is worth to have this product up and running?)
š£ Share in the comments: What frameworks do you use to go from strategy to roadmap?š£
Commentaires