good point, but then explain what you mean by listening to users.
if you mean the majority of people people they will want a faster horse
and if you listen to specific feedback from specific users you'll choose them based on your own bias
because ultimately every user wants something completely different if you ask
I mean that a team should not be a presumptuous echo chamber.
Listening to external requirements, ideas, compaints is needed, if you are creating a product for others and not only for yourself.
How to discriminate what to approve is wisdom, experience and product vision (maybe you are targeting *other* users). But just watching to the numbers/frequency usually is a good start.
makes sense and I can agree now
