Shulou(Shulou.com)05/31 Report--

In this issue, the editor will bring you about how to write a good PRD. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

Overview of practical information

How to write a good PRD perspective to help product managers improve their professional competence.

PRD writing is not only an important work of product managers, but also the core embodiment of professional competence.

First, let's take a look at the problems that often arise in PRD.

The first big problem in Q1: incomplete information

Lack of project background, product objectives and other information, easy to let people see in the clouds.

The second biggest problem of Q2: unclear logic

There is no complete product process, the logic is not clear, the front and rear do not match, or enter a product dead end.

The third problem of Q3: expressing ambiguity

The expression of words is not accurate and there are many kinds of meanings.

The fourth problem of Q4: high cost of reading

Text redundancy, lack of product flow chart, basic interaction diagram and other visual expression.

So how to solve these problems?

First of all, make it clear what PRD is and what is the purpose of PRD?

Q what is PRD?

A documentation of product manager's design ideas, design plans and product details. It is the most important document in the product project, from the "conceptualization" stage to the "graphic paper" stage.

What is the purpose of Q PRD?

A product manager product design ideas, specific plans, details of the carrier, the core goal is to convey product design information to different roles. These roles include developers, tests, project managers, interaction designers, operations, and other business people. Developers can learn the logic of the whole product according to PRD, tests can build use cases according to PRD, project managers can split work packages according to PRD and assign developers, and interaction designers can design interaction details through PRD.

Then, make clear what kind of PRD is a good PRD?

Q what kind of PRD is a good PRD?

According to the definition and function analysis of PRD, PRD is not only the basis for multiple roles to obtain product information, but also the standard for them to carry out their corresponding work.

Then a good PRD must have complete information, clear thinking, no ambiguity, and easy to read. In order to achieve this effect, the writing of PRD is the unity of content (product design ideas) and form (format).

Content: the logic of the product is clear and the text is concise.

In form: the information is comprehensive, standardized, and the information display efficiency is high.

Finally, from a practical point of view, what does a good PRD need to have?

Analyze from two aspects: content and form.

● content-level ● has clear goals

1. What is the pain point for the user / customer?

two。 What is the product demand behind the pain point?

3. The goal must be to address user / customer pain points.

The solution is correct and reasonable.

1. The solution starts to meet the needs.

two。 The solution is executable.

3. The solution is the best way to solve the problem.

The expression should be clear and the words should be refined.

1. Language expression should be accurate and unambiguous.

two。 The main points should be summed up.

3. Keep it simple.

The composition of ● information at the formal level of ● should be comprehensive

1. Need to include project background, product objectives and other project-related information.

two。 Need to include online time, delivery time, each link time expected and other information.

3. Need noun explanation, resource requirements and other information.

The format is clear

1. The style should be clear, the segments should be clear, and the font should be neat.

two。 There is a clear version number, document number.

3. If necessary, including corner marks, notes, etc.

Visual expression

1. Have a global product flow chart.

two。 To give a complete product interface.

3. The product process should be presented in a closed loop.

4. Product details should be covered.

A good PRD is the unity of content and form, which can help the project to move forward better, and can help each role in the project to better understand the background and design ideas of the product. It is hoped that every product manager can master the writing skills of PRD.

The above is the editor for you to share how to write a good PRD, if you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.