The demand side may be operations, sales, and customer service. They will directly ask the product manager for requirements based on the problems they are currently encountering.
Everyone knows the story of fast horses and cars. The email list demander needs a fast horse. Do we give him a fast horse directly as he said, or think about what the essential appeal of his demand is and whether it can be transformed into another demand? Is there a more reasonable solution?
If there is a demand, just do one, and lack the thinking behind the demand. This is not called a product manager, but a demand implementer.
Clarify the boundary between product and demand side
When cooperating with the demand side for a long time, it is necessary to form a good communication model and clarify the scope and boundaries of their respective responsibilities.
For example, when a project is launched in cooperation with operation, what content needs to be clarified for operation and what content can be displayed by the product. In this process, the product cannot arbitrarily modify the rules of operation confirmation, but it cannot allow the continuous change of demand, and cannot let Operations directly interfere with product system-level impacts.
Grasp the boundaries gracefully and respect each other's work content, which can reduce a lot of wrangling and make cooperation more efficient.
3. Communicate with developers
For junior product managers who focus on project execution, the most people who communicate daily must be developers. If there is too little communication, either your requirements document is perfect (almost impossible), or you are not proactive enough.
(1) The difference between communicating with the development boss and the development younger brother
The development boss is the technical leader of a certain line. When there is a major function iteration, it may be necessary to discuss the plan with him first.
When communicating with the development boss, it is best to think of a reliable plan in advance, rather than too much deviation, so as to avoid wasting both parties' time and improve the boss's trust in you.
The development younger brother is the development classmate other than the big brother. The core skill of communicating with them is to establish a community of interests, because they are the people who specifically meet the needs, you need to tell them the background of the needs, the value after realization, and go online. Afterwards, the effects should also be synchronized with them to increase their sense of pride.
Developers also need successful projects to reflect their value and make them feel that you are on the same line. They will also do their best to help make the system better, and it is not a problem to change some small requirements during the development process.
Of course, these techniques are based on the premise that the quality of the requirements document is qualified.