Today I want to talk to you about the communication problems in the work of designers. I believe that designers often encounter a situation in their daily work: the development students are unwilling to do the plans we propose. In the three years that I have entered the category email list workplace, I have experienced designing according to product requirements, directly connecting with development students after completion, and reading the plan word by word; I have category email list also experienced product innovation, working with the product team and development team. Formulate product direction, formulate product requirements, and propose design suggestions.
Facts have proved that no matter what the situation is, our plan will be questioned by the development classmates to some extent, or even "obstructed"; so we had to go to battle with the development classmates, and spent a long time going to category email list rounds of meetings. , discuss, run in. The cycle is long and inefficient, and there are so many tomorrow after tomorrow. First of all, it should be noted that the reasons for disagreements in team work must not be one-way. The category email list birth of a perfect product must absorb multiple viewpoints and experience the collision and acceptance of ideas. Today, what I want to talk to you about is how to accurately and effectively express the reasons and advantages of the design scheme in the communication stage, and how to better make the development students accept and convince them.
This is also to better grasp the right to speak to designers in the future. After all, developers are also a large user group that designers need category email list to face. Therefore, we need to understand the needs of users in order to accurately judge the "enemy situation", take corresponding countermeasures to defeat the "enemy", let them be persuaded by us, and then it's category email list over. In fact, in most cases, developers are reluctant to follow the designer's plan for the following two reasons: They don't understand your design The workload required by the scheme "seems" too large 01 They don't understand your design Have you ever encountered this situation.