How would you decide which user feedback to act on?
Model answer
Model answerNot all feedback is equal. I'd group it by frequency (how many users raised this?), severity (how much does it hurt their experience?), and fit (is solving this aligned with where we want to go?). Single loud voices — especially enterprise customers or internal teams — can distort priorities. I'd always check: is this feedback coming from our core user, or from an edge case? Acting on the wrong feedback is as harmful as ignoring the right feedback.
Framework · RICE Framework
- RReach
How many users raised this? One user's passion ≠ a widespread problem - IImpact
If solved, how much better does the experience get for those users? - CConfidence
Is this one opinion or a pattern? Qual and quant both needed before acting - EEffort
A fix that takes 2 hours and helps 40% of users jumps the queue immediately
Related questions
- What is product-market fit and how would you know if you have it?
- You have 3 features requested by customers and only 1 sprint. How do you decide?
- How would you communicate a feature delay to stakeholders?
- How do you handle a situation where engineering says a feature is impossible?
- How do you say no to a stakeholder's feature request?