Academy · 2026-09-20 · 9 min read
Feedback prioritisation: use signal wisely
By Feedlark Team
Key takeaways
- • Feedback prioritisation works best when it is part of a clear loop, not another isolated place for comments to disappear.
- • Make one route obvious, keep the first action small, and give people a visible way to follow what happens next.
- • Votes and repeated reports are useful demand signals, but they need context from customer conversations, strategy and delivery effort.
- • A short weekly review prevents small pieces of feedback becoming an unsearchable pile by the end of the quarter.
Prioritising feedback is where a product team proves it is listening without promising to build everything. That balance is awkward because a vote count feels tidy and a customer story feels urgent. Good prioritisation makes both visible, then adds strategy, effort and timing before a team commits precious delivery capacity.
What feedback prioritisation means in practice
Feedback prioritisation is the practice of deciding which customer problems deserve research, roadmap space or a response now. It is not a formula for choosing every feature. A request with twenty votes may be important, but the score does not reveal whether those voters are in a strategic segment, whether an existing workflow solves the problem, or whether a small fix would remove a much larger source of friction.
Start with the job, not the screen
Before adding feedback prioritisation to a product or website, write down the moment that should trigger it. Is somebody stuck, deciding whether to renew, trying a new feature, or responding to a release? That answer determines the prompt, the right amount of context and where the response should land. A blank box labelled “Feedback” asks people to do the sorting for you. A specific invitation, such as “What stopped you completing this step?”, produces a more useful first sentence and makes triage far less painful.
| Check | A useful default | Warning sign |
|---|---|---|
| First action | One short prompt and a clear submit button | A long form before someone can explain the issue |
| Destination | One queue where the team can search, merge and assign | Comments split between inboxes, chat and spreadsheets |
| Demand signal | People can add a vote or join an existing request | Every similar suggestion starts a fresh thread |
| Follow-through | Reporter can see a status or receives a shipping update | The message disappears after submission |
Separate demand from the decision
Record votes and repeated reports as demand evidence. Next, add a short note on the customer problem, affected segment, business or product goal, confidence and likely delivery effort. Discuss these inputs in a regular planning session rather than only when someone senior remembers a request. A lightweight RICE or ICE score can make assumptions visible, but the important outcome is the conversation around those assumptions, not a false sense of mathematical certainty.
A small operating rhythm that keeps it useful
- Review new feedback prioritisation items on a fixed weekly slot, even when there are only a few. Consistency makes ownership visible.
- Merge genuine duplicates early and keep the clearest title, so demand gathers on one item instead of being split across lookalikes.
- Add a plain status only when it has a clear owner: under review, planned, in progress or shipped are usually enough for customers.
- When an item ships, connect it to a release note and tell the people who asked. That is the bit most teams leave on the cutting-room floor.
“Votes tell you where to look. Context tells you what people are trying to achieve. Strategy tells you whether now is the right time. Prioritisation needs all three, even when the answer is uncomfortable.”
— Feedlark Team
A realistic example
A team saw two requests near the top of its board: SSO and a colour-picker. The colour-picker had more votes, but most came from free users asking for cosmetic control. SSO had fewer votes from larger teams blocked from adopting the product. The team prioritised discovery and delivery for SSO, explained the decision on the board and kept the colour-picker visible. The vote count was honoured as evidence, not obeyed as a command.
The mistake that makes this feel like a black hole
The biggest pitfall is letting a scoring sheet replace human judgment. Teams sometimes give made-up reach and impact values a veneer of precision, then claim the result is objective. Another is losing sight of the underlying problem. Customers may ask for a feature because they cannot complete a task; a different solution can sometimes solve it better and faster.
Make the next step visible
Start with the top ten open requests, not the whole historical backlog. Add source, repeated-demand evidence and a sentence about the job each customer is trying to do. Use the next planning session to make three clear calls: investigate, plan or leave visible but uncommitted. Then publish the status changes so customers see that review led somewhere. Link the collection point to a feature request tracking workflow, then make its priorities visible on a public roadmap. When work is finished, a readable changelog is the final hand-off. These links matter because they show a customer the route their idea takes after they press submit, rather than asking them to trust an invisible internal process.
What good looks like after the first month
After four weeks, feedback prioritisation should leave a clear trail: new input is acknowledged, similar items have been grouped, the highest-signal themes have a decision or an owner, and contributors can see at least one honest update. Do not judge the setup by raw submission volume. Judge it by whether a product teammate can explain the evidence behind a priority and a customer can understand what happened to their idea.
Sources worth keeping nearby
Good feedback collection should be understandable and usable by more than the loudest people in a customer base. The W3C introduction to web accessibility is a sound starting point for accessible controls and clear interaction. For the research side, the GOV.UK Service Manual on user research is a useful reminder to learn from real users in the context of their task. Neither source is a product-management playbook, but both help keep the collection step honest.
Frequently asked questions
- What should a feedback prioritisation process include?
- At minimum, it needs an obvious place to submit or vote, one shared queue, a named review cadence and a way to tell contributors what happened. The tool matters less than those four habits, because each fixes a different point where customer input otherwise gets lost.
- How do I get more useful feedback prioritisation input?
- Ask about the specific task or moment someone has just experienced, rather than asking for general opinions. Let people add context in their own words, then give them the option to vote on an existing item. Specific prompts create better signal without making the form feel like homework.
- Should every request be added to the roadmap?
- No. A roadmap is a commitment to focus, not a public copy of every idea. Keep the request visible, assess its demand and strategic fit, then move only the work you intend to pursue into a clear public status. Saying “under review” is more credible than quietly overpromising.
- How often should a team review feedback?
- Weekly suits most small SaaS teams because it is frequent enough to acknowledge new input before it goes stale without turning into a daily meeting. Higher-volume products may need a short daily pass, but the important thing is that someone owns the cadence and the queue remains searchable.
Feedlark Team. The Feedlark team builds the feedback boards, public roadmaps and changelogs used in the workflows described here.