Task flow--skeleton of product design

I have been exposed to such an E-commerce products: the function of a large, complex business logic, but the requirements of the document detailed and thoughtful. After the development of the product also proved to be able to use, there is no bug, then ready to go online immediately. However, at this time, the product was suddenly rejected by the leadership and discontinued development, why?

The leader's opinion is simple: the user experience is too bad. Indeed, I read a Half-day page, also did not understand how to use, do not know which to point, after the point which, in front of me is a lot of scratching the head of the function. The reason for this is that the design is missing an important step-task process design.

In general, http://www.aliyun.com/zixun/aggregation/6579.html "> Users have a clear purpose for using this product (unlike browsing news sites), then you must give the user proper guidance on the page, Enables users to quickly complete tasks. Of course, before completing the task, the user may also take some detours (such as collecting first, or recharge first, etc.). In fact, designing this kind of product is like designing a maze, there are many lines, but only one main line leads to the end point. And the design of the maze, like the first design that main line, and then calmly design the spur, the context is clear, in order to correctly structure the entire product function and content.

The design main Line (main behavior flow) is the chaotic function point according to the user's expectations and goals in the right order to organize the process, tell users what to do first, and then do what. If you don't have a task flow chart, it's like putting all your routes together, then the user may never get out.

Whether to design a feeder (secondary behavior flow), to see if the user can complete the main behavior flow is necessary to help (the smaller the maze, the lower the overall complexity, the more help users to complete the task quickly, too much).

The product of the planning and development team's mind may be this:

Like this maze, product function emissions are disorganized, without primary and secondary, successively. Because they are too familiar with the functionality and business logic, each place will be able to quickly determine the next step by the environment, all the functions and operations alike.

And the product that the user expects is this:

Users hope that without thinking, they can successfully complete the task through guidance.
So what is the product of the interaction designer's eye?

The interaction designer must understand the intention of the planning team and think from the user's point of view. The key point is to determine the main behavior flow. Determined the main behavior flow, we can take this as a clue, to clarify the idea, and then planning the overall interface design products.

In a word, planning a product, from the whole to the local, from abstract to concrete, is not wrong. And if you don't go through the whole plan, what will you do directly from the details?

Those who do not pay attention to the whole and want to do well are bound to be prematurely confined to the details. Such consequences are nothing more than elephant. If everyone in the team is in this situation, the consequences are even worse. This is the reason why people often express their opinions but have no result at the meeting.

Another consequence: too much attention to functional details, resulting in bloated products, the concept of complex, and added a lot of unnecessary exports. In fact, the overall structure is clear, the user only with navigation and appropriate guidance can successfully complete a variety of operations, without the need for a variety of such as "life-saving straw" like the complex export. Otherwise, the product becomes mess. For a maze, each connection to a road or an additional path may increase the complexity of the maze exponentially.
Hopefully this kind of thing will never happen again, but if it happens, ask the interaction designer to come forward and meet the challenge bravely.

Why need interactive Designer (Why)

Interactive designers can understand the business based on the user's point of view, the complex obscure business logic needs to "translate" into user-friendly interface, and ultimately guide users to complete the task quickly, so that the planners and users happy.

What interaction designers need to do (What)

Understand website requirements and user goals

Understanding functionality and business logic

Design Task Flow

Design Information Architecture

Make a page prototype

What interaction designers need to do (how)

Later will write a separate Bovinlai detailed description, please pay attention to ...

Comprehensive:

A competent interaction designer is not blind to meet the needs of users, but to guide users to do to the enterprise and users themselves are beneficial and the most important things, at the same time to bring users a good experience, to achieve a "double win" situation.

On this basis, like design maze to design task flow, on the page targeted to guide users, leading users to quickly complete the enterprise and the user both sides expect to complete the task. The task process is like a product skeleton, supporting the entire product, is a step that can not be omitted.

Source: Source Address: http://blog.sina.com.cn/s ... 0100rto9.html