How to handle feature requests

Here’s a great tip for those of you who are in the process of building something and are getting feature request overload.

The key thing is that you should read all the requests, and the ones that stick in your head either by repetition or appropriateness will be the ones that you should work on. With the experience I have in product creation, this great tip can be squashed very easily if the recipient of the feature request has no interest in feature requests, even if they are memorable and appropriate. Hence, this only works if you have an open mind to developing your product.

Link: Getting Real: Forget feature requests – Signal vs. Noise (by 37signals).

Those are the important ones. You don’t need to track or remember everything — let your customers be your memory. They’ll remind you.