To become a good PM, please take the initiative to go into the technology

[Guide] The author is not to do product origin, just out of interest in product design, so this article does not represent the position of the Product manager, the author of technical background, but not keen on technology, so this article can not represent the position of research and development engineers. So this article may be more neutral, but may also have a strong personal bias, but I also welcome you to make corrections.

Product Manager (PM) VS Research and Development engineer (RD)

Often heard people mention, and also in the knowledge of the discussion, the Product Manager (PM) and Research and Development Engineers (RD) seem to like to pinch each other, standing on the individual point of view, although the technical background, but their own inner technical villain and product villain also often quarrel with each other, The feeling seems to be one of the mutual pinch in the mode of thinking. Of course, this is not to say that the two modes of thinking are antagonistic to each other, good products are not pinched out. The need for product managers and research engineers is more of an effective communication based on respect and understanding. But the foundation of the Simple research and development engineers are still relatively passive, so the author suggested that the product manager can take the initiative to understand technology.

Why does PM need to understand technology?

I have to say, the technicians are very proud. PM Although not above the role of Rd, but follow the PM design to implement more or less will make RD give birth to the feeling of inferior (no lack of the PM itself is also think so), this may be to let the pride of the technical flow of the place. So Rd do not see PM can be said to be natural, if the PM does not understand technology, then Rd can be more in their own strengths at ease to despise the PM. This is not the Xiaorendezhi of RD, and years of technical experience will make them feel more like a kind of self-protection, to protect their proud knowledge of the field is not to be told by non-professional professionals. So if the PM knows the technology, it will win the respect of RD to some extent. So it seems a bit around, frankly speaking, if I am RD, I will be more respect for the technical PM.

Unlike the designers who are "pointing", research and development are hard to "steer"

Understanding technology is not just a psychological problem, in fact, it makes it easier to communicate between PM and RD. We often feel that Rd is difficult to communicate out of the conceit of technology, and if Rd starts to throw off terminology and principle, then it's still understandable to spend a lot of time and patience, and sometimes it's even more frightening that PM feels like the conversation with Rd takes place in exactly two dimensions. In fact, RD in this communication, not in an attempt to highlight the technology of NB, which seems to be more of a habit, is a long-term technology and technical flow of the habit of communication. So, PM understand technology, can better understand and adapt to this habit, at least also can let oneself not be fooled by Rd, PM If Rd around Foggy, can't refute, inability to judge, that is also a very terrible thing, such as the following from XKCD comics.

Also know some technology can be the PM from strategically pull to down-to-earth. Most of the time RD will be negative with PM, it is likely that the PM design in the technical feasibility of the problem or create trouble. So in RD, PM is a wild-style irresponsible YY, but the implementation of a variety of unreliable issues have been thrown to them. As if the architect could not understand the civil engineering, PM sometimes need to know how to implement the brick on the technical level in order to make the design become steadfast.

PM may not understand technology?

Writing to this point, but also the moderation, in fact, PM understand technology, also may not be necessary, such as my personal inner technical villain will be excluded from these three kinds of circumstances.

1. This PM has a very successful product experience

Although the technology flow is proud, but also has the respect of authority humility. If you have a very glorious history, even if you are ignorant of technology, but with the "PM will lead you again to product success" belief is enough to make RD convincing. But can do this degree of PM, do not understand the technology should be rare it.

2. This PM has a very sharp product intuition

As a PM has a very sharp product intuition, especially for the new technology may bring the product innovation has a keen sense of words are also excluded. Good sense can make others follow applauded, RD is stubborn and can smell the direction, so will be willing to follow your intuition. However, sense this kind of thing, sometimes is same with the talent to encounter but cannot ask.

3. This PM has a very strong logical thinking ability.

Technology flow is logic control, if your design has a logical loophole or problem, it will make Rd is extremely despise, if you have made Rd has done a lot of work, it is more likely to incur resentment. It is because of RD's obsession with logic and value, PM's logical thinking ability has become a great test. In addition, learning technology can actually exercise the logical ability of people. Of course, it is not necessary and sufficient to understand technology to be powerful.

Summary

Said so much, it is not to advertise the benefits of the technology, in fact, sometimes the technology will bring restrictions on design thinking. For example, the PM look at the product may first consider the product positioning, and RD look at the product first thought is the function. Individuals have been very like to take the function of saving products, do something basically can not be called products. This may be the difference in thinking patterns that are mentioned earlier. PM mode of thinking is actually very valuable, so learning technology, but also need to be cautious.

All in all, PM should be able to understand some technology, perhaps do not need to understand the details of technology, but at least have common sense, and once again to the technology show respect and enthusiasm. Only in this way can you become a good product manager.