Product managers do the acquisition, sorting and definition of requirements, and R&D will clarify the entire process of requirements realization.
In other words, product managers decide what to do, and R&D decides how to do it.
If an Internet product is likened to a dish, the product manager is responsible for defining who will eat the dish, as well as the cuisine, ingredients, accessories, and cooking methods.
R&D is the chef, who is responsible for "frying" this dish.
The product manager is the role responsible for designing the software, just business email list like the owner of a restaurant, who needs to define the food sold in the restaurant and tell the kitchen how to do it according to the customer's requirements.
R&D is the chef, who will take into account the way he cooks, the dishes he uses, and make dishes with special tastes to satisfy the taste buds of users and make dishes that match the menu.
But there will be a situation here: the customer wants to add some mutton to the kung pao chicken, without the pepper, and it needs to be boiled a little more.
The product manager has to tell the R&D the demand, and the R&D is confused business email list does the Kung Pao Chicken put mutton? Why don't you put chili? How to cook?
But customers have to be satisfied. After all, they have to pay more, so they have to make a plate of Kung Pao mutton with non-spicy boiled chicken.
Then the customer took a bite and vomited, what kind of thing is this?
The product manager is also very aggrieved. This is done according to your requirements, and this is also developed.
R&D is confused, this has something to do with me, and it's not what you conveyed.
The customer then watches the product and R&D fall in love and kill each other.