top of page

👉 Product deep dive: Convert product strategy to a product roadmap using risk based framework.

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?🗣

0 views0 comments

Recent Posts

See All

Importance of sharing regular project updates

🏃‍♀️ Are you waiting for the end of the project to share an update? 🏃‍♀️ Wait no more, there are lots of benefits on sharing updates on the progress and results even while you are still working on t

Imagine how success looks like

Have you ever found yourself crossing finish line of a project and realising that you have not achieved what you wanted? There is one thing that you can do to ensure better outcomes of any goal that y


bottom of page