How to control the product - the whole process of product analysis

Something has happened recently, prompting one to stop and systematically summarize and share the accumulation of work and accumulation of knowledge during these years. Mainly hope that through the summary, deepen their understanding of the product control cognitive, strengthen all aspects of the specific details, and by sharing with many people to test and review their own design of the product, to further find their own capacity deficiencies And ideological loopholes to further enhance their ability.

This article first summarizes their own product design process, as well as the process of understanding all aspects of the process, in future articles, but also one by one all the details of each link in-depth summary, so as to systematically sort out their own cognitive system purpose.

The picture above is based on my own understanding of the product flow chart drawn in my knowledge, the product is mainly divided into three stages:

1. Demand research:

Through face-to-face interviews, collecting demand cards, etc., intensive research is conducted on users of a certain type or industry to collect and summarize some of the problems or suggestions they meet in work or daily life to find out the common parts , Summed up as a certain demand, and ultimately selected as one of the core issues, and to solve this core issue of the function, will be the basis for future product survival.

2. Product project and research and development

According to the user's core needs, put forward product ideas, and make the appropriate market research and feasibility analysis. After passing the decision of the decision-making level, the idea is refined into a prototype of the product and submitted to the UED and R & D department to produce the corresponding product and to put it on the market.

3 product market:

The commerce department packs and publicizes the products according to the target user groups set by the products. At the same time, the sales department actively collects user feedback together with the product manager to assist the product manager to correct and iterate the products so as to keep the products and the market in step with each other.

One product design and development, but also can be subdivided into five stages:

Product Establishment: Mainly including the preparation of BRDs, MRDs and PRDs, resource support through BRDs, MRD verification of product ideas, PRD submission of product models to ensure the feasibility of product solutions And maneuverability. Product Development: Including the design of user experience and the realization of specific functions. Product testing: Through some testing, to ensure product quality, timely detection of product BUG, ​​accelerate product iteration. Product on-line: After the product passed the on-line assessment, notice and coordination of related departments to complete the product on-line work. Product Operations: Assists the product manager in outputting related product documentation and planning related marketing activities with the product manager.

Someone once asked me why this division of the whole process, the advantages and disadvantages of what?

In fact, this model belongs to the typical "waterfall model":

The benefits are:

Divided into stages very clear, into the next stage will not be the last stage of the burden. It is suitable for using this flow of incremental iteration of the product;

The disadvantages are:

Frequent changes in demand will be very painful; between the stages belong to the serial connection, the version of the span control is not good, it will often appear when UED busy dying, research and development is very busy, research busy busy dying, UED is very busy , The team utilization rate is not high; the most serious is that if the project did not establish a good, or the wrong direction, the basic dead.

Because of their own products to do more, the general demand for their own control, but most require rapid iteration, so personally think that this model of development, is ideal for the development of Internet products, these years have been using such routines in the development of products, It is also used smoothly, compared with the previous FounderRd, the company used the CMM3 standard, the biggest personal feeling is: agile.

So if the control of the project, the demand can not be controlled by themselves, and the high quality requirements (such as banking or telecommunications products), I believe that the transfer will not be suitable for your current products or projects.

Here are the first to summarize here, go on some of their own understanding of each link and experience, more in-depth and detailed summary, I hope I can at least keep one reflection and summary of the article one day.

Source Address: http://www.marscn.net/?p=928