The Science of Ranking Features

As a product manager or designer, when it comes to building a website, an app, or any product for that matter, it could be really difficult to establish the features you want to build first and define a roadmap.

Recently, I came up with a small process that I use in my own projects to attribute scores on defined features in order to rank them and maximise productivity.

Please, let me know if you have any idea to improve this method.

Transcript

1. The Science of Ranking Features Product managers, here’s a homemade process to build features that work for your audience.
2. Defining and ranking features lead to anger, anger leads to hate, hate leads to suffering.
3. « That killer-feature-we-are- working-on-for-8-months HAS to be built. Because it’s cool. »
4. This is bad and you should feel bad.
5. The path to success is a two factor formula…
6. Time…
7. …And user needs.
8. Speaking of user needs, do you know the Kano Model ?
10. 4 Principles • Un : User need score from 0 to 10 • t : time factor (1, 2, etc. but no 0.5) • Final score will be defined by Un/t • The closer to 0, the less important
11. Defining Un Feedback is essential. I counts for 5 points out of 5.
12. Defining Un - Combo coeficients • “Must Be” = 2. • “Delighter” = 1. • “Perfomance” = 1.5.
13. Let’s put it to practice now.
14. Consider a Facebook Login feature.
15. My users rated it 2.5/5.
16. We considered it as a performance attribute.
17. Therefore, Un = 2.5*1.5 = 3.75.
18. Now, let’s say we can built it properly in 2 hours.
19. The feature get the final score of 3.75/2 = 1.875
20. There you have a simple, light process to organize your feature.
21. The Science of Ranking Features This article was originally built on Medium : http:// medium.com/p/613f89d2c6b6
22. Gilles Bertaux http://gillesbertaux.com @Gilles_Bertaux About the author
23. Font : Myriad Pro Images: Breaking Bad, Star Wars, A Serious Man, Basic Instinct, Hunger Games, The Time Machine, Seven Samurais. Credits