Editor's introduction: In their daily work, product managers often need to explain requirements, and the quality of demand explanations has a great impact on the scope of requirements, team efficiency, and recognition. So, how to do a demand presentation? The author category email list of this article has put forward a few suggestions, let's take a look. In the daily work of products and requirements, it is indispensable to explain category email list the requirements. For example, our team may organize a wave of reviews in two weeks. Sometimes it involves the demand support of the delivery team, the product demonstration of the pre-sales team, and related explanations will be more frequent.
In the course of continuous explanation in the past two years, I found some common problems of the speaker, and through category email list several months of trying, the small partners in the group gradually mastered the basic explanation ability. Today, I summarize it for your reference. What else do you have? A good way is also welcome to leave a message to exchange. The category email list quality of requirements explanation not only affects the effect of understanding and evaluation, but also has a profound impact on the scope of requirements, team efficiency, and recognition, and its importance is self-evident. 01 Throw some of the most common questions first Come up and talk about the function directly No matter who the audience is, the content of the explanation will basically remain unchanged.
The speaker's gain and loss are too heavy, but it affects the accuracy of language expression No pre-rehearsal There is no real understanding and absorption, the process is not confident, and the problem is not answered well You are free to add other questions. So category email list where can we start to solve these problems? 02 Distinguish crowds (see people speak human words, see God speak myths) Be sure to organize your own words in a differentiated category email list manner according to the different audiences, including the level of detail in the explanation. The documents may be the same, but the emphasis must be different when you tell them to project managers, developers, testers, colleagues in the requirements group, and leaders.