call you over whenever they get a chance.

[rifattryo.ut11]

If you are a product manager who is relatively easy to talk to or has little experience and is easy to persuade, it is likely that the R&D will come to you to communicate and suggest that you don't need to do the requirements in this way. The design can be simpler. Why make it so complicated? It will be more laborious for R&D. In the first few years when I was a product manager, every time the logic rules of the requirements I designed were a little more complicated, I would hear the classic quote from the R&D director: "This design can't be done.



If I do it this way, my entire architecture will iranian phone numbers have to be changed." At first, I was forced to adjust the requirements immediately after the review because I was in the position of the director and it was not easy to talk back. But in my heart, I still despised it, "It's just that the technical level is not good, why are you talking so much!" Later, I had more work experience and had hundreds of dealings with R&D. I realized that as long as there was a slightly more complex function, the phrase "the change is too big to do it" would appear.



It's not that it can't be done, but that they don't want to do it. Of course, there is another situation where the R&D partner's ability is really insufficient. He has used all his life's learning but still can't solve the problem. What to do can only be to throw up his hands and let it sit. Tell the product manager "I tried my best but I really can't do it." Then let the product manager find a way to adjust the requirements. . The project time is too tight. Find a product to change the requirements and try your luck.