A vote count is a wonderful, blunt number. It says how many people cared enough to press a button. It does not say when they started caring, or why a request that sat quietly for a year is suddenly getting ten votes a week.
That second question is often the more useful one, and the answer is in the activity around the post rather than in the total.
A total hides its own shape
Two posts can both have 120 votes. One collected them steadily over eighteen months. The other got 90 of them in the last three weeks. They are not the same request anymore. The first is a long-standing wish. The second is something happening right now: a competitor shipped it, a regulation changed, a big customer started onboarding a team that needs it.
If you only sort by total, both look the same. Sort by what's rising and the second one jumps out.
Look for the trigger
When a request starts moving, read the newest votes and comments before anything else. You're looking for the event behind the spike. Some common ones:
- A launch on your side that made the gap visible. You shipped a dashboard, and now everyone wants to export it.
- A change in who's signing up. A new kind of customer brings a new kind of request.
- Something outside your product. A deadline, a new law, a tool your customers also use changing how it works.
- One person in a larger company telling their colleagues. Ten votes from one company is a different signal from ten votes from ten companies.
Each of these suggests a different response. A launch gap might be a small fix this week. A new kind of customer might be a strategy question. One company rallying its colleagues might be a conversation with that company before it's a feature.
Read the comments in order
Comments carry the "why" that votes can't. Read them oldest first and you'll often see the request change shape over time. The first person wanted an export. The tenth wanted the export scheduled. The twentieth wanted it sent to their finance tool directly. That drift is your real roadmap item, and you'd miss it if you only read the post's title.
Then decide, with the score as one input
None of this means votes don't matter. They matter a lot. They're the cheapest honest signal you have about demand. But treat the total as the start of a question, not the answer. Ask what changed, who's asking, and what they're doing today without it. Then decide.
A useful habit: whenever a request crosses some line you care about, say fifty votes, write one sentence on the post about why you think it's moving. In a month you'll have a short history of what's driving demand, which is worth more than any single number.