Feature prioritisation
Also known as Feature prioritization, Prioritising feature requests
Feature prioritisation is deciding which product changes to build first, by weighing how many customers a problem affects and how badly against what it would cost to solve.
How do you prioritise feature requests?
Group requests by the problem behind them rather than the solution customers asked for, count how many different customers raised each problem, weigh that against the cost, and say no to most of them out loud. Sorting by how loudly something was asked for hands the roadmap to your most vocal customers.
What frameworks are used for feature prioritisation?
Common ones include RICE (reach, impact, confidence, effort), MoSCoW (must, should, could, won't), the Kano model and simple value versus effort grids. They all help, as long as the inputs come from real evidence rather than guesses made in a planning meeting.
What is the biggest mistake in feature prioritisation?
Counting requests instead of customers. One customer who asks every week is one customer. Votes have a similar problem: they measure who turned up to vote, not who is held back by the problem.
Feature prioritisation, in brief
- What is feature prioritisation?
- Feature prioritisation is deciding which product changes to build first, by weighing how many customers a problem affects and how badly against what it would cost to solve.
- Who should own feature prioritisation?
- Usually the product manager or founder, with input from sales, support and engineering. Whoever owns it should be able to point to the evidence behind each decision.
Put the theory to work.
Corha turns your calls, tickets and surveys into one evidence-backed picture of your customers, so these ideas become part of how your team works, not just definitions.
Try it with your own website, no account. We read the public page and keep nothing.