What kind of product managers the developers like

In practice, product managers often need to deal with developers, and the premise of interpersonal communication is a good sense of each other, or even established friendship, so that communication or communication will be very smooth. Product managers and developers, belong to the scope of the relationship between the work category, generally also belong to different departments, if coupled with the assessment of the KPI is not the same, between the two is difficult to achieve a common goal and seamless cooperation. From the normal situation, the product manager to start from the overall situation, to be more comprehensive, a design may contain future operations and data-gathering forward-looking stuff, and developers are more concerned with how to implement it, how easy it is to achieve it, how much code is required, and how many different angles to do the same thing, Bigins will cause a lot of discussion, so the meetings that the product managers have to attend are always a lot. How to maintain good and efficient communication with developers is always a problem that product managers need to solve.

Supposedly, product managers and developers can also establish a deep friendship, this need to work outside the communication and a lot of pleasant cooperation can slowly build up. The product manager who has worked in an environment for a long time and the product manager who has just entered into a new environment must have a good relationship with the developers of the product line, otherwise it will affect the work carried out later. Often hear from peers complaining about how poorly they communicate with team members in the company, lead to the loss of confidence in the product and so on, I would like to say is, whether it is and ued, design, development, and so the whole team is not smooth communication or only with the development of communication problems, product managers are to self-reflection, the problem is in your own body , because the purpose of interpersonal communication is to be in the face of different personalities and different backgrounds of people to adopt a very different way to create a good interpersonal environment. There are some ways to make a product manager that developers like, and to rule out some personal charm factors. The individual is doing better in this respect, two companies can stay with the entire team, but also with a number of developers to establish a deep friendship, the following talk about personal experience.

Reasonable communication

Communication is the necessary means in the process of interpersonal communication, and good interpersonal relationship begins with communication. From the perspective of communication, in the face of different personalities of developers, is to adopt a different way of communication, which requires some experience to do, so just out of school to fight the peers may be a bit of a disadvantage, but if you participate in the school enough social groups activities, I believe you should be able to learn some ways. To put it simply, learn to think and communicate from the point of view of others. To the dreary developer of character, the logic is as rigorous as possible in the communication, the language as far as possible with some professional terminology; for cheerful developers, there are also appropriate to some of the mantra ah, gag and so on; treat the elderly (above three years old), must be humble and polite, peers can be casual, But also cannot unbridled, treats the development new person, must treat equally, does not take any contempt. The relationship between people is the most complicated, need to accumulate and learn slowly, individuals are now afraid to say that they can deal with all the situation, can only try to do the best, in short, to remain humble and polite is always true, anyone likes to deal with polite people, low-key line of the world Ah.

Someone good communication beginning, can open conversation began to communicate, but to achieve the purpose of communication, only this is not enough. People and people to get along with the most concerned about equality, so in the communication should pay special attention not to take the Boss command Ah, KPI ah and so on to pressure people, to reason. Not only do you tell developers what they should do, they also tell them why they do it, where they are doing it, and it's best to tell them the value of doing so. Anyone who wants to do something worthwhile, rather than unproductive, has a good sense of purpose and value. When communication encounters disagreements, try to convince them instead of simply asking for leadership or doing it above, which can cause developers to resent it. Although sometimes do some of the leadership required to say the value of the function, product managers should try to make this thing look right, so that developers recognize the status quo, identify with your helplessness. At this point, the individual's approach is to talk to each other, who can persuade each other to listen to WHO, product managers will also make mistakes, sometimes developers say is right, after all, from different angles of thinking problems will have the same structure, and the view.

Professional Document writing Ability

A good PRD requirement is to correctly and clearly describe all the functional points of the product, functional description is not ambiguous, the description of the function point is consistent, each function is necessary and complete for the product, all the functions are designed to be verifiable and achievable, the elaboration is what to do rather than how to do. Others are better understood, good documents make people look very smooth, can be at a glance, and do not have to go into word for word, this will also save developers to see the document time and energy. But the last point to a little attention, how to do is generally to have a developer to decide, the product manager to specify the data source, organization logic, to achieve the display effect can be, do not need to tell developers how to achieve. Only in one case can you design something that you think you can achieve, and developers don't think it will, and you can tell developers by giving an example or a euphemism for how to implement it in a way that is necessary and valuable to the business. Try not to let the developers feel that they are not enough, but to lead it is a challenging thing to do. The ability to write in a developer's perspective is not necessary, but is a bonus, this ability is also a product manager of the necessary ability, if not strong enough, or a good cultivation of it.

Basic technical knowledge

First of all, it's not a prerequisite, but it's a bonus. Some product managers have research and development backgrounds, that is, before switching to do product manager, have engaged in development work, so that there is an advantage, if the previous development work and the current product needs is the same words, it is perfect, can be in the design of a certain degree of implementation and feasibility considerations, Evaluate whether the designed functionality can be implemented under existing conditions and resources, and can be understood at the review of the system design instructions written by the developer, and can be roughly understood to meet the requirements. Developers are interested in interacting with peers, like our own like and Product manager peer Exchange, so did the development of product managers and developers in the communication has an advantage, but need to pay attention to, do not pretend that the big guy, do not think they have done great development, on the participation system design, This will be objectionable, remember that your technical background can only stay in the product design phase and PRD communication stage, do not give too much technical advice or advice, and you have changed careers, maybe you know things are outdated.

A product manager without a research background needs to be cultivated, in fact, do not need to learn to develop technology, but to know some of the terminology, such as JS script, Ajax, database, stored procedures, BI, and so on what the noun is what, otherwise you will find you in the communication with the developers will be one Leng, Because you don't understand what they say. To be specific when you study, for example, the company's products are used in Java development, then to understand the basic knowledge of Java, the data are all using MySQL, then to a simple understanding of the database-related knowledge, our goal is to understand what the developers say, so as not to be passive. If you let developers find that he said a long time, you do not understand, if you want him to tell the second or one by one explain, it is estimated that the first to be a little impatient, followed by a little bit of you, hehe.

Listen to the suggestion

As mentioned earlier, there are times when developers will make some comments or suggestions, although everyone is very professional, experience is very rich, but we are very busy, many times can not consider so fine and so perfect, there are always flaws, and developers sometimes timely give some advice on the details and changes, This time you have to evaluate to see if it's valuable, if it is to change the demand, it is to be carefully evaluated; If you do not change the needs, you have to evaluate which is better, the two programs to achieve the ease of implementation, whether it can compromise and so on, as far as possible to stand in the perspective of developers to consider. The people who can listen to the advice are also welcomed, just like the devil, the following counselors are loyal to him, because he is good at adopting suggestions.

Finally, the developer is also very cute, but a lot of people outside the programmer will be branded with a variety of hats, it is biased, it should be noted that not all developers will have similar behavior, if you have preconceived, often make wrong judgments. The previous product manager with a background in research and development is a career change from a developer, which proves that there are a lot of similar people among the developers, and that there are one or two beautiful women from time to time. The above is a summary of some of the work experience of the individual, the first two points personally feel in collaboration with the team members are applicable.