Allow users to allocate priority across their already supported ideas
For example, each user gets 100 "feedbucks" (still working on that term) that are by default evenly distributed across all their already voted on suggestions. User can then adjust their points to highlight certain suggestions with a higher priority.
So I could vote up 50 ideas, and my $100 would by default be split to $2 per idea. If I vote for another idea, the split would be cut down to ~$1.96 per idea, but could at any time redistribute my $100 according to priority. No limits to votes, but secondary metric to allow me to communicate priority.
Having the user acknowledge a scarcity of resources, helps channel their influence to where they would really like to see change.
We’d be interested to hear what other ideas people have for expressing priority?
I certainly think this would be a valuable data point, especially when trying to assess criticality of the feedback (toward something like renewal or closing a deal). UserVoice already supports the notion of a “blocker,” but only a binary option for internally captured feedback.
Would a 1-5 scale work? Something in words? Interested in gathering ideas so that we can explore testing those.
Thanks as always for the feedback!
Kevin Praeger commented
I love the idea to communicate a second metric, priority. This one should be well thought out. For example we would likely want this to happen at the company/account level and not necessarily at the user level.