In the same way, problems in the business email list subsequent development process may be product-oriented/technology-oriented/business-oriented. If there is operation/business participation in the review, they should also play a certain role in program evaluation.
The test involves a full-requirement test, and the understanding of the entire product/technology is quite deep. If the positive team test students have any objections in the review, they should also raise it.
In general, products and technologies that have problems in the development process need to be introspected and improved the most.
It is difficult to sort out the requirements in one step, and there may be omissions in any link. It is also normal to have problems when drawing a prototype. The prototype itself is a product and needs to be iterated.
What a product manager has to do is to make trial and error step by step, iterate quickly, and reduce the probability of errors.
What do you want to say about the question "When drawing prototypes, many usage scenarios are often missed, how to improve them?" Let's chat together~
The function of the product requires the permission to call the system, and some mobile phone brands have strict restrictions on the permission, so some functions may not be available after installation.
For example, our product needs to call the camera permission, and Xiaomi disables this permission by default in third-party applications, so many Xiaomi users report that they cannot take pictures. Later, we added a prompt pop-up box when the permission is disabled to guide the user to enable the permission in the settings.