The Product Side
Product manager interview assignment — Part 4, think beyond the MVP
Show how the MVP can evolve through a high level roadmap and a featuremap.
This post is part of a series demonstrating ansers to a real interview assignments. This one is for a product manager position at Blueground. The assignment sums up to:
Step #1: Present one or more ideas to help Blueground and explain your reason for choosing them.
Step #2: Define the MVP and how to evaluate its success.
Step #3: Describe how the MVP can evolve, give a roadmap.
Let’s see how to answer step #3.
After stage S3 of Part 3, we have validated that customers will sign up for the premium services and Blueground will start earning some referral revenue. However, we have not yet covered the business need to increase the rent (see list item 2.2 in Part 3); for that we need to improve the service and provide a premium experience, so we create the following high-level roadmap for the next 12 months.
Q1: Seamless signup to a service provider
Q2: User orders a service from inside the Blueground app
Q3: User can rate a service
Q4: Blueground app predicts customer needs
This roadmap will certainly involve lots of features, and a full-fledged analysis is out of the scope of this assignment. However, I prepared the feature map below in order to showcase the various actors we need to have in mind (customer, internal users, external providers, etc.) and the most important features we will develop in each quarter.
To keep things simpler, I only examine customer interactions via the Blueground mobile app and not via the website.
So this concludes my answer to this product manager interview assignment.
Thank you very much for reading this far and please share your thoughts!
