First of all, let's look at the user role of PRD: mainly developers, who want to see "concise and easy to understand" product requirements documents in busy development tasks.
Combing the functions of the Pearl River Delta;
Communicate product requirements;
Manage and record the product iteration process;
All departments * * * enjoy product information to promote communication;
So the principle of a good Pearl River Delta is:
Clear structure
This language is concise and easy to understand.
Real-time * * *
What exactly should I do?
The answer is simple-a Pearl River Delta document is enough.
Nowadays, more and more product managers combine text description and prototype into a PRD document, because the previous word+ prototype method is cumbersome to manage and easy to cause information omission.
It is an ideal state to unify the prototype and text description and share a link directly so that developers can see all the information.
Multi-level navigation structure displays Pearl River Delta information
Generally speaking, product requirements documents include product overview, flow chart, functional details and prototypes, global description and non-functional requirements.
How to present these contents clearly and methodically in a document? Use a multi-level navigation structure just like a web page.
1. Product Overview The product overview section is used to display the document revision history, version description, development cycle and product introduction.
"Document Revision History" is used by product managers to record the revision status of PRD documents, and it is also convenient for members to know whether PRD has changed in time;
"Version Description" shows the core functions of each version of online products;
The "development cycle" is used to sort out the expected start and end dates of development, testing and online.
Product introduction is used to record product name, introduction, user portrait, usage scenario, product positioning and so on.
(Version information module in ink knife "PRD template A", Xiaolong)
2. Flowchart Flowchart is the product manager's thinking map of combing product logic and function. Generally, there are "functional structure diagram", "information structure diagram" and "task flow diagram".
The functional structure diagram shows the functional modules of the product, and generally expands the smallest unit visible to users.
The "information structure diagram" takes information as the dimension to describe which data fields can be used to display user information/behavior information, etc.
"Flowchart" records the path of users using products, and it is also a circuit diagram of products, showing all the pages of products and their corresponding relationships, which is helpful for product understanding.
(Structure diagram module in Xiaolong's ink knife "PRD template A")
3. Functional details and prototypes This module is the module that developers view most frequently. At present, a fast and efficient presentation method is "prototype"+"annotation".
Graphic and text complement each other, and information that can't be conveyed by pictures can be clearly supplemented by words, such as some use logic of products, which is convenient for colleagues to understand.
If you use an ink knife, you can create a large canvas, then paste the prototype page made by the ink knife into the canvas, add text notes, and add some descriptions of boundary conditions at key positions.
Or, add comments directly to the product prototype project through "Comments".
(The "interactive prototype" module in "PRD template A" is directly embedded in the ink knife prototype, which is completed by Xiaolong)
4. Global Description This page is used to display the design specifications of the whole product, and some general rules can be attached here.
To this end, the convenience of using ink knife production lies in:
You can directly graft prototype projects related to design specifications through web links, or click "Label" to view the details of each element.
(The "Global Description" module in the ink knife "PRD Template A", Xiaolong)
5. Non-functional requirements For different types of products, non-functional requirements will vary, generally involving:
performance requirement
system requirements
operation requirement
Security requirements
Statistical demand
Financial demand
……
This part should be adjusted as needed.
abstract
As an important internal communication document, PRD can collect necessary information with a clear logical structure, which is an advantage for improving work efficiency. The conciseness and understandability of language, combined with visual structural diagrams and prototypes, are all aimed at enhancing readability and making communication more efficient.
It is not a waste of time to polish the Pearl River Delta as a small product. Good PRD documents can be used for a long time.
Ink cutter has newly developed two product requirement document templates. The page content, navigation and interaction at all levels in these two PRD are designed for everyone.
Now you can click "Create Project", select "Product Requirements Document A" or "Product Requirements Document B" from the ink knife template, click "Use Template", and then make some modifications according to your own product requirements.
Through the sharing link of ink knife, employees in the company can directly synchronize the update of PRD online in real time, without worrying about information lag or incompatible documents.
Let's start creating or optimizing your product requirements document ~
Hope to adopt! thank you
The picture comes from? Screenshot of "Operation and Maintenance School" and Ink Knife official website