"Don’t bother soliciting feedback unless you’re in a position to act on it. If you’re not ready to start coding or designing, then you’re not in a position to act. It might seem constructive to run surveys asking what your users want, but if their only purpose is to make you feel busy then you’re fooling everyone. Feedback has to result in action. That action is design, implementation, and communication back to the user. Turning the feedback into a to-do list with no one responsible, or a putting it on a whiteboard of “stuff to do someday, maybe” is the equivalent of saying “Yeah, whatever” to your users. They won’t be keen to talk you again."
Quote by Des Traynor
I’ve been working on our feedback experience lately, and I feel like the biggest part of the feedback experience is what happens to the feedback after someone gives it. Sure it should be simple and easy to be able to give feedback, but the real reason someone is leaving feedback is to be heard. So how do we make sure that this is happening? These are the aspects that I want to focus more on.