Guide
How to prioritize feature requests without guessing
Updated 2026-11-02 · 6 min read
Short answerTo prioritize feature requests, group duplicates into themes, count and weigh who is asking (by revenue, segment or churn risk, not votes alone), estimate effort, pick what moves your goals, and tell requesters what you decided. Votes inform the decision; they do not make it.
Votes are a signal, not a verdict#
Counting votes is a good start and a bad finish. Votes favour popular, easy-to-describe ideas, and every voter counts the same whether they pay thousands a month or nothing. Use votes to find candidates, then add context.
A five-step process#
1. Collect in one place#
Requests arrive by email, chat, calls and a board. Pull them into one list so you can see them together. Capture who asked and in what words.
2. Merge duplicates and group themes#
"Dark mode", "night theme" and "reduce eye strain" are one request. Merge duplicates so votes add up, then group related requests into themes. Three hundred requests are often a dozen needs.
3. Weigh who is asking#
Add what you know about each voter:
- Revenue. Thirty-eight votes carrying $4,200 a month is a different signal from thirty-eight free-plan votes.
- Segment. Is the person in the customer group you are trying to win?
- Risk. Are the people asking at risk of leaving, and is this the reason?
4. Score value against effort#
A simple pass is enough: value (how many of your people, how badly, how well it fits the product's direction) over effort (days, risk, dependencies). Do cheap, high-value items first. Be suspicious of expensive items with a few loud voters.
5. Decide, and say what you decided#
Move each request to a status: planned, in progress, shipped or not planned. "Not planned, because it does not fit our direction" is a respectful answer; silence is not.
Keep the loop closed#
When a request ships, tell the people who asked. It is the cheapest retention you will ever buy. See closing the feedback loop.
Common mistakes#
- Ranking by votes alone.
- Treating the loudest customer as the market.
- Never saying no.
- Building what was asked rather than the need behind it. Ask "what are you trying to do?"
How Shipnoted helps#
Shipnoted's feedback board catches duplicates while people type, lets your app send each voter's plan and revenue so you can sort by money, groups requests into themes with what is rising, and sends a weekly digest. The decision is still yours.
Questions and answers
- How do you prioritize feature requests?
- Collect them in one place, merge duplicates, group them into themes, weigh who is asking, score value against effort, then decide and tell people the outcome.
- Should I prioritize by number of votes?
- Votes are a useful signal but should not be the only one. Weigh voters by revenue, segment and risk, and balance against effort and product direction.
- How do I handle duplicate feature requests?
- Merge them so votes combine, and suggest existing requests to people while they type so they vote instead of posting a duplicate.
- What should I do with requests I will not build?
- Mark them not planned and say why in a sentence. A clear no is better for customers than silence.
- How do I tell customers a feature shipped?
- Link the request to the release and email the people who asked once the release is published.