Put the user experience design in front of the underlying logic Architecture Design

• User Experience Design The work should not only be involved at the beginning of the project, but many experience designs should be put in front of the underlying design. This is a cyclical iteration process, but what comes before this process should be the interaction process design used by users.

 

1. "Some underlying logical relationships are still being considered. do not consider interaction design for the moment." and "the underlying logical architecture determines the development direction to a large extent, the cost of modifying the presentation layer is not high. "" Our underlying logic is not like this, and the interaction design here cannot be like this ".

The above are very interesting, and these phenomena are also very common.

I believe most Company This is the case now: Product owners or architects (or System Engineers) first design the formation logic and structure, and then perform specific experience design.

2. We have been doing this for years, and we even think it should be. It's like Japan Before people designed very lightweight household appliances, Americans always thought that household appliances must be placed in the cupboard to make furniture.

Now, we should think about it as a whole: Product Design Is the process necessary? Is this reasonable?

3,No.

4. products exist because of requirements. users use products only because of requirements (whether active or passive). Users can interact with the system through the interface to complete the "requirement ".

5. "users do not know or care about the underlying logical architecture of the system? He only knows the interaction process between the presented interface and the user experience ."

6 ,"The user's needs determine the product direction. The user's use and interaction process determine the product design.".

(Remember: it is not "the product design determines the user's use and interaction process ".)

7. A large part of users are engaged in "Interactive Design" in the field of user experience design. Work Which can be roughly described as follows:

"After learning about product ideas and user group features (user research), we will perform role simulation (role design) and Scenario Simulation (Scenario Design) for some typical users ), the scenario reproduction demonstration is used to summarize and Gradually refine the various interaction requirements (task decomposition) in the user's use. Finally, the design results are presented in the form of flowcharts and line diagrams ".

8. It should be noted that the interaction design flowchart is "user use process" rather than "underlying business logic process ".

Although they are very similar, they are essentially different: one is from the user's point of view, the other is from Technology Implementation;The flow chart is used to describe the user interaction process and needs. The underlying business logic flow is used to meet the user's needs.

The process that users use is transformed into the underlying business logic flow process to meet user needs. The underlying business logic flow is transformed into a user use process, it is assumed that the user will use the product according to your design.

9. Obviously, "first design the underlying business logic process and then consider the interaction process design" is Standard This is related to the background of engineers in the industry.

Finally, we will find that the product is designed for technical implementation rather than for users. (Although people who build the underlying logic architecture think they are designing for users, it is undeniable that their expertise is not the same .)

10. This kind of product design process cannot trigger technological improvement, and it will often lead:

The user experience designer has made some good and necessary experiences. Effect "The underlying logic is not like this. We cannot implement this. We can only give up on this part of the Experience "," Why does the user do this? According to our design, they will not do this !" "According to the current underlying logic, this interaction process cannot be designed, so do not consider it ..." And so on, the underlying architecture sets out that the experience design is common...

11,Remember: The interaction process you use is the requirement of the underlying business logic process, rather than the "performance" at the underlying layer ".

Therefore, the user experience design should not only be involved at the beginning of the project, but also be put in front of the underlying design. This is a cyclical iteration process, but what comes before this process should be the interaction process design used by users.

My suggestion: for product requirements, the PM should first design the product interaction, and then consider the underlying business logic and architecture.

Original address: http://uicom.net/blog? P = 575