How product managers like the birth of developers

【REVIEW】 wrote an article before "to create developers like product manager", which can be regarded as a sister chapter. As a developer, do not go to study technology, learning emerging technologies, will eventually be eliminated. IT industry is the fastest-updating industry, there are new technologies, new concepts appear, do not keep pace with the times will be abandoned by the times. Then the technology is a bottomless pit, the more in-depth research will be more proficient in a technology than know N technology more valuable.

As we all know, product managers are very hard to force the role of bitter forced to meet any role, coordination here, over there begging, I think many people have a profound understanding. However, everyone is a member of a product team. To achieve harmonious cooperation in order to achieve their product goals, they need to be able to interact with each other in an intimate and unobstructed manner, as well as tolerance and tolerance among themselves. Therefore, we can not blindly ask the product manager to relocate developers, everyone has their own personality, developers also need to accommodate product managers, each taking a step back to the brighter future.

The product manager most want to see is that their product intent can be completely achieved, and in accordance with the idea of ​​PRD, step by step to achieve a little bit. At PRD Review, team members can make comments, but in the end it is up to the product manager to make the decision. In particular, the product manager responsible for the team, grasp the product level, the product manager must have the decision-making authority, so as to ensure that the product can be implemented step by step according to the plan. If the developer of the product design flaws, and in the development process to join a lot of their own ideas, will undoubtedly affect the planning of the entire product, if added to the icing on the cake is also good to say that in case the disrupted the functional structure of the product, Will undoubtedly make the product manager very depressed, and even affect the performance of the entire product team.

As the saying goes, there are Wen Wen successively, surgery specializing in surgery. If we all play their part and give full play to each of our best parts, we will be able to make a big contribution to the product instead of interfering in the areas we are not good at. I admit that many developers have the potential to be product managers, there are indeed a number of product managers are technical background, I myself, but if you have not yet transferred, or should play a good role, the product manager is mainly responsible for Product planning and design, developers responsible for the realization. This is also what kind of developer is the product manager favorite topic.

The most popular is hardcore

For example, the product manager is to draw the drawings, the developer is the construction, to strictly follow the design of the drawings drawn to the construction, the building will not collapse. Hardcore developers are most welcome by the product manager, so that people can actually implement the product intent. Of course, is not a blind construction, based on a full understanding of PRD, to understand a certain background, to know its value, there is no big difference on the design program, there are no technical problems to overcome, and then follow the PRD development . Hard work does not mean that the muffled, there are opinions can be mentioned, only after we reached an agreement, or did not reach consensus, the product manager of one of the design plan, the follow-up can be developed by PRD as usual, so Is the product manager like it.

Having questions is a good thing, proving that taking the time to understand the ideas and intentions of product design can also help developers become familiar with their business and improve themselves. Product manager responsibility system is not to engage in "a word", or very democratic, only when everyone can not dispute, have the final decision-making power. What the product team needs at this time is a solid PRD implementation, not skepticism that can be tampered with in the development process.

The most annoying is mixed

When discussing the product needs everyone agreed, and finally found out that the development is completely not the case, this time the most depressing is the product manager, his design is someone else's face changed beyond recognition, but also take the time to refactor, Affect the overall project progress. In a product team for a long time, a lot of learning ability of developers will be the product or responsible for the business to form some of their own knowledge and understanding, this understanding is sometimes good, can help developers quickly understand new needs, Sometimes it's a bad thing, preemptive to make the developer think it's fun to play on it, he's already got it, and he's got some ideas of his own that add those ideas to the product. This situation is the worst.

There is also a cup of the situation is that developers across the product manager to communicate with their own business needs and consider themselves mastered the primary needs, as long as the business staff to help quickly meet the corresponding demand is a great contribution. Unpredictable primary needs are mostly unavailable, need to be transformed, and most users can not clearly express their needs, only to describe their daily operation is this. If this is the way to achieve, the product is made offline only online operation, no product planning at all, nor in line with business logic. This is equivalent to the overhead of the PRD, completely PRD as a decoration, which is very undesirable behavior.

Developers should have the ability and quality

The most basic is the technical level. As a developer, do not go to study technology, learning emerging technologies, will eventually be eliminated. IT industry is the fastest-updating industry, there are new technologies, new concepts appear, do not keep pace with the times will be abandoned by the times. Then the technology is a bottomless pit, the more in-depth research will be more proficient in a technology than know N technology more valuable. Sometimes the length of work experience does not represent the technical ability, the key depends on whether they are willing to study. There is no doubt that more skilled developers are more liked by product managers.

Technical architecture capabilities. PRD just expressed the requirements of the product demand level, the technical design level or rely on the developer to design. The scalability and stability of a system depend on the construction of the technology architecture. Good architecture can make the product has the most varied capabilities, although the demand can not change, but can be slightly changed to adapt. This structure is undoubtedly more enjoyable.

logical thinking ability. Mainly in the logic of the code is rigorous, especially in the judgment of the conditions are more, we all know if and else, also know and and, how to make them come together with a variety of conditions to meet the product's business logic and process logic , Is the developer to consider. This is more similar to the number of BUG.

Communication skills. Any member of the product team needs good communication skills, at least the things you want to express clearly, can not say for a long time, can not figure out what you are talking about. An example of communication is more effective, you can follow the PRD design, coupled with an example to describe the design of the question, so that product managers the most easy to understand. But the premise is that we must look good PRD Caixing, can not see the document, they began to mention a pile of problems, it will only make people objectionable.

Within the product team, product managers and developers get along well with each other, is a strong guarantee of product success. On the contrary, if there is a lot of contradiction between the two parties, nothing will happen. Therefore, the relationship between product manager and developer relationship has always been a headache, most of the time to the product manager are in compromise and cooperation, here, I also hope that developers can understand and cooperate with the product manager.