How do product managers get along with programmers

There is a lot of jokes between product managers and programmers, and most of the themes are that product managers are hacked (who makes more programmers). The news of the previous period has pushed this relationship to its climax:

Of course, the spread of this thing is not the same as the thing itself (read it here to know), but it clearly reflects the "Programmer hates product manager" social cognition.

As a product manager, the work will be difficult without the collaboration of the programmers. To get a good relationship, you need to find out why programmers hate product managers.

You wasted my time.

1. Frequent change of demand

This is the most frequently mentioned. Often the change in demand means that the engineer is in vain for the requirements to be realized. The thoughts and feelings that were poured before are in vain.

2. Problems caused by unclear product definition

The problems of unclear and illogical documentation can lead to a difference between the engineer's implementation and the product manager's vision. This often means toppling over again.

You hurt my self-esteem.

1. Take the boss to pressure people

"The boss said so change," the director said so change. The behavior is to move the boss out of the way and suppress the possible questioning of the programmer. This is very unfriendly.

2. Doubt my skills or work

The most typical is: "This function is simple to achieve." Sometimes product managers may intentionally or unconsciously show technical doubts, speculations, etc. But the engineer will think that you as a technical layman should not do so.

3. Put yourself in the highest position

Some product managers think of themselves as a decision maker over engineers and are free to dictate to engineers. But in fact the product manager and the engineer does not exist who leads the relationship.

So engineers are actually advocating efficient, authoritative and professional people. The way to get along is to extract from what they love and dislike.

1. Do a good job in the product design.

Maintain good product documentation, think clearly about the logic and process of function, coordinate design resources, etc. These jobs are the basis of the engineer's work, and the product manager must take it seriously. I have written a document about the importance of the product documentation before.

2. Confidence-building

Programmers eat by technology, while technology is the face of programmers. When a layman questions the technology, he is bound to get upset. Although the product manager must be taken into account in all aspects, the technical things are assured to the engineers. Trust is the foundation of mutual cooperation.

3. More, more, more communication

There will never be too much communication, only too little communication. Maintain a sufficient frequency, sufficient quality of communication, product managers can be more timely to identify problems, such as the requirements of the implementation of deviations, engineers understand the deviation and so on. Early detection of early treatment, while engineers have not poured too much time and energy in the direction of deviation.

4. Sincere dialogue, have

Avoid the use of bosses to suppress this irresponsible behavior. In fact, the need to change is inevitable, but this matter must be explained to the engineer. Why modify it? What was the problem? What are the benefits of this change? Why did this change occur at this stage? To be honest with these answers to the engineers, I believe that engineers can understand to some extent the need to change the matter.

Summary finished! or based on their own experience to share. Hope to communicate with more students ~ Now popular said a good product manager should have "no authorized leadership." This is the next step in the friendly coexistence with the engineers. In the future, I will write the relevant articles specially.