Recently, when reviewing the prototype solutions delivered by other product managers in the team, it is always found that many product students do not have a clear definition Ws Number List and standard for what and how to write a prototype; this also leads to the inevitable in the development process. The developer complained: "I did it according to the prototype" - but because the prototype itself did not clearly define the corresponding functional description, the final launch content was not what the Ws Number List product manager originally wanted. In order to standardize the prototyping specifications of product students,
I have sorted out 4 major prototyping principles. As long as you fill in the prototype content according to these principles, you can ensure that you can write a prototype plan Ws Number List that allows developers to silently praise the "brilliant" in their hearts. 1. Analysis of the product prototype itself Before introducing the design principles of product prototypes, let me analyze the prototype itself. According to the formula of requirement analysis, a complete requirement is composed of target Ws Number List users , usage scenarios and the goals that users want to accomplish in this scenario . Then the requirement of product prototype includes the following usage scenarios: 1. Weak usage scenarios a.
The product manager gives the corresponding solution after receiving the needs of the operation, and uses the prototype form to determine whether the solution can Ws Number List meet the operation's vision; b. After completing the overall product plan, report to the superior leaders to confirm whether the leaders agree with the overall plan design ideas or details. 2. Strong usage scenarios a. The product manager conducts demand presentations to developers, testers, and designers based Ws Number List on product prototypes at the demand presentation meeting, so that all project members have a general understanding of the requirements;