Picking the right prioritisation techniques for your product and team
The impact matters much more than any particular list of features or enhancements.
Hi dearies, Iqmat’s here again…
Prioritisation techniques are not one-size-fits-all, there exist hundreds if not thousands of technique that has been developed by different people at different point in time based on their burning need that the other techniques weren’t 100% suitable.
However, there is really no such thing as “right” techniques as each technique is unique in its own way and look at prioritisation from different perspective. It all depends on your objective, outcome intended and the need of your team.
It is highly recommended to make use of two to three prioritisation technique as this help to weigh your decision from different perspective and reduce bias as much as possible. Regardless, it is important to be consistent with particular types of prioritisation used in your team as this gives you a standard way of measuring initiatives, your initiatives are measured from a single source of truth because all initiative are measured using the same evaluation.
If you already have a technique used within your team, it will be nice to maintain it but if you don’t it will be nice to pick a technique best suitable to your need and be consistent with it.
Without further ado, let’s discuss some prioritisation techniques that you can consider for your initiative. I won’t be listing all the techniques available in the world in this newsletter, but I will site some of my favourites and group them into categories for easier understanding of the different perspective each operate from.
Initiatives ranking or scoring system focus on how the initiative provide value numerically e.g RICE scoring Model
Customer satisfaction technique focus on how the initiative can satisfy customer e.g Kano Model
Customer goal technique focus on what users are trying to achieve e.g Job-to-be-done Model
Time frame prioritisation technique focus on functionalities and when it will likely be developed e.g MoSCoW model. These technique can be easily manipulated and faulted because it can easily focus on budget, company’s need or team bias to make this prioritisation.
Other popular prioritisation techniques include:
Design thinking
Weighted scoring
Value vs complexity
Feature drive development
Prioritisation techniques are a good way to streamline product roadmap however we need to remember that it all comes down to impact. Any technique chosen should be aimed at helping you evaluate every potential idea, how it impact your users, impacts your product strategy and impact the company at large.
After all, the impact matters much more than any particular list of features or enhancements.
Book recommendation: Your next five moves by Patrick Bet-David with Greg Dinkin
I guess you enjoyed your read, Don’t forget to like, comment and share.