What bugs do developers hate about product managers?

First of all, no one will hate a person for no reason, the only possibility is that you have to let him dislike the place and some smelly problems, they may think it is okay. This is due to human cognitive barriers, sometimes unavoidable. Not being a product manager annoying to developers, you need to first figure out what developers hate? So I asked a question: what are the bad things about product managers developers hate ?

To my surprise, many in the industry have discussed and focused on this problem , and have followed suit to create what are the most annoying things that designers dislike about product managers? What are some of the bugs that product managers hate about developers? and so on. It's not hard to speculate that in an internet company, it's always challenging for people of different roles to achieve seamless cooperation in the process of accomplishing projects together.

Admittedly, these challenges may be due to the capacity of the participants, which is unavoidable. But I would like to believe that communication is not smooth, poor habits, lack of transposition thinking and other factors are the most common. The discussion of several issues in the knowledge of the various roles may play a role in exchanging places between different players, and undoubtedly, this is a matter of positive significance to all parties.

Product Manager as a link between the central node, to avoid some annoying smelly problems appear particularly important. From the answers I have made, I have categorized these possible behaviors into the following situations:

What can be avoided in a short time:

The demand is not clear, when the developer asked the PM needs, and found that PM also do not know, such a problem is must be eliminated also completely can be eliminated, if the PM themselves are not clear demand, the consideration of such a job is suitable for their own.

Intervene in purely technical issues, such as: This code should be written like this. Avoid the way: for pure technical problems do not intervene, if his technology implementation is really a problem, the relevant person to be responsible for the product only to pay attention to whether he finally achieved the expected function.

The delivery of the solution is uncertain, developers hate "in fact this can also", "otherwise it is", they need a clear solution. When a variety of options are hesitant to think, PM it's best to just take such hesitation into consideration. Unless the engineer is unable to implement your first plan, then say the alternative.

There is no need to reserve the time, "This we modify, tomorrow to submit a new version, a look, listed a lot of added functionality, not just modify." Coder is really not God, the added function is to be tested. PM give yourself time to stay at the same time, poor poor siege of the wet, save some time to think about it. This is the exact words of an engineer. PM to be responsible for the progress, the pressure is very large, but set aside time is a must.

Not entirely avoidable but can be improved in the short term:

Requirements change, which is the highest rate of the answer in a vocabulary. However, for developers to be disappointed, for a variety of reasons, this problem can not be completely avoided, PM can do is to try to make as many problems as possible before the delivery of development, so as to minimize the need for possible change, the other is to eliminate the need for reciprocating changes, Do not feel that it is not possible to change from programme A to programme B and change back to programme a.

Oral sex Too many times: to avoid verbal confession, obviously unrealistic, and then the perfect document can not replace the verbal direct communication. But frequent mouth (head) (flow) may interrupt the engineer's thinking and delay the progress. PM can do one is to try to improve your document, the second is to try to focus on a verbal communication as much as possible, so as to reduce the number of times.

Requiring long-term accumulation or exercise to improve:

Lack of charisma: yes, the lack of personal charisma has also become a reason engineers hate PM. But the personal charm of this thing, it is really difficult to improve in the short term. Even, different engineers have different criteria for judging personal attractiveness.

Lack of experience: or qualifications are not deep, to change the status quo, I am afraid it will not be immediate.

above to encourage.