Jun 11, 2022
In Wellness Forum
Editor's introduction: As we all know, writing is an indispensable weapon for product managers, so how do we write a working document? This category email list article discusses the methods and techniques of writing in an all-round way from four aspects: clarifying the goal, conceiving the structure, writing the content, and checking the details. Recommended reading for children who want category email list to learn about writing. When it comes to writing, we may have these misunderstandings: writing is the patent of copywriting positions, and ordinary workplace writing only needs to convey information, whether it is good or not. This is not the case. An important way to judge the professionalism of a product manager is to look at the requirements document he wrote. Whether the document is good or not depends on the basic skills of writing. Therefore, writing is also an indispensable weapon for product managers. When category email list you master the writing itself, writing a beautiful requirements document is not a difficult task. Writing is written expression and needs to follow this important principle - Don't Make Me Think, from the category email list reader's point of view, try to increase readability and reduce readers' barriers to understanding. We can follow 4 steps to write a good working document: clarify the goal, conceive the structure, write the content, and check the details. 1. Clear goals why, what, who, when, where Why - clear purpose, what is the purpose of this document. What do you want readers to achieve by reading this document? Is it communicating a decision, reporting status, or discussing some aspect category email list of the project? What—Clarify the key content, what key questions does this document answer? The key questions to answer category email list determine the content and structure of your document. Who - clarify the needs of readers, who is the document intended for, and what will they be concerned about? What questions will there be? To your immediate supervisor or to your users? Will they care about the progress of the project or the specific user experience?