The features on the voting list on the link I saw yesterday, seems already mostly implemented, or nearly completed. I was initially unclear on some features on the list. It would be good to have some more details on the features in the voting list, otherwise the votes may be made on innacurate assumptions. Once you find an idea you like, open it to get access to voting and commenting. Example: Figure 8 – Vote and comment. Equally important to voting is explaining why you voted a certain way. The more information you provide, the easier is for the PD team to customize the new functionality to serve your needs.
Letting your customers and team vote on potential new features is a simple and effective way to build a product roadmap.
After all, customers are using your product on a daily basis. They know what is working for them and what isn’t – and they expect you to care. A public roadmap helps them see that you do.
- If you can’t find what you are looking for you can start a new feature request. Once you’ve found the feature you want to support then cast your vote by clicking on the Vote button. At anytime if you change your mind and want to remove your vote from a discussion you can do this by clicking the tick button.
- Re: Vote on your favorite new features « Reply #25 on: September 26, 2020, 10:32:17 AM » I defenetly agree. The status screen should have some quick buttons to launch a scann and updates.
Each member of your team also has unique insights into what is working and what needs to be improved. They can help you create a strategic product roadmap that leads to growth and increased revenue.
Using a tool with a feature voting capability gives you the ability to see which improvements are most needed. The most needed ideas rise to the top; the least valued sink to the bottom.
In this article, we’ll describe four ways you can implement roadmap voting using simple tools that are either free or cheap:
|Customers can vote||Yes||No||No||Yes|
|Customers can vote without signing in||No||No||No||Yes|
|Facilitates comments and discussion||Yes||Yes||No||Yes|
|Designed specifically for roadmap voting||No||No||No||Yes|
Trello is a popular collaboration tool that organizes your projects into boards. For basic use, it is free for unlimited users. Paid versions cost from $10/user/month.
Vote For New Features 2019
Trello’s voting “power-ups” enables voting on a Trello board. The free version of Trello allows one power-up per board, so you can use this without charge.
Here’s how you can use Trello for roadmap voting:
- Create a Trello board to track suggestions for your product’s roadmap. If you want the public to be able to vote, make sure it is a public board.
- Create a list on your board called “Suggestions”. Each time a user makes a suggestion, add it to this list.
- Enable the “voting” power-up to add the “Vote” button.
- Users can now vote by viewing a card and clicking on the “Vote” button on the right-hand side under “Actions”.
Roadmap voting with Trello
Each person who wants to vote has to:
- Have a Trello account. They’re free, although manyusers will give up trying to add a suggestion if they don’t already have a Trello account.
- Learn how voting in Trello works. It is pretty simple but not immediately obvious, which could be an issue for time-poor customers.
Depending on your industry, many of your customers might already be familiar with Trello and have an account.
Trello is a general-purpose tool. Although you can implement roadmap voting with Trello, it lacks that “designed for purpose” nature.
Jira is the most popular issue tracking software on the market. Many product development teams are already using it. If you are not already using Jira as an issue tracker, it is cheap and easy to get started.
Jira allows voting on issues. You can create a “project” in Jira to specifically track your roadmap, or you can use your current Jira project. Only people with an account on your Jira installation can vote, and you do need to pay per user for Jira. For this reason, Jira works best as a way for internal users to vote on a roadmap.
Each Jira issue has a “Votes” section. With a single click anyone viewing an issue can register a vote.
If you have a product with an external customer base, using Jira to track voting can be frustrating. That’s because your customers can’t vote directly. Instead your support teams vote on behalf of your customers. Jira only allows one vote per Jira user, so you won’t be able to track each customer vote.
For one of our products, we tried using Jira ourselves for tracking roadmap voting. As customers requested improvements, we’d add them to our Jira project. But because each internal user could only vote once, we couldn’t properly track outside demand. If we had 10 customers ask for the same feature, we couldn’t easily capture that info in Jira. This was part of our motivation for creating Feature Upvote.
Voting in Jira work wells when all your users are part of your organisation. The voting is not an immediately obvious feature in Jira, so you would need to explain to each team member:
- That Jira has voting
- That you want them to vote
- Which issues are for voting on
Jira is a magnificent tool, but it is not ideal for allowing users or stakeholders to vote on your roadmap.
Excel or Google Sheets
You can use a shared Excel document or Google Sheets document to record each suggestion your customers make. Use one column to record number of votes. Here’s a sample structure.
Roadmap voting with a spreadsheet
This is okay for a diligent team. You probably already have Excel or Google Sheets. Most of your team are probably already proficient in either Excel or Google Sheets. But as a voting solution it is cumbersome, it requires a manual process, and lacks public visibility. It won’t record who voted and when. It is hard to clarify suggestions, to comment on them, and to know if the votes were recent or from long ago. Users can’t tell if they’ve already voted for a particular improvement.
A spreadsheet has the advantage that you can set it up immediately without purchasing new products or creating new accounts.
Here at Feature Upvote, we tried using a spreadsheet. We tried using Jira. We tried using Trello. In each case, we were unhappy with the experience. They all gave us pain. They didn’t give our customers a public view into our roadmap, and they didn’t make roadmap voting easy. So we created Feature Upvote.
These were the features we wish we had in Jira, Trello, or a spreadsheet, and that we built into Feature Upvote:
- Customers can view and add suggestions without having to go through our support team
- Customers can vote on existing suggestions
- Customers can comment on existing suggestions
- Suggestions automatically sort to show the most popular items
- Customers can see which suggestions we are planning to do
We wanted to make sure each suggestion, comment, and vote was tracked by user and date.
Roadmap voting with Feature Upvote
Feature Upvote offers your customers a way to submit suggestions directly, using a self-help model. This should save your support team time (and you money).
Customers can also use Feature Upvote from their mobile device, their tablet, or their traditional computer, making it easy for them to give you feedback as soon as they think about it.
With our voting system, your customers can build your roadmap. Simple!
Ready to give Feature Upvote a try?
Getting started with Feature Upvote is painless; in just two minutes you’ll have roadmap voting enabled for your product.
Try our free 30-day trial. No credit card required. See Feature Upvote pricing.Start free trial
30 day trial, no credit card required
Tell us which features you’d like us to add! Vote on the answers below. If the thing you want isn’t there add it yourself!
Vote For New Features List
Batch Processing of QCPA framework
Low-light versions of the RNL model integrated into QCPA
Adjustable weightings for the chromatic and luminance thresholds in the RNL clustering
Vote For New Features 2018
SIFT (Scale Invariant Feature Transform) based pattern analyses
Distance dependent effects of scattering (Haze, dust, fog, smoke, particulate matter) as addition to spatial acuity modelling
Landmark based pattern analyses
Easier ability to input visual system information such as the receptor sensitivities for non-model species (not included in the toolbox).
Landmark-based deformable image alignment as implemented by some Fiji plugins like BigWarp. It would make image alignment so much easier especially for rotations and slight out of plane pictures.