How feature voting boards work and how to use one well
A feature voting board is a public or shared list of requested improvements where users add ideas and vote on the ones they want. It helps a small product team see demand in one place. It does not make decisions for you, and treating it as if it does causes problems.
The basic idea
Instead of requests arriving scattered across email, chat and support tickets, users post them in one place. Others can add a vote or a comment instead of posting a duplicate. The team sees which requests come up most and can reply publicly with a status such as “under review”, “planned”, “in progress”, “done” or “not planned”.
Setting one up without special software
A small team can run a board with tools it already has:
- Create a shared spreadsheet with columns for the idea, who asked, the problem behind it, votes, status and a public reply.
- Collect requests through a simple form so people describe the problem, not just the solution.
- Merge duplicates weekly and add their votes together.
- Publish a read-only view or a simple page listing ideas and their status.
- Update statuses whenever a decision is made, and tell the people who voted.
Dedicated board tools exist and add features such as voter accounts and email notices, but the process matters more than the tool.
Votes are a signal, not a ranking
Raw vote counts favour ideas that are easy to understand and that early or loud users want. They hide the cost of building each one. A simple way to balance them is to divide votes by an effort estimate.
Worked example (made-up numbers). Effort is scored from 1 (a day or two) to 5 (several weeks).
| Idea | Votes | Effort | Votes ÷ effort |
|---|---|---|---|
| A: Export to spreadsheet | 42 | 3 | 14.0 |
| B: Dark mode | 18 | 1 | 18.0 |
| C: Team accounts | 30 | 5 | 6.0 |
Ranked by votes alone, A comes first. Ranked by votes per unit of effort, B comes first and C last. Neither ranking is the answer; both are inputs to a judgement.
Questions to ask before building the top idea
- Who voted? Paying customers, trial users and casual visitors may want different things.
- What problem is behind the request? Talk to a few voters. The best fix may differ from what they asked for.
- Does it fit where the product is going?
- Will it make the product harder to use for everyone else?
Communicating decisions
The fastest way to make a board useless is to leave ideas sitting for months with no reply. Mark ideas you will not build as “not planned” with a short, respectful reason. People usually accept a clear no better than silence. When something ships, mark it done and note it in your changelog.
Common mistakes
- Promising to build anything that reaches a vote threshold.
- Letting the board become the only channel, so quieter users are never heard.
- Counting staff votes alongside customer votes.
- Ignoring the comments, which often hold more insight than the votes.
Questions people ask
Should the board be public?
Public boards show openness and cut duplicates, but they also set expectations in public. If you are not ready to reply to every idea, start with a private list.
Can people vote more than once?
In a spreadsheet setup it is hard to prevent. That is one more reason to treat votes as a rough signal and talk to users directly.