Do suggestion boxes work, and what thirty six real ones look like

Suggestion boxes work when somebody answers what goes into them, and thirty six real ones are read further down to show how rarely that happens. A larger read of 634 public boards found 43 percent had never declined a single request in public.

VoteFirst sells a feedback board, which is a suggestion box with vote counts on it, so read this with that in mind. It would be easier for VoteFirst if the answer were a straight yes.

The answer is yes in a narrow sense and no in the sense most people mean when they ask. A suggestion box works when somebody reads it and something visibly happens as a result.

It doesn't work as a way of finding out what to build, and it very rarely works by itself. The arrangements that do work are listed separately, and the free routes for a staff box are compared on their own page.

That could be an opinion, so it was counted instead. On 27 August 2026 thirty six public feedback boards belonging to real companies were opened, all of them live, and the front page of each was read. This post is what that found and what it appears to mean.

What was actually measured?

Thirty six boards, one day, from outside, with nothing that needed an account.

They're all hosted on the same platform, which publishes each board's post list inside the page it serves, so counting is a matter of reading what's already public.

A larger read followed on 3 October 2026: every request on 634 public Canny and Featurebase boards, 67,473 in all. Counted that way, past page one, the median request held two votes, one of them its poster's. That file is open too. Atlassian's public tracker shows the same over twenty four years: of 179,402 suggestions filed on Atlassian's public tracker since 2002, 17.1 percent were built, and the ones still open have waited a median of 1,186 days.

For each board, the number of requests on page one, the votes on each of them, and the dates of the oldest and newest request shown were recorded. The script is in VoteFirst's repository and anybody can rerun it.

Two limits, stated before the numbers rather than after them.

Page one only. Every count below is a floor. A board with forty requests on page one has at least forty and probably more.

The dates describe the sort, not the board. These boards render their default order, which is prominence rather than date, and a sort parameter in the address is ignored. So the newest date on page one is a floor on staleness and never a proof of it. A board can be busy and still put a popular old request first. Getting it backwards would mean calling somebody's active board dead, which is both rude and wrong.

The demo board is open with no account and carries the same thing this post is describing.

So do suggestion boxes work?

On the median board, the median request on page one has nine votes on it.

Not the quiet corner of the board. Page one, which is the part the platform decided was most worth showing. On nineteen of the thirty six, the median request there has fewer than ten votes. On eight of them, fewer than five.

The top of each board looks healthier and is less useful than it looks. The most voted request had fewer than twenty five votes on eight of the thirty six boards, and on one of them the single most popular thing anybody had ever asked for had two votes.

These aren't hobby projects. They're companies that decided to run a public feedback board and put it on their own domain.

So the box gets filled. What it collects is a long flat list of things a handful of people each want, and almost nothing that a reasonable person could call a signal.

Does a suggestion box tell you what to build?

Less than you would hope, and there's a number for that too.

On the median board, the single most voted request holds sixteen per cent of all the votes on page one. The range runs from six per cent to sixty three per cent, and only one board in the thirty six is anywhere near that top figure.

Think about what a sixteen per cent share means in practice. It means the loudest thing on your board isn't loud. It's slightly ahead.

If you built the top request and nothing else, you would have addressed a sixth of the expressed demand on the most visible part of your own board, and the other five sixths would be spread across dozens of things with single digit support each.

That's the shape of the data, and it's the opposite of the promise. The pitch for a suggestion box is that it surfaces the thing everybody wants. What it actually surfaces is that there's no thing everybody wants, which is useful information and isn't what anybody was hoping to hear.

How many votes do you need before the count means anything?

More than most of these boards have, and the shape of the top of a board says so more clearly than the median does.

The five most voted requests on every board that had at least five, which is thirty five of the thirty six, were compared, fifth against first.

On the median board the fifth most voted request carries forty one per cent of the votes the top one has. On ten of those thirty five it carries at least half.

That's a cluster, not a ranking. The board has taken a few dozen requests and told you that five of them are roughly equally wanted, which you could probably have guessed, and it has done it with a precision the numbers don't support.

Put that next to the median request having nine votes and you get the practical rule. A gap of three votes between two requests is one person having a bad afternoon.

Treat the difference between the first and the fifth as real if you like. Treat the difference between the third and the eighth as noise, because on most of these boards it is.

The number does become useful, but it takes a scale most boards never reach. Until then the vote count is a tie breaker between things you were already going to consider, and reading it as a mandate is how a team ends up building the thing four people wanted loudly.

One large project put a number on it. VS Code closes a request it does not plan to build unless it reaches 20 upvotes within 60 days. Across its 28,886 feature requests, those with one upvote and those with nineteen were closed about equally often, a little over half the time, and more than half of the ones that passed twenty are still waiting in its backlog. A threshold settles what falls below it, and leaves what clears it waiting.

Does weighting the votes fix it?

Partly, and it fixes a different problem than the one above.

VoteFirst's board can multiply a vote by what the person casting it pays you, and the mechanism is written out in full here. That changes what the number means. It doesn't manufacture a signal out of nine votes.

Where it helps is the case a headcount actively hides. Eleven people ask for one thing and four ask for another, and two of those four are the accounts that pay for the office. A plain count says build the first one.

A weighted count says look again, and looking again is the correct response. Both numbers sit on the same card for exactly that reason, because the useful moment is the one where they disagree.

Where it doesn't help is the case most people are in. If everybody who votes on your board pays you roughly the same, or pays you nothing yet, then weighting has nothing to weigh and this whole section is irrelevant to you.

Why do so many of them go quiet?

On twenty six of the thirty six boards, page one still carries a request from 2021 or earlier. The oldest one anywhere on a page one dated from 2011.

Remember the caveat. That's the sort order, not proof of neglect, and a fifteen year old request sitting on page one may simply be popular.

But it does tell you what a visitor sees, and what a visitor sees on most of these boards is a front page carrying requests that are five years old and still open. Whatever is true inside the company, that's the impression the box gives.

There are four reasons this happens, and only the first one is about effort.

Nobody closes the loop. Somebody asks, the request sits there, and no matter what happens next the person who asked hears nothing. This is the one that kills a board, because a person who was ignored once doesn't come back to be ignored again, and they were your best contributor. The fix is mechanical rather than cultural, and it's the reason VoteFirst's own changelog is built out of the board instead of being a separate document.

The box is asked to do a job it can't do. Prioritisation is a decision about cost, risk, strategy and who is paying you. A vote count is one input to that and a weak one. When a team expects the box to decide, and it doesn't decide, the box gets blamed and abandoned.

It's put somewhere nobody goes. A link in the footer collects the requests of people who read footers. That's a real population and it's not your customers.

Nobody says no. A board where nothing is ever declined fills up with items that will never be built, and every one of them is a small lie to the person who asked. The number of open requests goes up forever and the page stops being readable. Saying no in public is unpleasant and it's the single most valuable thing you can do with the box.

When does a suggestion box actually work?

Four conditions, and you need all four, not most of them.

Somebody owns it by name. Not the team. A person, with a recurring slot in their week, whose job includes reading what came in. A box with no owner is a form that writes to nowhere.

Every item gets an answer, including no. Yes, no, or not now with the reason. The answer matters far more than the decision. People accept a no from somebody who read their request and they don't forgive silence.

It's where the work is. Inside the product, at the moment somebody is annoyed, rather than on a page they have to go looking for. That's the entire argument for putting the form where the frustration happens instead of on a contact page.

The people who asked hear when it ships. Not a general announcement. The specific people who asked for the specific thing. If you do one thing from this post, do this one, and if your tool can't do it then do it by hand with a list of names in a text file.

Those four are also, roughly, the four things the boards measured above were not doing. That can't be proven from outside, because only the page is visible.

But a front page where the median request has nine votes and the oldest thing on it's from 2021 is what those four failures look like from the street.

Does any of this apply to the box in the office kitchen?

Partly, and it's worth separating because half the people asking this question mean the workplace one.

The physical or internal suggestion box has a problem VoteFirst's board doesn't have, which is that the person suggesting has to work with the person deciding.

That changes everything about who writes what. Anonymity isn't a nice extra there, it's the whole mechanism, and any advice that ignores that's advice about a different thing.

What does transfer is the loop. An internal box fails for exactly the same reason a customer facing one does, which is that people stop writing when nothing visible happens.

The condition about answering every item, including no, is the one that matters most in a workplace, and it's the one that's hardest because the no is delivered to somebody you'll see on Tuesday.

What doesn't transfer is the counting. Votes on an internal board measure who is comfortable being seen agreeing with their manager, which isn't the same as demand. That distortion has a name and its own page.

VoteFirst does not sell an internal suggestion box, and the numbers above are not about one.

What does an online suggestion box template actually need?

An online suggestion box template needs two fields, not one, and the wording around them matters as much as the fields.

The first field is one line, capped at two hundred and fifty four characters, and it asks what they want. The second is a longer box, capped at two thousand characters, and it asks why.

VoteFirst's suggestion form widget uses exactly those two fields, both required, because a template with a single open box collects one line comments that are unreadable in a list of forty.

The wording around the fields is the part people copy wrong. Say, before anyone types anything, that the idea will be read first and is not live yet. That line belongs on the form itself, not in a message afterward.

Cap both fields before building anything else. An uncapped title is unreadable in a queue of forty, and an uncapped body is an invitation to paste an essay nobody on your team will finish.

Do suggestion box names matter?

Suggestion box names matter less than the four conditions above and more than zero. A box called "Suggestions" gets used. A box called something nobody understands, some clever internal name dreamed up in a meeting, gets ignored because people are not sure what it is for or whether it is even the right place.

A few suggestion box name ideas that hold up in practice: "Ideas," "Have your say," "What would you change," or naming it after what happens to what goes in, like "Build queue" or "What's next." Plain and literal beats clever every time, because the name's whole job is telling a stranger what to do at the box without reading further.

The exception is a name that promises something the box cannot deliver. Calling it a "vote" when nothing is ever built off the count, or calling it "anonymous" when it plainly is not, costs you the trust the name was supposed to buy.

None of that changes the numbers earlier in this post. A well named box that nobody answers still ends up with a median of nine votes on page one.

Do fun suggestion box ideas help?

Fun suggestion box ideas, a prize for the suggestion that gets built, a running leaderboard, a silly category next to the serious ones, raise the number of notes going in for a few weeks. They do not touch the four conditions above, and the four conditions are what decide whether the box is still alive in a year.

The risk with fun is that it crowds out the boring, useful notes. A box that rewards the funniest suggestion trains people to write funny suggestions. If you run a fun angle, keep it as a second, clearly separate lane rather than mixed into the main list, so the count on the serious requests still means what it is supposed to mean.

Novelty is a way to get the first fifty notes written. It is not a substitute for answering them, and answering them is the part that decides whether note fifty one ever gets written.

How do you write a suggestion so it actually gets read?

Writing a suggestion or a recommendation that gets read starts with naming the problem before the fix. "The printer on the third floor is out of toner most Fridays" gets read and understood in five seconds. "Fix the printer" does not tell anyone what is actually wrong, and it gets buried under twenty other one line notes just like it.

Say what you want changed in one line, then why, in the fewest words that still make sense to someone who has never thought about the problem before. That is the same two field shape the form on this site uses, and it exists because the boards measured above are full of one line notes nobody can act on without asking a follow up question that never gets asked.

A recommendation carries more weight than a bare suggestion when it says what you would do instead, not just what is wrong. "The booking system double books rooms; a simple calendar view would show this before it happens" is a recommendation. "Fix the booking system" is a complaint wearing a suggestion's clothes.

One thing to leave out: do not pad it with a justification about your own convenience. Notes that explain who else is affected get taken more seriously than notes that explain why the problem is annoying to the person writing it.

Should you run one at all?

If the four conditions aren't going to be true, no. Run an inbox instead, and read it.

A great many teams asking about a feedback board should still be using a spreadsheet and an email address, and the four conditions under which that's the correct tool are written out alongside the three signs that you've crossed the line.

A suggestion box that nobody owns is worse than a spreadsheet, because it's a public promise you're not keeping.

If the four conditions can be true, then a box is worth having, and the value isn't in the vote counts. It's in having one address to send people to, one place where the answer lives, and one mechanism that tells the person who asked when the thing arrived.

The counting is a byproduct and it's the least important part, which isn't what anybody in this category will tell you.

14 days, a card at signup, then $9 or $39 a month.