Feature Request Voting Board

A voting board customers trust: the right tool and visibility, honest status labels, weekly moderation and merging, closing the loop with voters, saying no well and reading votes without being fooled by them.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Feature Request Voting Board, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

203

Starter tasks

🧩 Product Management

Feature Request Voting Board

Running a public or customer-facing board where users suggest and vote on ideas, with honest status updates on what will and will not happen.

  1. Board purpose and scope statement
  2. Choosing a feature voting board tool
  3. Public, private or customer-only visibility decision
  4. Idea categories and board structure
  5. Status labels with honest definitions
  6. Posting guidelines and community rules
  7. Seeding the board with existing requests
  8. Voter sign-in and personal data set-up
  9. Board ideas linked to the issue tracker and CRM
  10. Named board owner and response time promise
  11. Monday moderation and reply routine
  12. Monthly duplicate merge sweep
  13. Status updates on the top-voted ideas
  14. Shipped idea notifications to voters
  15. Monthly vote trends report
  16. Spam, abuse and off-topic post handling
  17. Quarterly stale idea review
  18. Board signals into prioritisation reviews
  19. Logging requests on behalf of customers
  20. Quarterly board health review
  21. Writing a respectful not-planned response
  22. Reading vote counts without being misled
  23. Finding the problem behind a feature request
  24. Weighting votes by customer segment and revenue
  25. Editing idea titles so votes land correctly
  26. Status update style guide
  27. Studying how other companies run their boards
  28. Moderation judgement calls practice set
  29. Unlimited votes or a vote budget
  30. Comments and anonymous posting decision
  31. In-app widget for posting and voting
  32. Hiding or showing vote counts publicly
  33. Migrating from a spreadsheet or old board tool
  34. Clean-up of a neglected board
  35. Duplicate prevention at the point of posting
  36. Board statuses shown as a public roadmap view
  37. Board launch to existing customers
  38. Yearly round-up of shipped board ideas
  39. Declining a popular idea in public
  40. Relaunching a board after a long silence
  41. Board ideas session at a customer webinar
  42. Solo founder board in twenty minutes a week
  43. Simple ideas board for a small business
  44. Routing board ideas across several product squads
  45. Buyer and end-user votes in business software
  46. Merging two boards after an acquisition
  47. Vote data against churn and expansion
  48. Detecting vote manipulation and campaigns
  49. Board data exports into the analytics warehouse
  50. Yearly decision on keeping the board

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Board purpose and scope statement

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most voting boards fail because nobody decided what they were for, so customers read every vote as a promise and the team reads every post as noise.

First tasks

  • Write three sentences on why you want a voting board at all
  • List the request types that should go to support instead
  • Draft the sentence explaining how votes feed into decisions
  • Pin the agreed statement at the top of the board

Choosing a feature voting board tool

Dedicated board tools, the voting module inside a help desk, a forum category or a plain form and spreadsheet all work at different sizes, and switching later means losing vote history. Choosing against a short list of real needs (sign-in, merging, status notifications, integrations, price per tracked user) avoids paying for features nobody uses or outgrowing a free tool in six months.

First tasks

  • Write the must-have requirements for the board in one list
  • Shortlist three tools, including one built into a tool you already pay for
  • Run a free trial export of ideas and votes from each shortlisted tool
  • Record the chosen tool, its cost and the reason

Public, private or customer-only visibility decision

Who can see the board changes everything: a public board doubles as marketing and lets competitors read your demand, a login-only board gives cleaner data from paying customers, and a private board for internal staff is really a request log. Deciding visibility deliberately, with the trade-offs written down, stops the setting being picked by whatever the tool defaults to.

First tasks

  • Write one benefit and one risk for public, customer-only and private boards
  • Ask sales whether prospects would value reading the board
  • Choose separate settings for reading, posting and voting
  • Tell support and sales which setting was chosen and why

Make it yours.

Install Feature Request Voting Board, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.