NPDP | how can product managers not be excluded by programmers?

Product managers face customer needs , Often need to communicate with programmers , Many times, it's unpleasant if you're not careful . So how can product managers not be excluded by programmers ？

Here are some tips to try ：

1. Learn the technical terms used in the company's products 、 frame

If you are a product manager who doesn't understand technology , When communicating with the program ape, it is bound to be despised by the technical bull . But to reduce communication costs and their contempt for you , The product manager must at least know the technology and relevant technical terms used by the company to run the products 、 Proper words , Understand what this technology does , What problems have been solved , Avoid confusing you with a proper word , You will be passive when communicating , Fail to achieve the purpose of the work .

2. Describe requirements and clear boundaries

When describing a requirement, be sure to be clear 、 controllable , It can let the R & D personnel quickly understand what function you want . such as , Product manager said ：“ Add a mobile phone verification function to the user registration interface ”. Let the R & D personnel develop... Without other detailed instructions , Developers will ask ：“ Whether the mobile phone number is unique before sending the verification code ”,“ The format of the mobile phone number is incorrect, and the prompt message is ”,“ Prompt message of successful sending of verification code , Failure message ”“ Whether the verification code is always valid ”,“ How long before you can send the second verification code ”“ When the same mobile phone number is registered, each time it applies to verify whether it sends the same verification code ”…

Our product manager seems to be a very simple function , However, when R & D personnel implement it, they will encounter a lot of detailed logic processing , These problems require detailed instructions from the product manager , More detailed , The clearer your directly established needs are , Naturally, there will be fewer disputes .

3. Better than R & D, business logic jump 、 Data processing mechanism , You can't dig holes for R & D

stay 2 Clear boundaries of requirements are mentioned in , Similarly, business logic and data processing mechanism must be considered in advance when we redesign our products , You can't put all the unknown problems on the R & D personnel .

4. Don't underestimate the difficulty of developing each function , Communicate with R & D to determine the workload

Every function of the product needs to be developed and hard coded , The development difficulty of each function varies according to the use of different technologies and the technical skills of R & D personnel . Therefore, when proposing requirements or planning, product managers should not subjectively think that it is very simple and blindly evaluate the workload , Let the person who needs to communicate realize it 、 assessment .

5. It is not allowed to tamper with the defined requirements at will , If it does change , The workload, time and technical difficulty need to be evaluated

Requirements change must be cautious and discussed in the meeting , Especially relevant technicians , Explain the background of the change 、 reason , And let technicians evaluate the technical difficulty and workload of new requirements , Do not modify the plan without authorization .

6. Don't put all the failure of the product on the R & D team

The success of a product depends on the joint efforts of the whole virtual team , Although the R & D team produced this product , But other members also play a big role in this process , So even if the product fails , Nor can we blame all the reasons on the R & D personnel .

7. When driving product progress , Don't shout and stamp your feet like a child , Use euphemism

When we push a job , It can't be like ordering the R & D personnel , You can't yell like a child to ask others . We should use euphemism , It's easier for the other person to accept the way to promote the work .

8. When announcing a decision, give the background and reasons , Emotional acceptance is always more comfortable than right acceptance

Whether you add a requirement or change a requirement , Be sure to explain the background to the other party , Don't let the R & D personnel think that the product manager is subjectively changing the requirements , Thus excluding the work from the product manager .

9. When you don't know how to do something , Don't point fingers

If you don't know, you don't know , Listen carefully to others , Don't talk nonsense just to show off yourself , Disorderly command , Cause a mess of work .

10. Don't use technical terms you don't know

Don't play with a big knife in front of Guan Gong , I'd rather not use... For technical terms I don't know , And don't mess with , It's easier for others to feel how ignorant you are .

11. Consult with the technical team before making a technical decision

At present, Internet technology is developing rapidly , Today, this competitive product uses A technology , It will be used on the competitive product tomorrow B technology , At this time, the product manager must be calm , Don't let the R & D personnel switch to new technology , The transformation and Realization of technology is related to the whole product architecture , Whether it can be realized needs to be discussed with the technical team .

12. When users promise certain features , It is necessary to communicate and review whether it can be realized in advance

Don't allow a requirement easily , There must be a standard process for modifying or adding functions to the product , That is, the process of requirements management , After getting the requirements , In addition to analyzing the rationality of the demand 、 Necessity, etc , Also let technicians evaluate whether the change requirements can be realized , Don't make subjective affirmation and commitment .

13. Work together with the R & D team , Same prosperity

As mentioned earlier, the success of a product depends on the joint efforts of the whole virtual team , So whether the product fails or succeeds , Product managers have to work with R & D personnel .

14. Empathy , Understand the real challenges of R & D

Whether in life or at work , We all need a empathy , Understand each other's difficulties , Help each other overcome difficulties .

15. Respect 、 Listen to the opinions of R & D personnel , Analyze whether to take or reasonable reasons

In the process of cooperating with R & D personnel , Respect the opinions of R & D personnel , Sometimes the opinions of R & D personnel may really add new highlights to the product , Don't be subjective 、 In a narrow sense, we think that program apes can write code , In fact, the logic ability of R & D personnel is very strong , Maybe you can't solve the problem , The R & D personnel will help you in minutes , Don't look down on every colleague you work with .

16. Maintain a modest and professional work style , To be recognized by others , Handle daily work relationship

Maintain a modest and professional working attitude at all times , Whether in front of your leader or a novice , Everyone likes serious and modest working partners , Who likes to work with an arrogant person every day ？