The ability to coordinate and communicate is inherently soft power, highly dependent on the company’s overall environment, and it is not achieved overnight. We all know that some general principles apply to the whole world, but there is not much practical value, so just combine these two Days of work to think, to say some pragmatic words, for reference.
In the past two days, Jing Jing has frequent video conferences, evaluation meetings, various training explanations, and operation coordination. After being attacked, he is attacked again. He needs to coordinate and communicate to solve many things. There are actually two effective communication methods:
First, find out the real needs of the other party, clarify your own needs, and make a comparative analysis. Sometimes the solution to the problem will naturally appear.
The day before yesterday, our product department normally organized a requirement review meeting for new functions . The technical director suddenly decided that this time, developers would not be allowed to directly participate in the review.
The reason is that the development time is tight, the task is heavy, and it cannot delay too much time. It is said that the product manager should review it alone, and then send the requirements document to the development first.
He then arranges specific development work based on the requirements document and his understanding, and asks the product manager if he does not understand email list the development. If necessary, he can re-evaluate.
Although it is not explicitly stated that public participation in the review is not allowed, in fact, the developer is not allowed to directly participate in the review.
The product manager was stunned at the time and coordinated and communicated, but there was no result, and then he gave me the above feedback.
At the beginning, I was also surprised that agile development and review will be the most efficient tool . If it is only understood within the development itself, there is a risk of deviation, and there may be communication costs in the follow-up.
So, I went to the technical director to communicate. After in-depth communication, I finally learned that the original boss had new adjustments to the KPI indicators of the technical department.
Added the current month demand completion rate (total demand completion/total demand plan).
The demand here means that as long as the review is held in the current month, the product manager will be included in the reviewed requirements, even if the review needs at the end of the month. (Simply put, as long as the requirements are online, the performance may be high, and if not, the performance will be low, so it is better not to review)