How to clean up customer feedback into clear product roadmap priorities

After running our public feedback board for six months we collected more than three hundred feature requests that included things like dark mode and enterprise security compliance. Trying to build all of them left our engineering team exhausted and our release schedule, off track.

We put in place a scoring system that looked at three things: how often the request came in how much it affected core user retention and how well it matched our product vision. Requests that didn't meet two out of the three criteria were put aside away no matter who made the request.

That strict filtering process reduced our list by seventy percent and let us release three big features that really helped our retention numbers. Saying no to ideas is the only way to make space for great ones.

How do you handle feature requests that are conflicting from your users?