Do you know to not give anchors for getting feedback?

Last updated by Tiago Araújo [SSW] about 1 year ago.See history

Anchors are prompts or questions that guide the person providing feedback towards specific areas.

When it comes to requesting feedback, it's natural to want to guide the conversation by providing anchors that direct the conversation towards specific topics/elements. While this approach may seem helpful, it can actually hinder the quality of feedback received.

For example, if you were testing a new website, you might give an anchor such as "What do you think of the color scheme?" to direct the feedback towards the visual design. This approach can limit the feedback you receive by steering the conversation away from potentially valuable insights.

One of the most effective ways to get high-quality feedback is to observe how people use/do something.

For example, if you're testing a new product, you might watch someone use it and take notes on what they struggle with or what they seem to enjoy. This approach allows you to get feedback that is unbiased and focused on the user experience.

Video: How to Test a Frying Pan at the Store? 🤣 (15 sec)

Another effective approach is to ask open-ended questions that allow the person providing feedback to offer their thoughts freely.

By taking this approach, you can receive more valuable and constructive feedback that will ultimately lead to better outcomes.

Written work

When requesting feedback on emails, it's best to get the person providing feedback to read the email themselves, rather than reading it to them.

This allows them to read at their own pace and absorb the information fully, without feeling rushed or distracted by your tone of voice or inflection.

We open source. Powered by GitHub