Each person who wants to vote has to:
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:
Jira is a magnificent tool, but it is not ideal for allowing users or stakeholders to vote on your roadmap.
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:
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!
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.