How do interaction designers conduct business analysis?

Some designers, especially those with no real experience like me, do not form a systematic method of analysis, which is more fragmented when conducting business analysis, and it is very difficult to design with such analysis and communicate with other members. Here, after learning Daniel's design routines, analyze and organize a set of business analysis process to guide future projects.

Returned to the team at the beginning of April, began to take over the new business, according to the usual reading books and other designers of the design of precipitation learned that as an interactive designer of the business understanding is very important, good designers are just beginning to receive the product manager to give the need to do not rush to draw interactive draft to do the design, Instead, it takes a lot of time and effort to analyze the business, and sometimes it helps PD to organize the business logic together. If a designer is telling other people about his or her own design (especially the superior), being asked "What's going on here", "Why are these functional logic" and other business issues and not knowing how to answer it, it will appear very unprofessional.

　　1, understand the project background

It is important to understand the background of the project, because you need to describe your project more than once in the following time. I am now taking over a project business logic is very complex, and has not previously contacted this type of platform projects, so PD is very patient with me to explain the origin of the project, reasons, prospects and so on, for many times the full communication, This will be a very clear restatement of your project (especially your superiors) when you follow up with other students. Doing well in the early stage of communication will also be of great help to the progress of the follow-up project.

Generally, the project background is mainly:

1. Why do why: Why do you want to do this project, what causes need to do? What needs do users have to do? Are there some problems that need to be addressed? Or are you going to have to do this for XX festival? Why do users use this product?

2. Who is the target user? Who is going to use this product? Who can see the product? What are the parties involved in the product?

3. What do what: what is the function of the product and what value can it bring to the user?

4. How do I: How do users use these features? How are these features implemented? And what is the scheduling of the project?

　　2, positioning business objectives and design objectives

After understanding the project background, the designer needs to locate the business goal and the design goal, the definition of the two in the Five Guide Home Design law is:

Business goal: To use [a strategy] to bring [a value] to the target user to achieve [a realizable way].

Design goal: Use [a design strategy] to bring [a certain value] to the target user to help [a realizable way].

I personally feel that this definition has been a philosophical concept, understanding or more abstract and complex, I have read a lot of this content, but it is difficult to use in the analysis, and many projects in fact, only one overall goal will not be refined to such granularity. So I went to our platform to look at some of the designer's analysis of the content, organize the findings of the general information is this:

Then continue to refine one of the rules to achieve the description of two goals:

　　Business objectives

These are the main sections that can be grouped as business objectives, such as:

1. XX strategy to provide users with benefits, improve users in the website platform of the online share

2. Through XX function for users to meet the needs of convenient search, thereby enhancing the user's use of the site platform efficiency, to achieve XX goal

　　Design Objectives

The design goal in the case is basically consistent with the structure and business objectives, because of its own practical experience and the limited number of cases to be found, so that only personal understanding: Design objectives are relative to business objectives more specific strategy and implementation. It can also be described by using the same routines as the above, such as:

1. User 1 through the XX function to set the activity target and XX way, and if necessary, XX operation to help achieve the goal.

2. User 2 on the XX platform for active configuration, and viewing real-time effects, evaluation and acceptance.

　　3, the scene of the business process

PD, when describing a project to a designer, usually explains the business flowchart, which is often complex and involves the content of each resource module. These content can help us to understand the whole project better and faster, but in the design analysis, on the one hand the business process of many content and design, too much content will interfere with the judgment of the designer, so that the design links need to focus on the core information; On the other hand, the business flowchart lacks some details or does not cover every element that needs to be considered, resulting in the design missing from the final output scenario. So after understanding the business designers need to user perspective to the scene of the business process. By combing through the detailed flow chart, the designer can also better understand the project and check the gaps to fill each element to help PD with the project core information judgment and risk estimate.

Like my recent project, the business process is complex, involving many backend, algorithmic functional modules, and even some offline human operation modules. Involving three-party personnel (background managers, merchant and platform), so I will divide the user according to the scene process analysis comb, list all the operation path and various states, on the one hand check each element to help oneself understand the business, on the other hand also often can find some core issues, and feedback to PD communication, get "This is a good question , I did not think ", you understand very well in place" such admiration.

PD to the business process:

After the designer to comb the user operation process:

1. Basic process

2. User 1 Operation Process

3. User 2 operation Process

　　4, identify the core information of the project

The core information that needs to be listed mainly includes:

User background: What are the characteristics of the user (basic characteristics and behavioral characteristics)? Experience in the use of products?

Function type: What are the functional types of the product? What are the links and restrictions between the various functions?

Key Features: What is the core function? is the operation convenient?

Key scenario: What is the most critical use scenario? What are the characteristics of this scenario? What are the factors that affect it?

Operating mechanism, such as: Product function, algorithm, technology, how the operation of the mechanism? (although this is a technical content, but designers also need to understand clearly, so that the design of the project more grounded gas)

Doing such work has the following benefits:

On the one hand, and PD can jointly establish the focus of the project design, test their understanding of the project is consistent with PD, easy to follow to make a place. Sometimes you can even delineate the areas of responsibility and focus of your work.

On the other hand, it is also easier to communicate with other people who do not understand the business, and to deliver a design with such analytical content to them to make it easier to understand and focus.

　　5, record the problem point

Record and analyze the problem points in the business, confirm with PD discussion, and be sure to reach an agreement! This way, when you communicate with others, when they ask the same questions, they can easily answer and convince them.

The above content is purely personal opinion, if have unreasonable place welcome correction ~