Share User Research Workflow: User understanding methods and experience

Article Description: How to understand our users: Wireless end users understand how to share work methods.

First, the preface

After coming to Tencent, the iphone reader, ipad reader, ipad music player understanding of the user, is currently doing the iphone Qzone user understanding work. Do more times, methods in the continuous improvement, but also accumulated some experience, and share with you, hope to help us better understand the user.

First, introduce the current North Division WSD (Wireless Research and Development Department user Experience Group) User Research workflow: Our research needs from the project team and the use of research group needs pool, in order to control the rhythm and quality, to undertake the project team requirements of the work flow to carry out strict control, we targeted the project team needs, developed a working flow chart, User understanding is also within this framework.

Second, the user understands the method and the experience

2.1 Conceptual explanations

User understanding is one of the basic work of the research, the purpose is to help you see our product is to whom, including the demographic attributes of the user, the use of product objectives, behavior, motivation, and user values, as well as user preferences for certain things.

2.2 Basic Ideas

Defining demand → combing existing problems → looking for users → qualitative research → output periodic report → quantitative research → output final report → report → result follow-up → follow up.

There are some things that can be done in parallel, some of which are iterated over and over in special situations, which need to be handled flexibly according to the specific circumstances of the project.

2.3 Points to introduce

The following user understand the basic ideas about the work of the main points and experience:

Requirements defined to be clear, with the implementation of

Product side of the demand is generally all-inclusive, want to know what the user is, want to know how users use products, want to know how to determine the product's visual style, want to know what the existing version of the problem, want to know the new version of users will have problems, want to know a lot of things. With the research staff will communicate with the demand side to understand the background of demand, to help demand side comb demand, of course, there are some needs in a research is unable to complete, we will suggest that the demand side split into several times with the research. After the two sides agree on the demand, the demand side will send the mail to ask for demand, with the research group interface person to undertake. This part is in the introduction of the use of research team work flow specifications are clearly defined.

Here is a sample of our needs to comb for your reference:

To sort out existing problems and reach a consensus on the present situation

In order to avoid the results of the output of the research report, it is well known that in order to improve the quality of the research, it is important to comb through the problems exposed in the existing resources before the commencement of work, and the project team will have the resources to do so. As far as wireless clients are concerned, we typically look for and mine existing problems through several of our own platforms. Of course there are other channels, such as the App Store, forums, but there are certain limitations.

After you understand the existing problems, you will communicate with the demand side and reach a consensus on the known status.

[1] [2] [3] Next page