What is a feature voting board? Definition and examples
A public or private page where customers post feature ideas and vote on the ones they want most.
Feature voting board: A public or private page where customers post feature ideas and vote on the ones they want most.
Voting boards make demand visible and let customers see what others asked for. Tools like Canny and Featurebase are built around them.
They work best with large, engaged communities. Small or B2B products often prefer private requests, where customers don’t see each other’s ideas.
Example
| Pros | Cons |
|---|---|
| Demand is visible | Old ideas pile up unanswered |
| Customers feel heard | Votes favour the loudest users |
When a voting board works
- You have many active users who return to the board.
- Your roadmap is public, or you are happy for it to be.
- Someone on the team can answer and close old ideas every week.
When private requests work better
- B2B products where customers shouldn’t see each other’s needs.
- Small user bases, where a board with three votes per idea looks empty.
- Requests that come with context from inside the product, such as the screen someone was on.
Avoid the graveyard
Boards fill with ideas nobody has answered. Set a status on every idea within a week, merge duplicates, and close ideas you won’t build with a short reason. A board with honest “not planned” answers earns more trust than one where everything is “under review”.
Where Bopmigo fits
Bopmigo collects and groups requests privately, without a public board.
Questions
Are votes a good way to prioritize?
They’re one signal. Weigh who is asking and why, not just the count.
Can I have both a board and private feedback?
Yes. Many teams collect privately in the product and publish only the ideas they have decided to build.
Do votes reflect revenue?
Not by themselves. Weight votes by who cast them if paying customers matter more to a decision.