How to Prioritize Feature Requests (Without Letting the Loudest User Win)

Short answer: collect every request in one place, merge duplicates, weigh votes by who is asking, score what is left on impact versus effort, and publish the result on a roadmap so users can see what happened to their idea.

Most teams do not have a shortage of ideas. They have a shortage of a fair, repeatable way to choose between them. Here is a lightweight process that works for teams of one to twenty.

1. Get every request into one place

Requests arrive through support chats, emails, sales calls, reviews and social media. If they live in five places, the loudest channel wins by default.

Give users a single public board to post and vote on ideas, and have your team log requests from other channels on the same board. One list is the precondition for everything else.

2. Merge duplicates and rewrite titles

The same need shows up worded ten different ways. Merge them, and rewrite the surviving title around the problem rather than a specific solution:

• "Add a CSV export button" becomes "Get my data into a spreadsheet"
• "Dark mode" stays "Dark mode" — some requests really are that clear

Problem-shaped titles keep you open to better solutions than the first one suggested.

3. Weigh votes, do not just count them

A raw vote count treats a trial user and your largest customer the same. Before deciding, look at who voted:

• Are they paying customers, or visitors who never converted?
• Do they match the customers you want more of?
• Is the request blocking them from getting value, or a nice-to-have?

4. Score impact against effort

For the shortlist, a simple two-axis score is enough. Rate each item 1–3 on impact and 1–3 on effort:

Impact	Effort	Decision
High	Low	Do next
High	High	Plan it, break it down
Low	Low	Batch as quick wins
Low	High	Park it

Resist adding more columns. The value of the exercise is the conversation it forces, not decimal precision.

5. Close the loop in public

Move the chosen items to Planned, then In progress, then Completed on a public roadmap. Everyone who voted can see progress, and a request that is not planned can be marked as such with a one-line reason.

Closing the loop is what turns feedback into loyalty: users who see their idea shipped become your most vocal fans.

Keep the cadence light

A weekly 20-minute triage (merge, tag, set status) and a monthly prioritisation session are enough. The goal is a roadmap you can explain in one sentence per item — not a perfect model.