This rhymes with how one treats feature recommendations from users. It is typically the case that a user advising you to make a change does indeed have a problem when using your product that they’re trying to solve, and you should figure out what that problem is, but their account of how to solve it (what ‘improvement’ to make) is usually worth throwing out the window.
This is also very, very true in UX design (and all similar fields such as print design, etc.).
Edit: This is why “I didn’t like X” or “X seems ugly” or “I have a hard time reading X” is extremely valuable feedback, and any designer is always happy to hear it. On the other hand, “X is designed wrong because [criticism of specific design decision]” is basically worthless feedback, and almost never helps in any way.
Edit 2: Note that the above is the opposite of what people’s intuitions tell them constitutes valuable feedback. Non-designers often think that “I didn’t like it” or “it’s ugly” is unhelpful, and they try to be more helpful by making specific criticisms (like “the text is justified; it shouldn’t be”). Coming from a layperson, this attempt to be helpful is actually the diametric opposite of an improvement, turning useful feedback into useless advice.
Edit 3: The most useful feedback is the one that tells me what is the specific problem you are experiencing. The subjective nature of the feedback is important!
This rhymes with how one treats feature recommendations from users. It is typically the case that a user advising you to make a change does indeed have a problem when using your product that they’re trying to solve, and you should figure out what that problem is, but their account of how to solve it (what ‘improvement’ to make) is usually worth throwing out the window.
See also:
(And, really, the rest of the comments on the post “Incorrect hypotheses point to correct observations”, as well as the post itself. Highly relevant!)
See also: https://en.m.wikipedia.org/wiki/XY_problem