How products from larger projects work

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. Product work experience for larger projects [top]

In the project

2. Change of Requirement

The requirements change is a situation that every programmer, Product manager, designer, etc. will encounter. The product manager is not a god, and the project team cannot be invincible to withstand any external influences.

What should product managers do when faced with having to change their needs? Here are four personal tips:

A, active treatment. Often, when a design becomes more complete, people tend to adjust locally rather than redesign it. When a requirement has to be adjusted for well-known reasons, the first thing to do as a product manager is to actively face the problem and actively deal with it.

Project development is often a stressful process, every half-day or even every few hours there are several functional point development completed, when a demand change to communicate the "delay", the change to the normal process of the project "destructive" will be more.

B. Keep communication. "It's easy to talk, it's hard to communicate. A lot of things are useless unless the other person wants to understand. So, most of the time, communication is a process of struggle. The requirements change will directly affect the next process, the product manager needs to change the requirements of the details and reasons to the relevant personnel, including visual, front-end, procedures, testing and so on.

This is a very painful process for many product managers, because it is likely to be criticized and coldly, Japan has a etiquette principle is "Don't give others trouble", but in the project, this is unavoidable.

Personally think that all the barriers to communication from the idea of the unity, if we feel that this need to change is a waste of time, then communication is unavoidable. The project is not such a calculation, requirements since the change must have a purpose, product managers need to explain this reason, do not make changes or save communication time caused by rework, the consequences are often more serious.

C, update the document. is still convenient for the next process, product managers are often not only responsible for a project, the timely updating of documents and revision of the document version number can also facilitate future viewing. In addition, the document is not omnipotent, updating the document is necessary, not an end, do not just leave some text to others, it seems to say that "change, others do not ask", is irresponsible attitude.

D, walk the good flow. Each company's requirements change process is not the same, the process is for the project better, do not consider as cumbersome, the process is unreasonable can put forward their own suggestions, and bypass the process will be to shirk the responsibility to bury the hidden dangers.

3, before the line preparation

In the beginning of contact with the product work, for a product line has been stuck in the "demand-design-development-test-on-line" simple process model, the actual operation to find that there is actually a lot more.

These work mainly include:

A, data preparation: The data used in the product (page content) needs to be prepared in advance. For example, a channel page on the line, the content of the channel from where? by crawling? Call or background recommendation? If it is a completely new module, you will need to repopulate the data. This work often requires other departments (such as editorial department) with the completion of the product manager needs to do is: 1, in advance to inform the department responsible for the reasonable arrangement of work, 2, set aside sufficient time, at least to ensure that the line before the filling completed;

B, statistical requirements: After the product on-line need to follow the monitoring of the data statistics needs, need to form a document to inform developers. In the product design period controversial, not to grasp the function point, in the design of the effect diagram of the page element design can be recorded in the statistical requirements, so that the later better analysis of user behavior for the next iteration of the product and the need to provide data basis for the increase or decrease.

C, Advertising position: page advertising changes, need to be in the product design period and sales, marketing departments to communicate, and before the product on line again confirmed. Advertising position adjustment in product design is unavoidable, in order to better ensure the interests of customers, the need to listen to sales and marketing departments of the recommendations. Before the product on line need to reorganize the advertising resources to deliver the graphic design, and replace on the page.

D, product promotion: belong to the scope of product operation, products and operations in the work of the collision more, now many companies simply will be a part of the two, this is something. Here wants to say is, the product on-line necessary on-line (revision) announcement, the commercial soft article, the multi-channel propaganda these basic operation means are not few, the product manager can do the preliminary follow-up, mainly is does the communication and the cooperation.

E, Help content: page Help related content modification. This is primarily a content adjustment similar to the Help center channel, which needs to be considered for recording if it is a video.

After online

Product on line often means that the challenge has just begun, this is not the same as film, after tight shelomith drum carefully planned, a commercial blockbuster finally online. The audience looked at the angry and scolded that is the audience, anyway can make a bowl overflowing.

Product design is more like a target shooting process, user demand is the bull's-eye, each product revision is in the pull trigger, we need to do is--shooting, and then look at how much, constantly adjust, and strive to the next hit the bull's eye.

Yes, the product line means that the war is starting again and there is no chance of stopping. and return to user needs, experience, continue to invest in the next project bar. Finish]

Product work experience for larger projects [top]: http://www.yixieshi.com/pd/7202.html