Product Manager is a need for personal charm, appeal, gas field of the post, we are very envious of those on the stage aplomb talk about PPT products, those and research and development design mingle products, those get everyone respect and trust products, but how to do, can people see people love it?
Product Manager Learning
The relationship index between the product and each team needs to be maintained.
For example, a new job may be the first impression you can, all give you 60 points. So every time you make a good decision, a good communication plan, you may add a point to you, but in turn, you did something wrong, you may be deducted 10 points.
If you let the relationship index go down and eventually get mixed up, and the teams see you scoff and defy Bufen, then you are a failure as a product manager.
so the key is: what is right and what is wrong? What can give us more points? What will bring our relationship index directly to the freezing point?
A few cases, let's see.
One, respect for your designer
I've actually done a lot of disrespectful things to designers, either intentionally or unintentionally. Some people may say: I respect the designer, every time he will buy food, smiling face. But this does not solve the core problem, the core question is: You can let the designer in their own field have enough voice.
My first disrespect for the designer is in the new period, there was a designer did a non-segmented design, I was the cognition that this is very lazy, in the front of the screen to cut the color number, I directly said in the content directly with the gray section, the designers walk after the time to avoid embarrassment, did not tell me the problem.
the second disrespect is that I want to do a project visual solution to the leadership report, and the designer gave me the plan is a seemingly deviant design, so I told her on the spot: "You this program in front of the leadership is certainly not going to, and then also to re-change."
after the second disrespect, the designer told me a truth, let me suddenly enlightened.
He said:
1. You do not deny my design, my design is the information you give me under the premise of my professional level, if I did not consider your design requirements, or your concerns, you can communicate with me to change the draft.
2. Even if the leadership there will not be, I can do another version, but this version of the design if not deviate from your request, I must keep, because this is my professional achievements.
3. You as a product manager, want to work with me to make a version of the plan, know the quality of this version of the plan, communicated to the leadership, we together to find out the leader's preferences, enjoy the works on-line sense of accomplishment.
4. If you are sensitive to the negative here, can not be my professional to explain to the leadership, I am afraid that any plan will not pass, we even be denied do not know why.
I was ashamed of his words, and after apologizing to him, I summed up the principle of two-point designers to get along with:
1. Give him enough information to let him know what he is doing.
2. Do not point to his field of expertise, give him space.
These two points are the respect of the designer.
second, to help you relax the research and development
for research and development, many times it is easy to get into a tense relationship with the product. For example:
1. The product plan changes again.
2. No one is used, no subsequent iterative optimizations are made.
3. The scheme given is outdated and unreasonable.
in this case, research and development is not possible to accept the smiling face, they not only in the code level to co-ordinate the test delivery to you a finished product, but also to bother with your plan, anyone will get into the irritability.
under normal circumstances, the operation will give the product a greater pressure to do what function must be on-line. But operations are often aimed at a breakthrough in the functional point, rather than the global version planning considerations, if the product manager with the operation station to the development, will lead to the development is very passive, each time is urged to rush to go online some features, there are flaws and responsible. The result is not at work, but in a good turn.
So how do you do it? I suggest that the product or the development of the United Front, for them to do tradeoff programs and priorities, let them know what to do, what can be done, why this arrangement. With a long-term planning, instead of urgent needs, let them on the future work arrangements and trends are expected, and not every day nervous and afraid of products to knock.
This kind of relationship goes on, research and development is actually more relaxed, because they know that the product manager is already blocking some needs for them, do some processing work, they just need to write code, unconditional trust can be.
Let your research and development to relax around you, the back unconditionally to you, you have succeeded.
third, communication and not behind closed doors
Why does a lot of recruiting require collaborative communication skills across teams? is because the product manager: More than one team, one more times the amount of communication. The truth is very simple, if it is the internal team, everyone in the morning together to open the station, daily communication progress, naturally enjoyable; but what if it's an outside team? Need a correlation schedule? Daily progress is not synchronized, it is easy to lead to test mismatch, delay, the effect is not ideal.
so the more complex the project, the more communication there is. Product managers work overtime not because of the number of jobs, product managers can think anytime and anywhere, think clearly even if the work is done, rather than study documents and prototypes every day. Product Manager overtime is because of communication, in the work time and everyone to exchange, occupy a lot of time, so only in the off-hours to complete their personal work.
If you do not communicate, there will be problem points, the problem is either delayed or cause the demand side dissatisfaction. The dissatisfaction of the demand side will be transmitted to the cooperation team, will lead to suspicion and irritability, if not a person to stand out to direct traffic, the result is blockage.
Product managers like traffic police, it is true that you have to understand the road command, you have to learn the traffic dispatch, but your main job is to stand in the street, to see clearly a problem point, to dredge them up. A good product manager does not have the ability to landing, but also in vain. Because the threshold of this thing is not high, as long as you stand in the overall position, to see which car should be reversing, that a car should wait, you can do well, rather than rely on the station behind closed doors.
So, do not ask what kind of product manager is attractive, good product manager does not need Yan value, do not need to listen to sound, do not need to be versatile. As long as you can stand your position, take out your attitude, treat your partner well, you can also see people love.
How to be a product manager that people love?
