There can be two approaches Approach 1: Impact vs Effort, Urgency vs Importance. Create two matrices, rate each of the features on a scale of 1-10, then map them out on a board. Place them relative to each other and this will help size big projects with big impacts against other Approach 2: Binary scoring. Create a list of questions to answer in such a way that the answers are just 0s or 1s (0-no, 1-yes). Add up the 1s for each feature idea, the one with the highest score wins. Can weigh certain questions higher if you think those questions are more important. Advantage: removes the subjectivity from the exercise. Sample questions could be - - Is feature going to help more than 100 users? - Is feature going to help more than 1000 users? - Is feature going to help more than 10000 users? - Is feature going to take <1 week to build? - Is feature going to take <1 month to build? - Is feature going to take <3 months to build? - Has a senior stakeholder requested this? - Does it tie into company priority? And so on. Important/useful features will automatically bubble up. I found out about the 2nd (binary) framework from a Spotify interviewer on preptick.com, he took my mock interview to help me prepare for my interview. Maybe he's still around on preptick and is willing to give practice sessions...