Interactive discussion: design based on user scenarios and product requirements

　　

 

[Editor's note] the author @ wbuild in this article introduces the three stages of a designer's growth, in view of these three different stages of development, we have discussed three different design methods to adapt to their own levels. From Basic Technology to performance design, the last thing designers need to do is to design users.

For designers, the most important thing to design is to have a deep understanding of product requirements, and to have an in-depth consideration of how users use products,

As an interaction designer, I think there are several stages of development:

In this field, most people may focus more on how to use tools, how to draw a line chart, and how to turn ideas into real-world demos;

Designers in the next stage may consider how the lineframe diagram is more reasonable, how it can have better interaction effects, the design of task flows and information structures, and the availability principles;

At a higher level, I think it is necessary for the designer to go to the front-end products on the basis of the first two levels, deeply understand the product requirements, and thoroughly consider how users use the products. What paths are available for users to use products and the actual use scenarios of these paths. What are strong scenarios, what are weak scenarios, what are user targets in various scenarios, what are their needs, what are strong requirements, and what are weak requirements ......

I would like to share with you 3rd levels of design methods that are suitable for the design of WebBase products.

First of all, when we get the requirement from PM in the early stage of the product, we must not immediately start to draw a line chart. As a product, our designer's job is to determine two core issues: 1. What pages are needed and the relationship between these pages; 2. How should each page be designed.

This is my consideration for the 1st questions. First, determine the user group and application scenario of the product. The user group here is the exclusive and exclusive user group of the product. There are many classification methods, which are determined based on the product's own characteristics, it can also be determined based on the previous research. Based on this idea, the following thinking diagram is generated:

　　

 

Of course, it is necessary to determine which scenarios are strong and which are weak, and then make some trade-offs during design. For example, in a strong scenario, you can consider adding a more important path entry to an obvious position (such as navigation ).

Take Baidu as an example. Here we use this model to roughly list the page paths:

　　

 

(This section focuses on the design model and does not discuss whether there is room for optimization for the classification method)

During the design, we considered these two types of users and selected several of the most powerful scenarios, such as looking for food and sellers. In this way, we need to have a clear business page and food page.

Now, "What pages are needed and the relationship between these pages" is very clear, and we can generate the following product architecture diagram:

　　

 

The 1st problems have been solved. Let's take a look at how to design a single page.

First, we should reference a design model similar to the 1st question categories: Consider the scenarios where there are several mutually exclusive users on this page, what are the requirements and functions of users in each application scenario. Each function is evaluated in depth, breadth, and frequency. The more powerful the function, the more important it is to give priority to this function during design. For example, the strongest display is given in the most obvious position; the weaker the function, the more hidden, merged, or placed in a non-core view area.

　　

 

Take the official Baidu XX product APP website as an example. If you reference this model, you can export the following Mind Map:

　　

 

From this model, we found that the platform portal, download portal, product features, etc. scored a high score, so these are the information we need to consider and highlight during design. Therefore, we have made the following designs:

　　

 

In the process of designing a product, we can introduce the above design model to achieve "user-centric" design. At the same time, we can clearly solve the following problems:

Simulate how real users actually use our products to avoid blind subjective assumptions;

Designers and PM can consider the same issue in the same way of thinking to avoid endless debate;

The actual use path of each user is considered to provide a basis for task flow optimization and page path rationalization;

Reproduce the user goals and needs of each page, so that the page layout and function display are more reasonable, in line with user expectations;

Link: http://qing.weibo.com/1899099217/7131f45133002570.html