Generally, an Internet product project team consists of technical personnel, product personnel, and operation personnel.
Based on my previous experience, I have conceived a project team communication framework. The specific process of the Framework is as follows:
After user research, requirement analysis, and product planning, product personnel should come up with the prototype of the product as soon as possible to discuss with the project team, and listen to the opinions and suggestions of technicians and operators. To further improve the product design. After the product design is finalized, a "product meeting" will be held to present the product design and hand it over to the technical staff for development. Meanwhile, the operators will formulate corresponding operation strategies based on the product characteristics.
Technical Personnel adopt iterative development and do not accept new requirements during the iteration period. In the product development process, you can use the task board to report the development progress to the project team. After an iteration ends, the technician needs to hold a "product demo meeting" to present the functions completed in this iteration to the product personnel and operation personnel. After that, the technical staff organized the product to go online. Operators start to implement product operations.
During the operation process, operators need to collect user feedback and hold regular "Operation meetings" to report operation data to the project team, such as the number of registered users, PV values, and UV values. At the same time, we should report the collected user feedback to the project team. After the product personnel receive user feedback, they should conduct corresponding research to continue to improve the product.
In this way, the formation of a sound flow of information ring.
Advantages of this model:
- Transparent and good information circulation. All communications are completed through face-to-face communication to reduce information distortion and improve communication efficiency. There is no "Courier" in the team-the person who coordinates and transmits information of each team, and there is no "information islands ".
- Form a "Product collective responsibility system ". The entire process of product initiation, design, launch, and operation requires the full participation of the project team. Actively mobilize the enthusiasm of every member of the team to make suggestions for the product and create a sense of belonging to the team.
- Effective collaboration and fast execution. This model emphasizes "feedback ". Efficient feedback helps the team make adjustments as soon as possible and evolve products during continuous iteration.
Communication Model diagram:
