Subscribe
Sign in
How do you prioritize features when user feedback conflicts with your long-term vision?
1. First, it's essential to thoroughly analyze user feedback and uncover the underlying needs. Oftentimes, users are not pointing out a specific problem but expressing dissatisfaction with a particular scenario, which might already be part of your long-term roadmap.
2. If there is indeed a significant conflict between user feedback and the product vision, I suggest being transparent rather than hiding the truth. It's even better to communicate openly with users-perhaps even recommending a product that might better suit their needs.
In conclusion, I believe that the long-term value of a product will always shine through, and maintaining a good relationship with users is undoubtedly a critical factor.
8
Replies
Best
@zhiqi_shi This is very hard because the bigger company is and a lot of people in management, the worse for new suggested and applied features. But I have heard many founders to apply those who are asked by already paying users/clients. If there is a massive inquiry.
@busmark_w_nika Small companies face greater survival pressure, so it's understandable. Big companies usually have complex review process, which allow for more adjustments to be made, sometimes it's not that difficult.
Analyze user feedback, uncover core needs, and communicate openly. If there's a conflict, transparency is key, and long-term vision should guide decisions.
First, deeply understand the long-term vision and identify the core features needed to realize it. Then, thoughtfully consider user feedback and look for alignment with the vision. Where there's overlap, prioritize those features. For conflicts, analyze if the feedback reveals gaps in the vision to address. Else, deprioritize and clearly communicate the reasoning to users. Continuously refine the vision based on learnings. It's a balancing act of staying true to your north star while being responsive to users.
I agree.
At the same time, I think it is necessary to count the number of similar problems reported by users.
When a problem contradicts my development vision but receives a large number of user feedback, I need to reflect on whether my product planning was unreasonable from the beginning. Although the probability of this extreme situation is very low, it is still possible.
We should continue to listen to the voices of users and maintain a continuous attitude of optimizing the product.
minimalist phone: creating folders