Skip to content

Based on the product manager must know how to write PRD documents

Author: Gong Yu man

PRD is the product requirements document, is a description of the needs of the product, including the main content of the product functionality and performance. PRD is the most important document that must be identified before the project starts.

write PRD documents, in fact, is a product business needs analysis process, the logic is as follows:

1, product structure

product is composed of function and content, these functions and content, in some way, the composition of the channel / module, and ultimately the formation of the overall structure of the product. Here only a part of the product structure:


product structure in general through the MindManger comb.

2, analysis of core business processes

analysis and sort out the core business processes, can help project members understand product logic. The role involves multiple business processes, you can use the lane map, a single role can use common activity diagram. In addition, in the analysis of business processes, but also can be used in conjunction with the state diagram and sequence diagram, the specific use of what tools, depending on the situation, the key is to sort out the clear logic. Here is a part of the interception of the lane map:


3, analysis and use case

this step is a more specific step, the first two steps is to determine the scope and process, and this step is to do a specific description of a function. There are two ways: use case description and function point description. The difference between the two is that the description is different, the use case is described from the person and the system of the spectator, and the functional point is described from the product point of view. Through the use case to describe the requirements, it is best to use a unified template to describe, and functional description only in the form of comments in Axure can be described.


on how to describe the demand, there is no right way, only the most appropriate way, this varies from person to person.

4, analyze and organize non functional requirements

non functional requirements involving more widely, such as performance requirements, access speed, how many people can simultaneously access the maximum support; such as design requirements, products should be designed into a small fresh style or mature style; but also such as statistical demand, product statistics which words, which form report.

5, organize the requirements document and review

after the completion of the above 4 steps, in fact, the logic of the entire product has been very clear, then you can summarize the requirements document. After the project and the relevant person in charge of the review, review and approval, you can enter the implementation phase of the product. The implementation is generally done by the project manager, but it is

Comments are closed.

Leave a Reply

Your email address will not be published. Required fields are marked *