It really does not matter what methodology, or tools you will use, if at the end it does not pass the user acceptance test
So why consider it a failure if you have users telling you what they want and how off you are? Better to embrace it and make a better product
>That's how you suss out the rare 10% of community feedback that is amazing and transformative.
So don't obsess over every bit of user feedback, but figure out what matters, and what multiple people are complaining about, not just one loud person.
(There is also the issue of observing what people do versus what they say they do. At least early on I find the problems are severe and obvious enough that this subtlety isn't a big deal yet.)