Nice thought provoking article and I can empathise with it. But the title is dangerously misleading IMHO. All feedback is valuable. Decoding it is the entrepre

Nice thought provoking article and I can empathise with it. But the title is dangerously misleading IMHO. All feedback is valuable. Decoding it is the entrepreneur’s job - shutting off feedback from your user base can be a quick death march to oblivion. Hear their pain, ignore their demands :-) If it’s overwhelming have a private beta and gradually let people in (we’re doing that right now at http://hashbo.com http://hashbo.com - I know, I know gratuitous plug) - listen to the first groups pain. Ease it where possible and accept the limitations present. Move to the next. You won’t please everyone, doing so is the pitfall I believe this article is aiming at. Encourage users to feedback, but put it in a list you don’t read. Every now and again look at the list for trends, for themes and reconsider if those themes are within product scope, if they are then get on it, if not forget it. There’s a huge middle ground between between reacting to each demand and ignoring all feedback :-) Personally I decode feature requests into user desires or user pain, so I both agree with the principle of what you’re saying but feel it’s perfectly okay to receive feature requests if you are willing to decode them :-) But to be fair, my follow up the question is, why do you want this feature (i.e. where is the pain :-) ) Ok 2c given :-)