In order to avoid a product becoming the product manager's own design, or the idea of a leader's head. As a member of the product team, the interaction designer has the responsibility and obligation to analyze the requirements and get the first-hand requirements information, instead of accepting an inexplicable list of requirements. How to do it? The author of this article shared 4 practical methods for analyzing design requirements and shared them with you.
01 written in front
With the continuous improvement and popularization of Internet technology, users have further requirements for the visual effects and user experience Country Email Listof products.
As an operations designer, you might think that as long as the visual is done, the job is done. Slowly in the process of work, I gradually realized the importance and value of demand analysis. The ability of requirements analysis directly determines the pros and cons of the output design. Take this article to share with you how I work.
02 Align requirements and communicate correctly
In our daily work, we often encounter some problems of one kind or another. For example, when you have worked hard to finish a page design that you think is very nice and show it to the product manager, you may get this sentence: " Change it again, optimize it again", but they don't provide you with specific suggestions for revision, even if you take the initiative to ask, they can't tell what is inappropriate, or you are a designer and you can think of a solution by yourself .
Communication is crucial here, because this gap determines whether designers can correctly understand the essence behind the requirements, and understanding the essential requirements is the bridge across this gap. Product managers and designers have different functions, so their positions and concerns will be different. Therefore, proper communication is the first step in understanding the needs.
1. Know your goals
It is also mentioned above that product managers and designers have different positions. Designers habitually think about problems from the perspective of user experience, and often need to be responsible for the experience, while product managers need to consider more about product strategy. The problem is to have business KPIs. As designers, we should not only think about problems from the perspective of whether the experience is good or not, and whether it is good or not. Instead, we need to communicate correctly based on user experience and understanding business goals.