Hierarchy Task Analysis

To do a user-centric design, we need to better understand the user, understand the user. As an interactive designer, we need to sort out the user, the target (Goal), the Tasks (Task) before we draw the interactive manuscript.
Today, we mainly discuss task analysis . At present, the common task analysis methods are: Hierarchical task analysis (hierarchical task analyses) and cognitive task Analysis (cognitive task analyses). In this paper, we will focus on the analysis of task hierarchy task.

　

What is hierarchy task analysis?
Hierarchical task Analysis is a structured approach to objectively describe the task and its subtask hierarchy system. In user experience design, hierarchical task analysis is used to analyze and describe a series of tasks that users can do to achieve their goals, and how users interact with software systems.

　

Why use hierarchical task analysis?
we through the level of analysis will continue to disassemble the task, the gradual refinement of the user's task, until the actual operation of the user. As tasks are refined, our understanding of users and products becomes clearer. Then, the Task Scheduler (plan) is used to reorganize the subtasks to outline the user's actual operation process.
When designing a brand new product, hierarchical task analysis allows you to explore the different ways in which users can accomplish the same tasks. The design needs to be able to meet the behavioral paths of these users.
For existing products, hierarchical task analysis can help you optimize interactive design, making them more natural and humane.

　

Project Combat
for the sake of understanding, here is an example. Assuming there are no competing products, we will design an online bookstore through the user's mission analysis.

Using simple task Analysis
1, the user's goal: to buy a book.
2. Task Analysis
According to the user's behavior in life and Internet characteristics, the user's task analysis is as follows:

　
3, low-fidelity design Draft

　
In order to allow users to complete the task of selecting books, designers refer to the physical bookstore for the way books are displayed. The design is as follows:
Can users really find the books they want? Think again. The person who goes to the bookstore to buy books can be divided into two categories:
The first category of users, very clear to buy their own books. In life, they usually go straight to a specific area to find the book they want, or ask the clerk directly; the second type of user is unsure of the book they are buying. In life, they would wander around the bookstore. Interested in the book, you will buy.
Depending on the two categories of users mentioned earlier, there may be some new understanding of the user's choice of books.

　

Use Hierarchy Task Analysis
1, the user's goal: to buy a book.
2. Task Analysis

We try to use hierarchical task analysis.
In task analysis, we can combine one or more subtasks to describe the actual operating process of the user in the system through a task plan. In reality, the execution of a user's task cannot be carried out exactly in a numbered order. In order to ensure the flexibility of analysis, the task is disassembled through the hierarchy, then the task is reorganized by the task plan to sketch the actual operation process of the user.
The user's main task is to order books. In order to complete this task, the user's task is scheduled to: Pick the book-> fill out the Harvest address-> Select Payment Method-> Submit order-> complete payment.
Hierarchical task analysis allows you to explore the different ways in which users can accomplish the same tasks. We disassemble the subtasks. Here, for example, select a book.
For browsing books, sifting through books, and searching for book subtasks, users can execute one or more of them at will, and the order of execution is not unique. The task of the user who picks the book is scheduled to:
A. Browse books-> selected books.
B. Browse Books-> Search Books-> selected books.
C. Screening books-> Search books-> Screening books-> selected books
D.......
Since subtasks are not simple sequential execution processes, it is necessary to consider making it easier to move between subtasks in order to meet this type of task scheduling.

3, low-fidelity design Draft

The design manuscript can meet the different types of users for browsing, filtering, searching, any combination of these subtasks. The design draft is intended for illustrative purposes only.
This design draft, I believe you can feel that has been and the current mainstream online bookstore to select the function of the book is very close. What is missing is some business thinking and operation.

　

Continue to refine
as subtasks continue to break down, they will soon be able to find the user's actual operating process on the interface.

Task analysis: Continue to disassemble the search task.

Based on this level of subtasks, we will be very relaxed when making storyboard. Of course, its better application is to compare the actual user's operation path to the current task schedule after the product prototype has been completed. By comparison, it is easier to identify the points that can be optimized.

　

Written in the last
The purpose of this article is to introduce the use of hierarchical task analysis in the project, so that we can think more carefully to users and products. Hierarchical task analysis focuses on the tasks that can be observed and compiled in the work, and largely ignores external factors such as integration of individual/team knowledge, skills and attitudes. Another, cognitive task analysis just make up for this deficiency.
To simplify the description, the examples in this article are only indicative, branching, and abnormal tasks have been hidden away. I hope the examples in this article will inspire the readers.