What kind of plan do we have for the product, and what rhythm do we want to achieve the desired result? Its own needs come from product goals, from quarterly planning, and from the O in OKR. Dismantling the target and planning the functions job function email list and progress nodes of each version is the rhythm of its own product. At the same time, some places are reserved in each version to insert the needs of users, bosses, colleagues job function email list and other aspects that may appear.
In this way, while dealing with new requirements, we job function email list can do a good job of version control to ensure that the product is moving towards its desired goal. Requirements are gathered from various sources to the product manager, but the iterative versions can only be advanced one phase at a time, and there are only a few requirements that each version can do. At this time, it is very important to manage the expectations of all job function email list parties on the requirements. At the heart of anticipation management is timely synchronization.
After receiving the demand from one party, you need to job function email list be serious and responsible, and every progress node of the demand must be synchronized to the demander. Whether it needs to be done, when to do it, and what is the effect of doing it? Instead of clearly telling the reasons and alternative methods, the estimated launch time job function email list and post-launch analysis results are given. Only in this way can our product planning be implemented. 6. Finally Product managers, not demand shredders. Do not blindly undertake demand,