[foobarrio]

Consider their response an input signal and not necessarily instruction from them. If my little niece comes crying saying there is a monster under her bed, of course I know it's not a monster but I'll still go look. Maybe a toy is under there making a noise, or the heater pipes, or the cat is moving stuff around.

[ErikVandeWater]

This is how you get your kid eaten by monsters.

But in all seriousness, this is a good point. In addition, you have to think about the user you are listening to. Are they smart? What terminology do they know that other users don't? Maybe they figured out a workaround to some problematic UI already, and you can just make that workaround global.

[Bartweiss]

I've heard a corresponding principle in both game design and writing expressed as "When people tell you what needs fixing, they're almost always right. When they tell you how to fix it, they're almost always wrong." Feedback is great, but feature requests and proposed changes aren't actually feedback, they're new ideas.