Shopping Cart Change Case analysis: An effective design plan

Article Description: in a scenario design, there is a situation where all possible scenarios appear to have been exported, but are not satisfied when the discussion is finalized, and think that there should be more optimal output? What causes this situation? How to output an effective design plan?

In a scenario design, there is a situation where all possible scenarios appear to have been exported, but are not satisfied when the discussion is finalized, and think that there should be more optimal output? What causes this situation? How to output an effective design plan?

What is an effective design plan?

"Effective programmes", and personal understanding is "a programme that achieves the desired objectives", rather than a list of "all possible scenarios". The design is different in different stages because of different direction and ability, but when these premises are consistent, the scheme should be logical and unique, and there should be no ambiguous output.

How to output an effective design plan?

The core: logical, justified output

STEP1 Determine product objectives

Each product has its goal, this link is extremely important, after determining clearly, in the next design decision, will play the role of the direction of judgment. Product objectives must be discussed with the product side to determine, do not give a reasonable judgment. Take the Ishun shopping cart as an example, its core goal is to let the user "quick order", the second is "buy more".

STEP2 Determine user group division

With clear product objectives, we need to have an understanding of the user's behavior on the product to know what they need. The following points need to be paid attention to:

① What type of user (scale, primary/secondary role)
② different types of users will use your products to do

Also take the shopping cart as an example, Ishun is primarily a billing user (the main role-the shopping cart as a basket for determining what to Buy), followed by the collection (auxiliary role – the aggregation of a shopping cart as a possible purchase, and the need to add or delete goods).

STEP3 user + strategy → divergence design point

That is, to brain burst, which points can effectively meet user needs and achieve product objectives, the steps are as follows:

① from user requirements (note that primary/secondary roles are identified)
② thinking, under the premise of the existence of demand, how to better achieve the goal
(such as shopping cart analysis, will consider the user in the case of a single demand, how to better achieve a quick order; instead of saying that because the product wants users to quickly place a single, they weaken or do not give a single demand)
③ examines design points, focuses on the needs of key players, and meets the needs of secondary roles without impacting their experience

The three steps should be discussed with the product manager to determine, agree upon, and then design

STEP4 design Phase

This is what we are doing every day ~ here do not do detailed instructions, the need to gradually accumulate experience

STEP5 Program Test

User testing is the most direct way to test the design results, especially the design of the operation. Professional with the research colleagues will help you to get the test, but need to communicate some points before:

① The purpose of the revision, the key design point is what; there are many plans to explain the characteristics of the program (with the research colleagues must first know how to use this thing)
③ you want to know the psychology of the user in the course of the operation (such as whether or not some copy will not understand)
③ with the research plan output, again confirm the test point is comprehensive, can solve the design confusion

Of course, you also need to give a test demo, Visual manuscript + clickable prototype is the most perfect, time is compact best or output an interactive + clickable prototype bar. Prototype content as much as possible to ensure authenticity (such as shopping cart with real goods, real prices, real activities).

STEP6 final

According to the results of the study, the manuscript is finally optimized and submitted. The programme descriptions and user feedback are also attached.
At the review meeting, when the product side challenges the design point, we can review the product objectives and the user requirements phase of the conclusions, explain why the present design.

Some principles

In the shopping cart revision, the summary of some principles is shared as follows

1 do not easily change the results of user actions

Do not let the user feel that you have moved its things, such as shopping cart merchandise list should be based on the order of the user to add the reverse sequence, and do not deliberately distinguish between the goods and no goods to disrupt the sequential. In the design of this shopping cart, due to the coexistence of activities and package relationships, there is a contradiction between the display of the package included in the product or the activity contains merchandise (pictured below), the two methods for the shopping cart page is each have advantages and disadvantages, at that time also put forward "users are more concerned about what the question", but in fact, users will care about, It's hard to weigh the weight of a weight. Actually jump to think about it, the package is added to the shopping cart, the user is regarded as a whole, should not be separated.

2 user operation results should be in the vicinity of the operating area to give timely feedback

The operation feedback should be displayed in the user's operation area of concern, and the link should be positioned to the change area. If you click on the Checkout button, there is no goods, then the button area feedback no goods, and the link to locate the goods line.

3 The revocation function is superior to the two confirmation operation (under the non-critical process)

Two times confirmed in some cases will be due to user inertia operation, can not prevent misoperation effect. And given the revocation function, a different form, one can prevent inertia operation, on the other hand, can reduce the cost of operation and thinking. such as the shopping cart deletion function (as shown below).

Original link: http://ecd.tencent.com/design-proposals.html