Interactive discussion: User scenarios and product demand-oriented design

Author: wbuild

For designers, the most important to their own design is a deep understanding of product requirements, in-depth consideration of the user is how to use the product,

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

In this field, most people may be more focused on how to use tools, how to draw wireframes, and how to turn ideas into realistic demos.

A designer in a further stage may consider how the wireframe works more rationally, how it can have a better interaction effect, focus on the design of task processes and information structures, and usability principles;

To a higher level, I think the need for designers in the first two levels of the base up front products, a deep understanding of product requirements, in-depth consideration of how users use products. Http://www.aliyun.com/zixun/aggregation/6579.html "> What are the paths for users to use the product and what is the actual usage scenario on these paths?" What are strong scenes, which are weak scenes, what are the user goals in each scenario, what they need, what are strong requirements, what are weak requirements ...

Share with you the 3rd level of design methods, which are suitable for the design of webbase products.

First of all, the beginning of the product, from the PM to get the demand, it must not immediately start drawing wireframe. To be a product, our designer's job is to identify two core issues: 1, what pages are needed, and how the pages are related; 2, how each page should be designed.

I think this is the 1th question. First of all, to determine the product user group and use of the scene, where the user group is the actual existence of the product, mutual exclusion of several groups, a lot of classification methods to determine the characteristics of the product itself, can also be based on the preliminary research to determine. Based on this idea, the following diagram is generated:

Of course, there is a need to determine what the strong scene is and what the weak scene is, and then make the design choices. For example, under strong scenarios, you might consider adding a core path entry to an obvious location, such as navigation.

Take Baidu side to give examples, here according to this model roughly listed the page path:

(this point introduces the design model, for the inside of the classification method has the optimization of space here do not make a special discussion)

At design time, we consider the two types of users, and choose from a few of the strongest scenarios, such as looking for food, business, so you need to have a clear business aggregation page and the Food aggregation page.

Now that "what pages are needed and the relationship between these pages" is already clear, we can produce the following product architecture:

The 1th problem is solved, let's look at how a single page should be designed.

The first is to refer to a design model similar to the 1th: consider how many mutually exclusive users there are in this page, what user scenarios they have on the site, what needs and what they need to use in each scenario. For each function, from the depth, breadth, frequency of these 3 dimensions to evaluate the strength of the function. The stronger the feature, the better the design needs to be, such as giving the strongest presentation in the most obvious locations, and the weaker the function, consider hiding, merging, or placing the feature in a non core view area.

To Baidu XX product app website as an example, reference to this model can export the following thinking map:

From this model, we found that the platform portal, download access, product features, etc. score higher, so these are the design we need to focus on and highlight the information. So we did the following design:

In the design of a product process, the introduction of the above design model, we can truly "user-centric" to design, at the same time, can be very clear to solve the following problems:

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

Designers and PM can use the same thinking mode to consider the same problem, avoid endless controversy;

The use path of each user is considered, which provides the basis for the optimization of task process and the rationalization of page path;

Reproduce each page's user goals and requirements, so that the layout and function of the page more reasonable, in line with user expectations;

Original link: "Interactive discussion: User scenarios and product requirements-oriented design"