How do you decide which user feedback to actually ignore?

by•

Listening to your users is perhaps the most repeated advice in the startup world. Everyone tells you to talk to customers, so the real challenge is filtering out the noise without building a bloated monster of an app.

I have been pondering over my feature request board lately. Some suggestions come from power users who genuinely want the product to succeed, while others come from people who used the app for five minutes and want it to become something else entirely. It seems wrong to dismiss someone who took the time to write an email, but at the same time, I feel guilty saying "no" to paying customers.

The rule I set for myself is to ignore a request until at least three different people ask for it without prompting. This leaves my roadmap rather quiet, and the updates are usually subtle polish, not big shiny additions.

How do you choose?
Do you build what the loudest users want, what fits your original vision, or whatever is easiest to ship? And do you, as a user, actually expect makers to build what you suggest?

5 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.