Everything is a product, a goodProduct ManagerThere's no need to have the ambition to change the world as jobs did, but be sure to have the ability to write good product requirements documentation. For the new product manager is particularly important, so how to improve the ability to write the document?
before sharing a specific document structure, there are two prerequisites for writing:
first, the ultimate goal of the product documentation is to guide design and development and to build a common understanding of the project. So in writing, you have to have a general understanding of the reader's comprehension and knowledge level, as well as the level of understanding of the project, to make sure that everyone can understand. In the context of lean startup, we do not advocate for the record in detail, nor advocate all things only to say a point. This balance is based on the understanding of everyone in the team.
Second, the product documentation is a constantly updated process. At the product concept design stage, there is no way to write the specific requirements and test plan of the design. Early risers the role of documentation is to document the concepts and goals that have been identified, to the end of the product, to understand what to do, to identify user processes and screen details, and to slowly support the entire skeleton of the document. This means that we have to be version controlled.
the company's product documentation contains 10 sections.
1. Product Overview (overview) about three or four sentences to describe what kind of product we will make and why we should do it.
2. Questions and opportunities (problem and overview) describe the issues we need to address through this product, or the opportunities we are looking for. Generally speaking, the purpose of this passage is to let people read and understand why we take the time to do this, and understand the meaning of the matter.
3. Product objectives and Scope
a set of product goals based on smart principles. The most important of these is to define what is the success of the product. This point in the product development of the earlier proposed to have the advantage, slowly will find the basis for all decisions.
The product range defines not only what we decide to take the time to do, but also the functions that we decide to give up. It is clear that these out-of-scope things are also listed to help in future discussions without repeating "so we do not do this?" Do not do that "discussion.
4. Product Demand product requirements refers to a small list of statements written through the user's perspective. For example, "I hope that through this product I can achieve ..." It does not need to contain specific implementation details, nor does it need to write specific interface elements. They are just some of the concrete manifestations of product success.
5. Product principles the principles of design and technology are mentioned in this, such as Facebook's design principles: universal, clean, consistent, useful, etc. Different products will require different principles. For example 2B of some enterprise-class software, security and ease of use is very high principle. For some consumer products, however, interest and innovation may be more important.
6. User Stories
There have been references to user stories that describe the three elements of a user story: Who, what, and why. This is a more straightforward statement. In the eyes of the designer, more scenarios, motivations, user behavior, and ultimately value implementations are considered. So a product in general, will support a number of priority user stories. Each user story is a description of the use of a separate end-to-end experience. It includes: User portrait (persona), usage scenario (context), use intent (intent), step (flow), product value (value, how the product helps the user to achieve value), and priority
The most high-priority entry MVP (minimal viable product), and so on, and so on, the lowest priority entry backlog, we have plenty of resources to consider the implementation.
7. The details of the design are contained in the design rules. The product manager can sometimes provide some wireframe, but also allows the designer to provide more professional design drafts.
8. Measuring indicators This piece is about how to measure the success of a product. An indicator of something to help us determine whether our efforts have the expected return.
9. Dependencies (dependencies) This is more easily overlooked, but often important. Because the product manager is the person who has the most holistic view of a product, it is important to make it clear that the deliverables are in front of which deliverables, what is the relationship before the deliverables and deliverables, so that the corresponding person in charge has a clear understanding that the development time will not be missed.
10. Test Plan
a test plan is a series of tests that need to be done before the product is released to ensure that there is no accidental occurrence of the product in a variety of usage scenarios. The test plan includes usability testing, performance,regression testing, and some behavioral tests based on specific usage scenarios.
There are a few good points to talk about, you can speak more deeply, but for the time being to share here. Making products especially in the early stages of the product is actually a process of colliding ideas with different people constantly. Then we put some definite ideas into the product documentation and sealed them up. The first thing to consider is whether the product is valuable, this value can be in the exchange to let others feel, generally this two points to meet after the product documentation will be more clear thinking.
public Number: Maibanzhang
(material from the network, not original, if there is similar, please contact delete)
How do product manager interns improve their writing skills?
