When designers receive product requirements, they will design according to the demand background, goals, and users, output interactive documents, and improve various details, including special status, style and size, etc. In a company system with relatively complete procedures, how can designers obtain their own design evaluation results from product feedback and data after the requirements are launched? How to reflect its own design value?
If you want to discover the value of design, you can't just ignore the basics and just analyze the data and the results of the user research interviews. Instead, you want to start from the demand itself, return to the starting point of design, and fundamentally look for clues of design value, and finally obtain a complete value outline. .
When it comes to the source of demand, there are mainly two cases:
Design optimization requirements.
The design value in the two demand sources is generated in the whole process of "demand generation - design - product/function launch", and the value of the design is different in each stage.
100% of the design optimization requirements can be used as the result of design value promotion. The main key point is the early embedding of data. Therefore, the article mainly focuses on extracting design value from product requirements .
1. Design value in demand generation
Design begins to generate value from the moment it receives product demand. Mature designers will not be frightened by long PRD descriptions, nor will they be confused by PM's short-sentence requirements, but first sort out the content of the requirements, and split them from PRD or description according to their own design habits Identify the design key points, design details that need to be supplemented, problem points, etc. (after all, the PM's ability and work habits are different, and the designer should also be flexible when docking). Before starting the design, it is necessary to communicate with the PM to confirm the requirements, expected goals, and doubts.
Here comes the point.
Before the start of the design, the process of "tear X" between the designer and the product, in fact, the design has already begun to intervene in the demand. The user behavior path, behavior, jump logic, special state, and user's psychological expectations in the product requirements are all Try to check with PM as much as possible. These processes are all processes in which design affects product decision-making or design promotion, but most designers do not realize... After a fierce "tear X" process, there are generally two results:
(1) There is no problem with the demand