How can product managers better communicate with technical staff?

You can ask the technician what you don't understand, so that you can communicate better.

Communicate calmly and tell the technician what he wants.

For the technical person, he is more concerned with the logic of the function implementation than with your own abstract perception or thinking logic of the product.

Remember to keep a kitchen knife next to you when communicating with the product.

The attitude of communication between the two parties is very important, and the starting point and purpose of communication should be clear.

Accurately understand what the requirements are, what are the solutions given by the product, what is the business logic, and how to deal with the details of the interaction?

Communicate that your understanding of the need or the difficulty of realizing it, that there are higher alternatives, that it is unreasonable, etc.

From the perspective of the growth path of a product manager, there is a lot of knowledge to learn, which is divided into the following parts.

1. Tools.

To be a product manager, you need to be able to draw prototypes, and you should know how to translate ideas and requirements into technical and development languages.

Then the tools commonly used in the product must be proficient, including: Axure RP, Visio, XMIND, PPT, Word, Blue Lagoon, Jira, which must be proficient.

2. Communication.

In the process of project development, the product manager needs to communicate with many students from multiple departments such as operations, front-end development, back-end development, testing, and marketing.

This requires the art of communication, and product managers need to know how to deal with people, both internally and externally, including users.

For example, a very important part of the product research process is user research, user interview research, how to ask questions, how to let users express the problems in the process of using the product, these are all communication art.

3. Advanced Chapter.

This part is the hardest.

Understand the needs of the crowd and formulate a reasonable product strategy.

Understand the situation of the industry, understand the company's position in the industry and the form of competition, there are so many people in the team, there are so many functions, what to do first and then what to do, and what is the possible reaction after doing it.

Empathy, the ability to analyze data are a must.

Personally, I think it's the definition of the product. Then there are the following points.

Business: The product manager is first and foremost a business position, and his main responsibility is to maximize the business value of the product. Product managers should focus on product optimization to achieve business goals and maximize return on investment.

Technology: There is no point in defining a product if even the product manager doesn't know how to build it. This is not to require the product manager to be able to write, but it is essential to understand the technology and, most importantly, to know where to go.

This is even more important in agile development, where the product manager is the one who spends the most time with the development team.

User experience: This is the last but equally important. The product manager represents the voice of the user in the company, and he must pay attention to the user experience of the product.

This requires the product manager to step outside the team, test the product as a user, talk to users, and get first-hand feedback – especially for startups.