How do you create a product roadmap?

This is an interview question, with a few sub-questions I was able to get after asking them:

  • How would you determine the roadmap for a product? (Assume any product and any feature)
  • What are the key criteria's/aspects you will consider to create this road map?
  • How much weight will your roadmap have for user-driven features?

 

0 votes
295 views

This is an interview question, with a few sub-questions I was able to get after asking them:

  • How would you determine the roadmap for a product? (Assume any product and any feature)
  • What are the key criteria's/aspects you will consider to create this road map?
  • How much weight will your roadmap have for user-driven features?

 

in Strategy by (21 points) | 295 views

2 Answers

0 votes

Before jumping right into creating a roadmap, it is importing to define what problems to solve, who are the customers/users and what high level use cases we are trying to address. If this is a domain-specific problem, then narrow it and apply your knowledge); if no domain it is still important to highlight the importance of understanding customer and job-to-be-done.

 

A roadmap comprises of Objectives and Key Results. To arrive at a set of objectives, one needs to be able to classify the requirements into 3 buckets:

1) business – does the objective generate result that affect such metrics as revenue, churn rate etc. ?

2) customer – does the requirement directly come from customer themselves ?

3) product – does the requirement align with product vision ?

 

The next step is to assign effort in each item so that one can figure out ROI. Attempt to come up with a roadmap that maintains a balance in each of the 3 buckets at any given chunk of execution time frame (3 months if you do quarterly planning). However the key of creating a roadmap is communication – ensuring all stakeholders are aligned or at least understand where you as a product manager came up with the roadmap that you did.

by
0 votes
I would go with the 5-step outcome-based roadmap creation, this should work for any product:

1. Why: Determine why a problem needs solving - should be solved in alignment with business strategy.

2. Who: Determine who are the various stakeholders or user segments.

3. What: For each stakeholder/user group, determine which outcomes you would like to see - Features and KPIs, etc.

4. How: Determine how would you go about achieving each outcome, feasibility, timelines, etc. - Build vs buy, etc.

5. Weather: If the desired outcomes can be achieved by solving the selected pain-points in the chosen way. Data Analysis and other user tests.

Scale and re-iterate for new set of features/requirements.
by
Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
To avoid this verification in future, please log in or register.
Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
To avoid this verification in future, please log in or register.