Feedback, what to listen to, what to ignore?
Dylan Merideth
5 replies
When receiving feedback from users, how do you create a framework for understanding what to integrate and use to improve your product, and what to ignore?
Obviously you read all feedback, but you have to have some sort of conviction in order to make decisions.
Replies
Anna Kuzma@kuzmanna
There are a lot of aspects to consider actually. First of all, you should keep in mind you product strategy, and where you want to get your product in future. When receiving feedback from your customers always try to find out the reason WHY a user is asking for a certain feature, and what problems he might be facing. When tracking customer feedback we try to get qualitative data to see if the feature request is popular among other customers. To track qualitative feedback we created a public feedback community board where our customers can share feedback that will be visible to others, and they can leave their comments and votes for certain feature requests. If we see that a feature request is popular, we evaluate the resources required, check if the feature won't break the current logics of our system, and what value it will bring.
Share
@dylan_merideth I would say, if it's a frequent request, it makes sense to consider integrating it. The final decision is made by Product Manager anaway
We are considering a target demographic "tag" for our beta at https://ideaisland.io, so we know if feedback came from a user in our target demographic so we can weigh it more heavily.
Let me know what you think