How can I become a good product manager on Google?

How can I become a good product manager on Google?

At Google, I have worked with the best product manager I have ever seen. I will create a list based on my own experiences. Since I am not a project manager, these conclusions are the result of my observation of the best product manager at Google.

1.Responsible for products and all related issues.

This will make you proactive. You are the first person looking for bugs, the first person who communicates with users, and the first person who worries about whether the product is qualified. You are always the first volunteer to volunteer various tasks for products or teams, such as making meeting records, sending emails to customers, filling in temporary vacancies, and prioritizing bugs, or quickly create an entity model. Always hold this idea:This is not the responsibility of others, it is your responsibility. When you do this, you will find 2nd items easier.

2.Incredible persuasiveness.

(I don't know how to do this, but I will see it every day.) You want to finish things, but you are not the owner, so you have to convince others. No team reports to you, and no one will follow your instructions.In Google, you need to convince others rather than give orders to accomplish things.If you are working on 1st items, things will become simple, because everyone knows that if someone attacks this product, you and they will be in the same trench.

3.Become an engineer.

I am not saying that you really need to write code for the product. I would like to say that you should be as curious as an engineer about the product construction process. You should understand the cost of product functions in the development process, and why the development cost becomes so high. What algorithm does that feature use? Why is this page very slow? A major architecture change has an impact on the product. Every engineer in the team attaches great importance to this change, and you should also. If you meet the project owner and want to know specific things, you should be able to explain some major engineering decisions and the trade-offs between the two. At Google, the best product manager will tryBecome more technical and happy.

4.Positive.

Your team may be composed of all engineers, and some of them may be very cynical. A very positive product manager can create an inclusive atmosphere in the team. Although it seems ridiculous to be positive all the time, it is contagious and your team will depend on it. Remember, you and the main Engineer (Technical Director) may list millions of frustrating things, but others in the team should not know about it. Because you are a product manager, you should not immerse yourself in your worries. This will help them better complete their work.You are the team's window and letter for other departments of the company.If you become negative, the team will think that others in the company view their work as well.

5.Do not recommend yourself.

This is obvious. If you do this, it will not only be boring but also be harmful to yourself. Praise others in the team. You and the technical director are already the main contacts of the project, so do not make any recommendations. If you use the hard work of others to win praise for yourself, you will not only be wrong but will not succeed.Be broad-minded.No matter whether it is a project blog or a lunch video conference with new product features, the best product manager should recommend other members of the team. Looking at Google's best product blog, you will find that the authors of these blogs are not always product managers, but members of the team. The product manager will actively recommend others. (Do not misunderstand the "recommendation" I mentioned here"
Promotion, which is totally different from promotion. By the way, promotions at Google are closely related to performance appraisal .)

6.Fearless.

This term may be better explained by writers, but please do not be confused by the literal meaning. The content reported by the best product manager to the leadership should be the same as that reported to engineers or designers in the team. If you say no to the decisions made by the product design leaders, you will certainly not succeed. Make a concise and clear answer andWithout fear, you can defend your team's creativity.