How do you go from being a programmer to a product manager?

<> why do most programmers switch careers to become product managers? What are the reasons behind it?

Product manager is a position with relatively low hard requirements, especially suitable for program apes to change careers.

Programmers have a great advantage in turning into product managers, because they understand the implementation process of the product, so they have a considerable say in the time of the project, which can ensure the progress of the project and help the future expansion and upgrading of the product, so the product manager transferred by the programmer is very sought-after.

The foundation of an Internet company is Internet products, so the position of product manager is the core. As long as you learn more about product marketing and operation, and have more communication skills, product managers born as programmers will naturally have a great advantage in the market.

Internet product managers can also change the world, although they can't save the world like Superman, but they can make the world a better place by releasing new products and optimizing old products, whether the world is a virtual world that brings us a variety of rich information and various experiences, or a real world that facilitates daily life and improves the quality of life. So with such a mission, it is a very rewarding job to work as a product manager.

There has been a lot of clash in the industry that product managers are "the closest core position to the CEO". In some "product-driven" Internet companies, the importance of product managers has even risen to the CEO level.

It's easier to switch to a product manager, and you may have a product manager job in your past experience.

In the reality of the contempt chain, the programmer is downstream of the product manager, so everyone wants to move to the product.

The product manager does not have a specific corresponding major, and can only say that psychology, computer science, and economic management majors have a slight advantage, but they are not a decisive advantage. Even if you are a sinkhole professional, as long as you have excellent grades, excellent ability, and enough internship experience, then you have a good chance of going ashore.

As mentioned in this question, how do R&D programmers change products and whether they want to change products, it can be seen that the person who asks the question should be good at thinking, positive and have the courage and ability to transform products. In terms of experience, I personally think that it should be a good direction to do R&D to products.

Because it is rumored that no one wants programmers after the age of 35, there will be many people who want to find some "sustainable" jobs.

After doing development, your logical thinking is clear, and you only need to transform your development thinking into product thinking. In addition, the requirements document written by the general developer will be very clear, because the development has made it clearer what kind of requirements document is needed for development.

With the continuous progress of society and the continuous development of the Internet and technology, many repetitive jobs will be replaced by artificial intelligence technology. As a result, many people in society will have to face unemployment or job transfer. So what position can't be replaced by artificial intelligence technology?

The Internet product manager is Hail, and Zheng is one of them.

There is a saying in the industry that product manager is "the closest core position to the CEO". In some "product-driven" Internet companies, the importance of product managers has even risen to the CEO level.

The programmer has to hide a knife in his drawer, and he has to take it out at any time to cut the product manager who often makes unreasonable needs.

If you want to do something closer to the user, then choose the product, if you want to understand the technical principles more deeply, then take the expert route.

In the reality of the contempt chain, the programmer is downstream of the product manager, so Yuan Song everyone wants to turn to the product.

Of course, if you understand the product principle, you can find that it is closer to the needs of users and programmers, which is the breadth of product managers.

As we all know, programmers are one of the high-consumption occupations, and the unstable hunger and high-intensity workload will make the body rotten and have various problems, so it is also a young meal, and changing careers to become a product manager is also to choose a path for your future life, so as to make more money.

The job of product manager does not have too high requirements for previous work experience or education, and then filial piety and these two jobs have a joint cavity system, as a programmer understands the attributes or nature of the product, the programmer's communication skills are very strong, so he can be well qualified for the job of product manager.

Because being a programmer is too hard, I often stay up late and work overtime, but the salary is not very high, and the work of a product manager will be easier, miraculous and more valuable.

This is because the salary package of a product manager is no lower than that of a programmer, and there is more room for promotion as a product manager.

Personally, I think that if you change careers and return to the manager, it is still more difficult, because the daily work of the program escort is relatively fixed, but for the product manager, he is involved in a wide range, so if you want to change careers, you still need to continue to learn.

The difficulty is relatively large, different positions have different career plans, and if you want to be a successful product manager, you must have very good communication skills.

The difficulty is still relatively large, there is a certain difference between the two types of work, and it also requires different experience.

The position of product manager is not really like the book that everyone talks about is a product manager. Don't just tell people that I've changed careers to become a product manager, it's not that simple, unless the company is added by you or you're talented, and you're the legendary genius product manager.

Daddy is now a product manager, and he did research and development for three years at the earliest, and then had the opportunity to be a requirements analyst and a business-oriented project manager, and slowly got a feel for the business and user experience, and then worked as a pre-sales consultant for a few years before slowly starting to turn to products.

If you want to become a product manager after a year of programming, it is difficult to do it in one step, so it is recommended to run in small steps, distribute the implementation, and start with the requirements or product assistants.

The three core competencies that product managers need the most, business, technology, and user experience, are what I call the three axes of product managers. As a programmer, you have a good technical foundation, and communicating with R&D colleagues in the future is your strength. Communication is more empathetic, and it is more conducive to the implementation of a good idea through demand means.

From another point of view, a programmer-turned-product manager has a big problem, at the beginning, when he sees a requirement or a problem, he always wants to go to R&D in one step, which actually lacks the process of demand analysis and scheme design, and this ability happens to be the core competency of a product manager.

In addition to technology, you need to exercise your business sensitivity and increase your user experience design ability, which is not achieved overnight, that is, because the difference of business and the user experience requirements of the product are inconsistent, so the product manager who has done very well in the traditional industry has become difficult to do well in the Internet industry and make a C-end Internet product, like a mountain.

Learning PMP is actually very helpful for being a product manager, the role of the project manager is to do the right thing, and the role of the product manager is to do the right thing, one is more focused on execution, and the other is more focused on planning. However, it is not useless, and the product manager also needs to control the release progress and release quality of the product, so some of the schedule and quality control methods mentioned in the PMP can still be used.

Of course, by participating in some product manager training as a stepping stone into this position, I recognize, you can learn some theoretical methods and basic tool skills, but if you really want to work in this industry and become a real product manager, you still need to improve your ability through actual combat, keep thinking, iterate your cognition, and really change careers to become a product manager.

Development and product manager are two different job positions, development is mainly about implementing the design, while product is mainly about research design and product life cycle management.

The most important aspects of a product manager are: market research, demand analysis and product planning prototype design, assisting in development or leading team development, product pricing and promotion planning, market feedback and iterative updates, etc.

Turning from developer to product manager is actually a good direction, and the product manager understands the technology and can quickly get the solution. But how do you get started? Personally, I thought that it could be simulated based on the above aspects.

First of all, you select a project for simulation, continue the virtual research and analysis and write a requirements report, and then make a high-fidelity prototype design and select a technical solution based on the requirements report. And then implement this product, i.e., coding tests, etc. Through these basics, you can understand the general process.

As for promotion, pricing, and iterative updates, these projects that have no actual reality may not be accessible for the time being, but you can also try to do it.

As for those documents, you can search a lot, and you need to write more according to those formats, mainly to describe the functions clearly. Then use the prototyping tool to design a high-fidelity prototype, and the rest is how to implement the product, promote pricing updates, and so on.

This is just a rough simulation process, and you can basically know how to do it after only two or three projects. All that's left is to go through the project to temper and improve.