How do you prioritize feedback?

Javier Solans
8 replies

Replies

Neel Patel
Align your vision with demand. Demand must be quantified too- meaning, enough people should ask for it.
Nicolò Marchesi
It seems rather strange... I don't. Don't get me wrong, feedback is highly considered when building new features, but it's more related to why the user needed that specific feature and what kind of problem he was dealing with rather than jumping straight ahead and building what the user requested. It's a spark that should start conversations and questions, but you can understand the underlying problem only after that. Then, after you've discovered, you can get to normal prioritization and roadmapping.
Javier Solans
@pethron thank you for the answer. This is what I was thinking. That's why I have set up a page where all requested feedback is stored there but then afterwards I decide exactly what I'll be working on. Also, most requested feedbacks are from free users!
Tanzirul Huda
Use a customer feedback management tool and let your customers vote on each feature request. You'll find which one is most important to work on.
Javier Solans
@tanzirulhuda right now I am using featurebase for feedback. it let's users to upvote the requested features, let's see how it goes. thank you for the reply
Raju Singh
First things first, start with what you understand. If not, ask and get clarity. Most of the time, we oblige but don't understand it - as per our capabilities, capacity, the timing of it, and that's where regret creeps in. Every feedback is valuable if we understand it and map it on a scale of capabilities, capacity, and timing of it
Mahsima Dastan
Yes but it depends on various factors, some users really need some features