How do product managers not let developers hate?

First of all, no one hates someone unprovoked unless you have annoying smelly things on you. And some sore, they may not think it is very serious. This is due to the obstacles of human self-awareness and can not be avoided. Do not make the product manager annoying developers, you need to first find out what developers really hate? So, I know a question asked: Developers hate the product manager which the most troublesome?

Surprisingly, this issue has aroused much discussion and concern in the industry, and follow the trend created by the designer who hate the product manager what soreness, product managers hate developers what soreness, product managers hate Designers of those smelly problems? And other issues. Not difficult to speculate that in the Internet company, the different roles of personnel in the process of jointly completing the project, to achieve seamless cooperation is always a very challenging thing.

It is true that these challenges may be due to the competency of the participants, which is inevitable. But I prefer to believe that poor communication, poor habits, lack of empathy and other factors are the most common. The discussion on several issues of knowing may help to change positions among people of different roles. Undoubtedly, this is a matter that has positive meaning to all parties.

Product managers as the central node through all aspects, to avoid some annoying stenosis is particularly important. From the obvious answers, I summarize these actions that may become sore as follows:

Short period of time can be completely avoided:

The demand is not clear, when the developer asked the PM needs, and found that PM is not clear, this problem must be eliminated and can be completely eliminated, if the PM themselves are not clear demand, consider whether such a job is suitable for themselves .

Intervene purely technical issues, for example: This code should be written like this. Avoid: for pure technical issues do not interfere, if his technology is really a problem, the relevant person to be responsible for the product simply focus on whether he ultimately achieved the desired function.

Delivering a solution that is unsure, developers hate saying that "it's okay to do that," or "it's going to be right." What they need is a clear plan. In a number of programs indecisive need to think, PM best is just such a hesitant reflected in their own thinking. Unless engineers are unable to implement your first option, put the alternatives back.

No need to set aside time, "This we modify it, submit a new version tomorrow, a look, listing a lot of added features, not just modify. Coder really not God, the added functionality is required to test .pm Give yourself time to stay at the same time, poor pitiful siege to wet, leave some time to think about it. "This is the original words of an engineer. Pm to be responsible for the progress, a lot of pressure, but the reservation time is a must.

Can not be completely avoided but can be improved in the short term:

Demand changes, which is the answer to the highest flat rate appeared in a word. However, to the disappointment of developers, this is a problem that can not be completely avoided for a variety of reasons and what the PM can do is to try to take as many issues as possible before delivering the development, to minimize the potential for change, ; The other one is to eliminate the need for the reciprocal change, do not let from program A to program B after that feel no, change back to program A.

Too many oral sex: to avoid verbal confession, apparently unrealistic, and then the perfect document can not replace oral direct communication. However, frequent oral (head) delivery (flow) may interrupt the engineer's thinking and delay the progress. PM can do one is to try to perfect your document, the second is to try to talk as much as possible in a verbal exchange focused on things, thereby reducing the number of times.

Need long-term accumulation or exercise can be improved:

Lack of personal charisma: Yes, lack of charisma has also become a reason engineers hate PM. However, the charm of this thing really difficult to be improved in the short term. Even for the judgment of personal charisma, different engineers have different standards.

Insufficient experience: or seniority is not deep, to change such a status quo, I am afraid it can not be immediate.

Above, self-encouragement.