I think the problem there is that you aren't understanding what they're asking for. I'm sure they are being perfectly clear in telling you what they want but so

I think the problem there is that you aren't understanding what they're asking for. I'm sure they are being perfectly clear in telling you what they want but something weird happens when users describe features and wish lists. They often don't know what they want. Finding that out is YOUR job. IMHO, what you need to do is ask them what would make it better and then dig in to find out what they really mean. Why do they need that feature? There's no script or formula to do this, but that's one question I've found to be useful. For example, User A says: put a link on my profile, which when clicked shows my age, sex and location. You should ask, "why do you need that?" The User will often respond in some way which will give you a clue as to what they're really looking for. So, the response to that question might be, "oh, well, people always email me to ask me what my a/s/l is and I'm tired of telling them." So, using this (very lame!) example, they're not looking for a link - they're looking for a way to show their a/s/l on their profile. You can give them what they really want, not what they're asking for. I hope this makes sense.