Why do I need to write documents in product design?

Why do I need to write documents in product design?

Many people may ask, "you can just say two sentences. Why is it so troublesome to write documents ?" When all of us work in the same office, we can just say a few words. Why is it so troublesome to write down everything in the document? Copyright yixieshi

The value of the product documentation is that it can provide a reference point for the entire team. The product documentation provides a good reference for the work to be done in this project and defines your product documentation, in order to ensure that the development process will not encounter the case of modeling. When a product manager sees a new article or idea, a new function is considered. If a project has no fixed goals, no schedules, and no pre-planned milestones, there will be no end to the project. In this way, no one knows what benefits the project can get and when the project will end. These documents drive the project, organize the project, standardize it, and play an important communication role in the project team.

Project documents are the main communication method between my boss and me. It's hard to communicate with my boss, or if my boss doesn't understand what I do, my "Project Manager" is coming soon. Poor communication with subordinates makes it difficult to ensure the quality of the project. The project fails. Even if my boss does not withdraw me, do I still have the face to continue as a project manager?

Although it is very troublesome to use documents to describe the project requirements, you must do so mainly because of the Internet.

1. Do you know what the goal is when you have a document?

The goal of a product is not just your own thoughts. The product must be fully cooperated by the entire team. Without a document record, your product and project will become a "legend" by word of mouth. What's terrible is that everyone has different understandings and their oral descriptions are different, in this way, no one knows what the real goal of the product is. As long as a document records the project's objectives in detail and the project's process schedule in detail, the product will not stay in the mind of the product manager, it becomes something that everyone in the product team is at your fingertips. This project can be handled perfectly only when the idea of a person is turned into the idea of the entire team. Some things from the Internet in this article

2. Do you know what to build with the document?

Product projects have a lot of ideas and ideas in their early brainstorm discussions. If there are no documents recorded, it will be very confusing in the development and implementation process, I don't know what the current job is to do? As long as documents are supported and the purpose and specifications of the product are recorded in detail, it may look like an independent functional module; only after the requirements are determined, in order to make things more detailed. A product has a series of clear requirements in development, so that you can clearly allocate responsibilities and have a clear division of labor in order to provide collaboration efficiency at work.

3. Do you know what you don't need to do with documents?

When product projects are in full swing, there will be a lot of functional ideas that sound very attractive. Every idea function does not seem to work much, but when many ideas are brought together, the whole project is out of control. Like a snowball rolling, the project will expand endlessly and the launch time of the project will be far away. With this document, do you know what is being built? What is not required at this stage? It is good to have an idea, but it does not mean to do it right away. You can document these outstanding ideas and analyze them to turn them into your long-term plans. This is the true value of your ideas. Bring together all new ideas to reserve product upgrades and version updates.

4. With documents, you will not die when people flow.

With the document, if someone leaves, the document serves as an important handover tool, so that the project will not be delayed too long.

The most painful thing for the project supervisor is that when an important member leaves the project team halfway, he finds that he has not left any available documents. There is no banquet in the world, and members of the project team are also dynamically adjusting. Documents are an important tool for connecting members. Many supervisors may easily fall into the misunderstanding of "focusing on technical implementation and document-light. They always think that the project implementation time is short. To save time, they can rush to write documents at the end of the project. If the project cycle is a little longer, will the members still remember the details of each implementation? A project without a document must be a failed project.

By attaching importance to the project documentation and organizing implementation, each member of the project team (including me) can be replaced to a certain extent, minimizing the risks of the company. This shows my "loyalty ". Although this is also the requirement of software specifications, many bosses also say that "loyalty" is always the first. "Loyalty" means putting yourself in the shoes of the company to maximize the company's interests. It is the smartest way to maximize your own interests by maximizing the company's interests.
From the perspective of process control, the most important aspect of project quality control is document management control. The document shows the workload and completion quality of each member for each baseline to minimize project risks.

5. With the documentation, it will be easier to maintain in the future

6. With the document, we found the same project, so we had a reference.