Ongoing engagement and conversations with your users, testers, clients, and more are imperative for growth and improvement, so we must speak directly to them.

That being said, we can’t just take everything they say as holy scripture and must try to identify whether it’s an important signal or just a very loud noise. And there is also an option it’s just a bleep that doesn’t necessarily amount to much right now, but the seed will grow in many exciting directions.

But there is no foolproof way to find out if a user’s feedback will amount to something that is nice-to-have or a must-have, yet we should be open to it nonetheless.

Is the idea, feature, or feedback provided just a throwaway opinion, or is it something they can actually explain and convey its importance and why it should be considered seriously?

If it’s a concern or worry, will you take an extra minute and empathize with their feedback to realize if it’s a personal matter to them as users?

And also, does their feedback stay in line with helping improve their end gain?

Everything should be taken with a grain of salt, as you never know where the hidden gem will be found. For example, devs are people too, and sometimes their feedback is technical, sometimes it’s feature-related, and sometimes it’s a recommendation for a dark theme :).

While on the surface it may sound just nice-to-have, or not too important, could it end up meaning a whole lot more for your target market?

So listen intently to find the signals for improvement.