How the product manager convinces the technician

All skills are a means, real work is the king. This sentence is very scientific basis. In my 7 years of experience as a PM (product manager), it's important to convince others, especially the research and development, design, and front-end colleagues in the Research and development department, the most significant professional, not the so-called eloquence, communication, and data. We want to understand the truth, we must first, you have to use the expert way of thinking, expression and processing methods to think, communicate and carry out; second, you can always make the right decision.

A person must first believe that you can say the correct words, it is possible to seriously listen to what you say, and then you will be able to recognize your words. It's like we all listen to the command of an expert. So pm to be very knowledgeable and professional.

Some PM is very distressed: I clearly said is right, why does the researcher not listen to it? Yes, you may be right, but because of your usual performance, developers think you're unprofessional and they don't really listen to what you're saying.

Only as much as possible in-depth understanding of upstream and downstream related positions of professional knowledge, and have certain practical experience, in order to let us appear professional. In the communication with the relevant posts, obtain the trust of each other, and then adopt our opinions.

There are a few tips to introduce, but before I look at these techniques, I must repeat: the basic way to become professional is to learn as much as possible about the professional knowledge of each position, small skill is just a means, do not fantasize that only by virtue of skills can be truly professional.

Tip 1: Try to say the term

When we communicate with developers, try not to say plain, but to use terminology. It makes people feel like we know the technology. For example, once I and a client engineer said: "I want the pop-up window to be modal." After listening to the engineer, he was surprised to say, "Do you know the mode?" I said, "Of course, it's important for interactive design." So the engineer immediately changed the window to modal and didn't ask me why. So what is modal? With Plain said is a pop-up window, outside the window is black, or can not operate, only this window can operate, similar to Windows inside often pop-up annoying error prompts. But if you describe this with an engineer, you'll get a good temper and you'll have to change it, bump into a bad one-way: that's annoying, I hate windows bombs.

Tip 2: Think carefully

Try to think of all possible situations and their solutions before speaking. For example, you want to modify the location of a button, people naturally want to ask you, empty out the location of how to do, change the past will not affect the existing functions, users can not be accustomed to, and so on, if you can solve the solution, others will naturally follow your advice.

Tip 3: Let the other person draw their own conclusions

People have self-esteem, all hope that their decision is the right decision, if you always say "you are wrong, I was right" will inevitably cause other people's disgust. So you can first put the problems encountered, in the proposed solution immediately after you said: "You are experts in this area, if you think this program can be used, if there is a better plan I do not have any opinion."

People, usually lazy, since you can come up with a reasonable solution, and let the other party feel that it is his choice, usually will not embarrass you.

Skill 4: Mas disc

Not everyone is persuaded by the same words, and people are different. In my experience, treating engineers, designers, bosses is different.

The engineer should be organized, the logic should be clear and the data should be fastidious. For example: Scenario 1 will cause the data server overload, concurrent volume of 20,000/sec, and at least 10G of storage space, most importantly, we pay such a large price, in fact, only meet 20% of the users, and this part of the basically is not paid users. This big set of words, developers will seriously think about: Ah, in case the server down the responsibility is big, or with the plan 2.

Treat the designer to be feeling moving, because the designer is generally the art origin, the special sensibility. For example: elder sister, you change to me, in order to draw this prototype I have added a class yesterday, you do not change today, tomorrow refers to what kind of work, I have to do this project when online AH. Besides, it's not that I want to change Ah, is the sale over there for a while said users like this, a while said users like that, we also screwed them ah. Designers listen, are colleagues, who has not a difficulty ah, come on, overtime to people to do it.

Treat the boss to learn to draw a blueprint, for example: according to the results of competition research, this product is very promising, xx just on the line 1 months, there have been 1 million users, 100,000 at the same time online, income is almost about 4 million. We are better at technical, channel and government relationships than they are, and I think that as long as they can be launched within 2 months, the data will certainly be stronger than theirs. What's more, our product line is currently lack of user precipitation, and this product just provides a powerful social function to make up for the product line vacancy. The boss listens, the young man thinks quite clearly ah, into, give you two engineers, a designer, 10,000 project bonus, 1 months to make out for me. If the results are good, you will be rewarded with an annual bonus.

Of course, some people are very strong, he just when you are a brother, how do you say he did, no reason, no why. For this kind of person usually eat a few meals more, send a little gift, then nature help you.

Skill 5: Personality charm

A person must have a sense of humour, to learn to ease the atmosphere. There is no need to have a straight face every time a need is discussed. The joke, the gag, to the designer poured a cup of water, to the project hammer shoulder, to the operation of the little girl a few pieces of chocolate, to the operations of colleagues to buy a few bottles of water. You usually so pay attention to accumulation, when you need people naturally will not embarrass you. You can do it, you can't do it with a blind eye.

Finally, say it again: All skills are a means, real work is the king.