Product design process: Details of the various links in the in-depth summary

Article Description: This article first summed up the product design process, as well as the process of understanding each link, in the future article, but also each link in the details of the in-depth summary, so as to achieve systematic carding their own cognitive system.

recently something happened, and prompted himself to calm down the work of these years of precipitation and knowledge accumulation to do a systematic summary and sharing. The main hope is that by summing up, deepen their understanding of the control of products, strengthen the specific details of each link, and by sharing with many people to test and review their own design products, further discover their own capacity deficiencies and ideological loopholes, and further enhance their ability.

This article first summed up the product design process, as well as the process of understanding each link, in the future article, but also each link in the details of the in-depth summary, so as to achieve systematic carding their own cognitive system.

The image above is based on their own knowledge of the product to draw the flow chart, in my understanding, product production is divided into three stages:

1. Demand research:

Through face-to-face interviews, collection of demand cards and other means, conduct intensive research, collect and summarize some of the problems or suggestions that they have encountered in their work or daily life, identify the common parts of them, summarize them as a requirement, and ultimately select one of them as the core issue. And the function of solving this core problem will be the foundation of future product survival.

2. Product establishment and research and development

According to the user's core needs, put forward the product idea, and do the corresponding market investigation and feasibility analysis. After the decision by the decision-making level, the idea will be refined into a product prototype, submitted to the ued and research and development departments, to produce the corresponding products and put into the market.

3. Product Marketing:

The business department according to the product set target user groups, packaging and publicity of products, in the completion of sales tasks, together with product managers to actively collect user feedback, to assist product managers to correct and iterative products, to maintain product and market synchronization.

Product design and research and development, can be subdivided into five stages:

1. Product Project : mainly including business requirements document (BRD), market demand document (MRD) and Product requirements document (PRD) production, through BRD access to resource support, MRD to verify the product vision, PRD submit product model to ensure the feasibility and operability of product solutions.
2. Product development: Including the design of user experience and the implementation of specific functions.
3. Product testing: Through a number of tests to ensure product quality, timely detection of product bugs, accelerate the product iteration.
4. Product Online: After the product through the online review, notify and coordinate the relevant departments to complete the product line work.
5. Product Operations: Assist product Manager to output related product documentation, and plan related marketing activities with Product manager.

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

In fact, engineering, this model is a typical "waterfall model":

The advantage is:

1. Each stage is clearly divided into the next phase will not be the last stage of the task of the burden.
2. It is very suitable to use this flow to increase the iteration of the product;

The downside is:

1. Frequent changes in demand can be painful;
2. Each phase is a serial connection, version-span control is not good, will often appear ued busy dying, research and development is busy, the time to die, ued very busy situation, the team utilization is not high;
3. The most serious is if the project did not set up, or set the wrong direction, basically dead.

Because they do more of their own products, demand for their own control, and most of the requirements of rapid iterations, so the individual feel that this research and development model, is very suitable for the development of Internet products, these years have been using such a routine in the development of products, but also used conveniently, compared to the previous in Founderrd, The company uses the CMM3 standard, the individual biggest feeling is: Agile.

Therefore, if the control of the project, the demand is not controlled by their own, and high quality requirements (such as banking or telecommunications products), I believe that the flow will not be suitable for your current products or projects.

Today summed up here, and then go on their own on the various aspects of some of the cognition and experience, more in-depth and detailed summary, I hope to be able to at least a day to maintain a review and summary.