The core function of PRD is to clarify the functions to be implemented by the product manager, and at the same time, to synchronize the information of the bulk sms service participants, and ultimately reduce the cost of communication. Why write this article? It is said that the requirements must be standardized, so what is the specification and detail? And there are very few suitable templates on the market. It is very time-consuming to lay out every detail point by oneself. If the details are not detailed, the project members will not be able to understand it, which will easily lead to bulk sms service misunderstanding. Product managers need to pay attention to their own plans and the first time project team members understand the situation after reading the documentation.
If project members have cognitive biases about the specific implementation plan, it is equivalent to digging a hole for themselves. Therefore, in order for the bulk sms service project to develop as expected, we need to establish internal team norms to help project members establish cognitive consistency, The pits I have encountered, because some specifications are not clearly written (such as sorting), which lead to the rejection of requirements. Finally, after spending time discussing with the team, and finally extracting a "B-side PRD Requirements Specification", the entire team's needs bulk sms service understanding, tacit understanding and work efficiency have been greatly improved. Based on the above, I will share the methodology I have sorted out. Although it is not necessarily correct, I hope it will be helpful to some newcomers.
Attached is the "B-side PRD Requirements Specification" that I understand. 1. Demand structure of B-end products Description: The demand design of the B-side is more to serve the "process" and focus on scalability. And experience and efficiency bulk sms service are not at the heart of the design. 1. File name: project name + version number. The version format: major version number. minor version number. revision number, such as "Withdrawal Requirements V1.0.0" 2. B-side requirements bulk sms service document elements 1) Change records Record change history for easy tracking 2) Demand background, demand goals, product value Emphasize the pain points of the demand, explain clearly why this demand is needed now, what effect this demand will achieve, and what the value of this product will bring.