Set community norms on day one
Publish a short “how we use this board” note: one idea per post, search before posting, votes are a signal not a contract, and declines get a reason.
Voting rules that keep signal clean
Pick defaults you can defend in public. Change them rarely so customers learn the system.
| Rule | Why it matters | Default |
|---|---|---|
| One vote per person | Stops sockpuppets | Required |
| Search-as-you-type | Kills duplicates early | On |
| Merge aggressively | Concentrates signal | Weekly triage |
| Votes ≠ commitment | Protects strategy | Stated in FAQ |
| Decline with reason | Keeps trust | Public note |
Triage on a cadence
Block 30–60 minutes weekly: merge dupes, tag themes, move winners toward Planned, and decline dead ends. Stale Pending piles train users to ignore you.
- Merge duplicates onto the canonical post
- Tag by product area / plan tier
- Promote clear winners to the roadmap
- Decline politely when out of scope
Pair votes with a framework
Use RICE, ICE, or opportunity scoring beside vote counts. A quiet enterprise request can beat a viral freemium upvote pile.
Close the loop when you ship
Move the card to Done, publish a changelog entry, and email voters. That notification is what keeps people voting next quarter.
Ready to put this into practice?
Open a voting board