What happens when a product manager doesn't know technology?

If the product manager does not know the technology, it may lead to the following problems and challenges:

Communication barriers: When communicating with the development team, the product manager may not be able to accurately understand the technical challenges and limitations faced by developers, and it is also difficult to effectively convey the product requirements and vision. This may lead to communication barriers between the development team and the product manager, and increase misunderstandings and unnecessary delays in the development process.

It is difficult to make feasible product planning: product managers are responsible for making product planning and roadmap, but if they don't understand the feasibility and limitations of technology, they may put forward unrealistic or difficult functional requirements. This may cause the development team to face difficulties, unable to deliver the product on time, or the product function can not meet the needs of users.

Difficult to assess technical risks and feasibility: product managers need to assess technical risks and feasibility in product development process to make informed decisions. If they don't know the technology, they may not be able to accurately evaluate the risk and feasibility of the technical scheme, which will lead to technical challenges and delays in the project.

Unable to cooperate with technical team: product managers need to work closely with technical team to promote product development and improvement. If the product manager doesn't know technology, he may not be able to understand the workflow and requirements of the technical team, nor can he provide effective guidance and support, which will affect the team's cooperation efficiency and product quality.

In order to better fulfill the role of product manager, it is very beneficial to know technology. Product managers can improve their understanding of technology through learning and close cooperation with technical teams, so as to better communicate with development teams, formulate feasible product solutions, and better evaluate technical risks and feasibility.