How to put forward constructive feedback to designers

Editor's Note: This article by Julius Tarng, originally published in Medium.

In the process of continuous product change, but whenever a new design, usually ask for feedback from colleagues. The intent is very good, after all, the more feedback a design receives, the more likely it is to be improved.

But, what we need to be aware of is that nowadays most of us are accustomed to feedback directly via email. The feedback given in this way often lacks systematic thinking. E-mail than face-to-face Kan, it can not you a sentence I continue to say this sentence, but also do not see each other's body language. The designers who receive the feedback can only try to figure out the meaning of the speaker from the text. Sometimes, if the feedback expression is not clear, the designer can easily misunderstand the true meaning of the feedback.

I believe text can produce efficient conversations, so efficient feedback can be obtained by mail, except that we need some tips:

1. Keep everyone's information in sync

Before the designer can write down the feedback e-mail, the designer needs to make sure that all the people expect the project to be consistent. For example, the feedback survey should understand some of the terminology you are using and know at what stage of this version it is. Different expectations of the project lead to unnecessary debate.

At the same time, the designer can also write down your own expectations at the beginning of the email, for example: "I hope this prototype can be done this week, and it is expected to be officially launched this Friday. Therefore, the feedback is based on the following assumptions. ."and many more.

2. Say your own feelings, do not say your illusion of the user's feelings

Bad: "I do not think ordinary users can see this sharing button!"

OK: "I will not share this link because I can not find the Share button."

The problems users face when discussing your illusion are straightforward, but the image of the user in each person's mind is not the same, so it's hard to be constructive. Put another way, write feedback as a diary, straightforward and clear record of your own real design ideas. It may be that people will dispute because of the illusion of the user in their hearts. However, when we discuss our own opinions and feelings, because these are indeed true beliefs, discussions based on such real feelings are more constructive.

3. Seek advice, not let them convince you

Do not ask questions with emotions, such as: "How does your fucking know that the user will know how to use it?" This can be resentful.

Another way to ask: "Why do you think users know how to use ah? Can say it?" Through conversations later, he understands the underlying ideas behind him rather than focusing on who is right or what is wrong with the focus of the discussion.

4. Reduce the subjective wording, try to use the objective description

Bad: "It's a weird place to put this icon here."

Okay: "I used to see this icon at the bottom, and now that the design changed the position, I looked a bit not used to it."

Supervisor's words are difficult to understand the meaning behind it, the same word each person's understanding can not be exactly the same. So try to use considerable words to describe your subjective feelings.

Do not be too emotional

Bad: "I did not know the meaning of this icon at all, it just looked like ants who were only hiding their talents."

Okay: "After seeing this icon, I have to think about what it represents for a while and it kind of looks like a hiding ant."

Think before you use the word. Few face to face chatting concerns, but you're half joking tone in the mail but can not feel. Metaphor or exaggeration of the elements, shown in the text usually give people a less positive feeling. It may be helpful to have your text as soft as possible, "maybe", "maybe", "a little bit" and so on.

6. Observing and feeling for a period of time, and then back to the mail

Feel it again For a product to be used daily, the feedback based on the first impression may not be accurate. Can simulate the daily use of the scene, seriously feel the design, and then look at their own feedback is reasonable, confirmed after the e-mail.

After working for a start-up for a year, I found that almost all of my feedback is subjective - most people give feedback based on their own experiences and assumptions. Coupled with the mail "expressive" face to face communication is not as strong, often lead to unnecessary "internal friction", the effect is not obvious. The same problem, many large companies also exist.

However, in fact, these problems can be solved. If you also encounter the problem of seeking feedback not only without feedback, but cause internal conflicts, try the above method.

SOURCE: medium.com