We collect customer feedback on our products in a variety of ways / channels (sales tickets, support tickets, customer development interviews, etc.). We store it and work on it, but we're missing a great way to score it.
What's your recommendation for scoring it internally? Let's call an instance of feedback an "item". Multiple instances of feedback on the same thing go under the same "item". Now... to score it:
How are you handling this? What are you recommendations / best practices? I'm sure it's come up before. I just coulnd't find a discussion on this here on Answers.
Thanks much for any advice: I really appreciate it!
Usually you would have something like CRM software for it, i guess. But just for me to understand the question better:
As i have experienced these things usually a custom field has been created in jira to tackle this, something like customer impact or some other "text/number" field to tackle the number. The perfect thing would be to have a public issuetracker where all customers can see all improvements and then either upvote or create a new one, a good sample would be github or the atlassian trackers.
I am a developer not a sales person. My preference would be (as a product owner without contacting the customer):
Thats what i currently could think of with JIRA/Confluence default mechanics. In the end it's about a feedback translated into improvement requests and the later one is ultimately an issuetracker thing imho.
Thanks so much Frank!
I'm still unsure on how to collect the "votes". We have around 30 people between sales and support staff. The key for me is to give them an easy way:
If it's a page in Confluence (which would make sense since at that point we're still in the phase in which we're discussing the feature: it's not a task or issue yet), there is still the problem of letting the sales/support staff "vote" more than one.
Would you just have them add the customer name / ID / Ticket ID / etc. as a way to vote, and then count those?
This is quite informative: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com
There is some feedback page (tracker), like a wiki page with a table and a column with customer id (which gives the unique number of external votes). And another system / project where the actual improvement can be worked on. Like in the given article. When you already mention that you have some customer feedback portal (CRM) then you already have such translation / transition system. It is now about a comprehensible way to track it, right? I think the wiki page is a good start.
Anyway, if you dont have the need for permission stuff and showing some fields only for some audience you usually dont have to verify no one votes more than once i suppose. And usually the product team can find out also quite easy whether a feature already has been created in the todo's.
Quite often there is not the right or wrong tool, just the tool where everyone accepts to work with ;)
Thanks Frank, very much appreciated. For now we have decided to go forward with a table in Confluence as you mentioned above (with ticket or customer IDs of those that submitted certain feedback/feature requests), linked to feature-specific pages still in Confluence (for discussion / specifications), which will then be linked to an issue in JIRA when the new feature / enhancement has been spec'd out. Thanks again for taking the time to help!
You can take a quick look at Customer Case add-on for JIRA Cloud.
It allows you to have the customer portal which allows you to unify all feedback channels and process them in one place - in JIRA Cloud.
As of now, you cannot vote against ideas, but you can contact their team and ask for this feature. They are quite open and react quite quickly to such feature requests.
If you interested in a lightweight score solution for JIRA server, then check out our Feature Score add-on. This plugin adds a simple custom field type that allows you to immediately see your item's value on the Issue screen. You can customize your metrics, value range, and weights easily and the score will be calculated based on the configured equation.
Also, you can check out our best practices here about customer feedback management.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot