Product work for larger projects

Author: Water Bird

Recently done a project from the requirements analysis to the line stretches for four months, which is currently taking over the most complex function points, the most product lines of a project. Some of the experience gained from the design of larger products, take out to share with you.

Before the project

1, unified element design needs to consider comprehensive

Perhaps the cause of the start-up team, I have to lament the team's strict requirements of the Product manager, the project is only one person responsible for the whole process, so large to the product line docking, small to a hint of the location and display form need one by one scrutiny.

What elements should be unified?

A, the hint aspect: the Unification operation success/failure prompt, the Unified window form, prompts the language to adopt the more unified sentence pattern, the friendly reminder for the empty condition, the overflow situation friendly reminder, forms the real-time verification reminder form and so on.

B, writing aspects: whether there is a unified paragraph before "·" Unified link State, unified font, spacing, line of higher.

C, Picture aspects: The unified size of the picture transfer, if it is the operation of the upload picture class, you need to consider the full station of the transfer, and consider whether the unified preview of the size of the map.

D, detail Interaction: Inactive button to do "gray" processing (for example, the user does not check the information when the bulk Delete button is not available); button click on the state of Unity (for example, to increase the "submitted in" button state, to prevent the network slow user mad Point a button situation);

There may be friends who say that there are some things an interaction designer needs to do, but I've always thought that being a product manager is not bad. These "unification" can also be used in the acceptance phase, knowing that even a pixel can change the feeling of the whole product.

2, the original function of the fate

I've always felt it harder to upgrade existing products than to develop new ones. This is like growing plants, the new plant a tree just need to choose the right land, and then dig a pit to continue, however, the long-term to the disease, such as the top of the pruning of the energy consumption is often more.

Improving existing products often requires facing one of the most intractable problems: the original function is to stay?

The original function removed words will affect the use of some users? Is it necessary to inform the user in a friendly manner, such as announcement, station letter, interface Guide and so on? How to minimize the harm to users?

Can the original function be optimized and perfected? What kind of voice did you hear from the user group? Do you want to make adjustments in this upgrade?

When these problems are received, the product manager should be considerate. Special attention is, if this product is not the design of their own, then it is best to find PRD description of the document carefully studied again, to grasp the function point to find the original responsible for confirmation, after all, the seedlings are TA pick, do not put the best results in the future of the branches to chop.

3, product line upstream and downstream docking

Yesterday, chatting with friends Taobao Strong place, is the product and product tightly kneading, line, cross platform Cross-industry formed an intricate, deep-rooted foundation, can not be shaken.

So grasp the product line downstream and product surrounding is very important, even if a seemingly simple news display page changes will involve the editing background, advertising management, help Center, even access statistics, data requirements change.

This requires the product design before the start, the product needs to "uproot", carefully comb the relevant context, if the product line is long enough, a clear product line structure diagram is necessary.

In the project

1, the project period from the related product line adjustment influence

The adjustment of the related product line during the project is the last thing I want to encounter, it is like you are on the road to the destination high speed, it is almost to the end, suddenly a person told you: you go the wrong way.

There is a generic module in the project, product design to half, the general module has been changed; there is a process in the project, the product is half done, the process is abandoned; the most deadly thing is that the project has been developed, you have to bite the bullet and say to the programmer: "Because of some irresistible reasons, this demand we do." ”

For a long time project, this situation is difficult to avoid, the reasons for the private summary of three:

A, serious experience problems: for example, a process by a large number of users dissatisfied, in order to prevent users from losing, have to do a temporary adjustment, and unfortunately, you are also using this process.

B, the impact of related projects: including parallel projects and new projects. For example, your colleagues in the design of another product, your products are more involved with each other, so demand analysis did a lot of communication, but one day, colleagues tell you, ta a need to do a temporary adjustment will affect you, how to do?

C, the boss's abrupt decision: no example.

The final solution is three kinds: immediate adjustment, delayed adjustment, no adjustment. The principle of personal treatment is to adjust a situation immediately, discuss the situation of B and C and selectively postpone.

Why would you do that? A situation is to be changed, the time is sooner or later the problem, long pain than short pain, B, c two kinds of situation must sit down and discuss. Need to know why this need to change? Is it a long-term response or an interim decision? Can we postpone, record the demand, and so on? If B, c the demand has not been two days and change, that with your front-end and programmers are too insecure.

This era can patiently read 2000 Chinese characters fewer and less, the larger project product work experience [next] not to be continued, welcome to exchange ...