Some basic elements of the product requirements document (PRD)

Article Description: write the eight elements of the PRD document.

1.1 Purpose (Product vision)

Must have a deep understanding of the issues that the product is to be addressed, and clarify how the product to be developed will meet that requirement.

The product manager should be very clear and precise about what the product is, what it is meant to be, and what it is intended to be, and share the vision with the various roles (bosses, designers, developers, and users) associated with the product.

1.2 Objective (product target)

The product vision defined above is decomposed into the specific experience objectives to be achieved and the acceptance criteria for each subdivision target are clarified, such as:

1.2.1 Fluent without refreshing experience

1.2.2 Design is simple, easy to use, interesting

1.2.3 highly concerned about user privacy

1.3 User (Users role)

1.3.1 Role

After defining the requirements for the product to be resolved, the product manager will work closely with the designer to carry out interviews, widely contact, observe, understand the user, divide it into several types, identify the core target users, enrich the user role, including but not limited to age, gender, computer level, personality characteristics, etc.

1.3.2 Target

The user of each quality must have its clear and clear goal, defining the goals that each role wants to achieve when using the product, will help the product manager to face the needs of the project's role and make the correct value judgment.

1.3.3 Tasks

The demand is relatively stable, the solution is always with the technological revolution, software and hardware mature and change, for the user task design innovation is a good product success key.

Example: Traditional Photoshop has been carrying a powerful filter to help users deal with photo effects, Instagram on the mobile platform more convenient, elegant solution to the demand, to achieve success.

1.4 Principles (Product principle)

Looking around the product development process, each role should be as consistent as possible in the general direction, reduce friction, the focus of the discussion will be focused on the output of better solutions, in advance to develop a product vision based on the values and beliefs extracted, conducive to discussion, such as Facebook's credo:

1.4.1 Completion is more important than perfection (done is better than perfect)

1.4.2 Code wins controversy (arguments)

1.4.2 quick action, breaking stereotypes (move fast and break things)

1.4.3 stay focused, ongoing release (Stay focused and keep shipping)

1.5 Prototype (prototype test)

Paper and pencil prototypes are the best means of visualizing ideas early on, sharing them quickly, bringing together the discussion of the roles of the project, and revising the idea, rather than waiting for the thought to mature. The value of ideas will be highly magnified in the sharing of communication. The high Fidelity prototype can quickly bring the product's experience value to the user.

Feasibility test

Feasibility is the first step in testing ideas, working with technical teams to study technical trends, explore the feasibility or compromise of original ideas, and ensure that the products are addressed in a number of difficult points, early detection and evaluation of the time point is feasible or not.

Usability Testing/Value testing

Work closely with designers to provide a number of design options for different types of users, to verify the usability of the prototypes, to meet the original design ideas, to uncover missing requirements, and to gain valuable feedback.

In addition to technical feasibility and availability, using High-fidelity prototypes or simple demo can also test the user's thirst for the product, and whether there is a desire to buy, everything is a serious test personnel to observe, record the feelings of the user, surprise, disappointment, or callous, often difficult to hide.

1.6 Write (writing document)

PRD is undoubtedly the soul of all product documents, carrying the communication mission of each role's information equivalence. It is generally in the form of word, there are also in the PPT, the project whiteboard, the important thing is the content, not the external media, to ensure that your team members can easily get it, and timely update.

1.7 Prioritize (priority)

Products often have a large number of functional points, a clear product needs to enter the market point of time, and the release of the function of the priority to define and sort, is the product manager of the most valuable work. Dividing the story in each iteration version into Must-have,high-want,nice to have helps to understand more clearly the mission of each phase of the product.

1.8 Test (Review PRD)

With the development of the design and development, the release of PRD should be continuously updated, throughout the whole developing process, to ensure that all team members understand the document fully, clear the focus of their respective areas of concern, according to the role of the feedback and discussion, timely update the document.

PS: Part of the content from the "Book of Revelation" and SVPG, reprinted to indicate the source.