How to prioritize a product roadmap?
How to prioritize, that is, how to decide what to do first?
This is a frequent question from every product manager. Whether a new product –that’s is being created now– or a fully operating product –full of suggestions from clients and users–, you should know how to answer it.
Below are seven proven techniques to help you answer it, and prioritize a product roadmap:
- Value versus cost
- Kano Model Analysis
- Feature Sequencer
- Product tree
- Buy your features
- The one you remember first
1. Value versus cost
One of the simpler ways of prioritizing a roadmap is making an analysis of all items, seeking for estimating: the value (benefit) of each one for the business and for the users, and the cost of implementing each item. With these data on your hands, it is possible to even build a graph with two axes and put each and every one of the items in it based on the value and on the cost. The idea is to always prioritize what has the bigger value and lower cost, for the benefit will be obtained more quickly.
2. Kano Model Analysis
Kano Model was created by professor Noriaki Kano, from Tokyo University, to classify the items of a product based also in two dimensions, the need of an item and the excitement that it provides to clients. With this, it is possible to classify the items in three types: basic; satisfier and delighters.
For instance, in a car, the wheel is a basic item, for there is no car without wheels. Sunroof is a satisfier item, if your client does not consider it valuable. Being very silent is an item that delights a client that appreciates it. The recommendation is to have all basic items, some satisfiers, but do not leave some delighters out if you want to positively impress your client.
3. Feature Sequencer
Feature Sequencer was created to plan a product based on deliverables, and its features. The sequencer rules –such as three cards per line– foster the prioritization conversation.
According to the Lean Inception book, the Feature Sequencer helps you organize and visualize the features and its relation to the deliverables. The sequencer organizes and plans the product releases beyond the first deliverable. Typically, teams using the feature sequencer will dazzle the product evolution via a clear understanding on the features contained by each deliverable, and the release order.
The previous image has a sample feature sequencer; each feature is represented by an index card. The post-its on the right hand side represent the deliverables.
4. Product tree
The idea is kind of like the Kano analysis: classifying items of the roadmap according to the parts of a tree. Roots are the infrastructure; the stalk provides support; the branches are the different paths in which you can put your product in; the leaves are the features themselves; and the flowers and the fruits are the features that are going to delight the customer. Every product has to have roots, stalk and some branches with their respective leaves, but it’s important to always add on some flowers and fruits in order to make your product delightful.
5. Buy your features
In this technique, you make everyone play a game. You show all the items in your roadmap and set a value for each one based on how is going to cost to build it. Then, invite some clients and tell them they have X to spend. This X must be substantially less than the sum of the value of all your items.
With this X, each client has to “buy” the most important features and, as the money is limited, everyone is forced to make choices such as “Do I take these two features or trade them for this more expensive one?”. It is a very interesting exercise and provides a good knowledge on client behavior.
UserVoice is a suggestion system that you can put in your product. With this, your user will be able to make suggestions about it, and will also be able to vote for suggestions from other users. You can still limit the amount of votes, forcing them to make choices, like in the previous method.
7. The one you remember first
Jason Fried, founder of 37signals – currently called Basecamp, said on his book Getting Real that in his company the option was to prioritize based on remembrance. They receive several suggestions everyday, and simply decided not to write them down so they won’t spend time counting and classifying them.
As suggestions come up everyday, they hear them everyday. From time to time, they get together and discuss about the suggestions they remember, and these are the ones that are approached and eventually prioritized in the products roadmap.
So, what is the best prioritization technique?
As you can see, there are many ways of prioritizing a roadmap, all very useful. In other words, what we can conclude is: prioritizing a roadmap is not an exact science.
Despite of the presented roadmap prioritization techniques, the best method is the product manager voice. That is, the ability the product managers have of analyzing the available options and, using their empathy, they prioritize these options taking into account the company’s goals and the users´ needs.