Essential for fielding most popular feature requests with limited resources.

Much needed

One proposed implementation of this could be that each user has a ‘vote bucket’. In other words, a number of votes they are eligible to make at any given time.

The number of votes you can make could be a dynamic factor of how many suggestions have been made (i.e. the size of the ‘vote pool’). So as an example maybe you are given enough votes to vote once on N% of the total number of feature requests. Perhaps this bucket updates it size to match the number of feature requests at a specific X time interval (so either as frequent as dynamically or infrequent as quarterly).

Maybe both N and X are variables that you let the Canny customer tweak for their specific company needs in receiving feedback.

The user can view all of what they’ve voted on and change those vote counts at will.

When a feature has been implemented, users automatically get those votes added back to their bucket to claim elsewhere.

This vote bucket can be kept separate from power user and company stats. Such that I can then filter out votes all originating from the same company and/or weight votes from particular users as I see fit. Without the end users feeling like they aren’t being treated equally.

Lastly, a ‘Power Vote’ or ‘Must Have’ vote are perhaps no more than a symbolic way of applying a certain # or % of your votes in the form of a badge (if this is even needed at all).

Andrew Rasmussen Rather than me offering a solution, let me share our challenge and ask for your advice.

We're getting very, very skewed voting results because companies instruct their staff to all vote on an item. So big customers dominate our board, and they're not 'real' votes.

One thing that would help us tremendously is to have 'number of companies' as a core Canny 'thing' I think? Then at least we could sense check that when looking at vote counts?

I would like to see a limit on the number of votes for one company. This limit must be set in the SSO token

I like the idea of allowing users to vote on as many as they want (as to not limit their interest in any area) but to allow them to rank-order their list. Or be able to have up to, say 3 posts that are at the top in their "priority" votes. I also like the simplicity of another persons idea here, suggesting a single "Power Vote" - Mark the one post you want the most. The post-est with the most-est ;)

Love the discussion here. I would split the difference here. I would love my more engaged customers to have 5-10 special "I NEED THIS"- let's call them "Earnest Votes" in addition to their traditional votes of interest. If we positioned and leveraged these "Earnest Votes" as "they feel they need this first votes"- then we might have engagement with some crude stack ranking of importance.

Totally agreed. This would also be nice to see a shortcut on all the things you have voted on.

If this is an issue re limiting users, maybe a super vote (max 1 usage) but adds more complexity to the problem.

I also think that it would be excellent to collect feedback from the customers' priorities somehow, but I understand why you hesitate to implement it. What came into my mind is a kind of 'power vote.' We could provide a single 'power vote' to each customer so that they could mark their most wanted feature.