own health status and make
Posted: Mon Dec 23, 2024 7:09 am
Generally speaking, it's okay. If it really can't be changed, how to deal with it better? Dear friends! Have you ever encountered this situation? During the product development process, those smart R&D or testing partners always come to you to talk about requirements. Even if you have written the requirements as clearly as a dictionary, they will still "diligently" try to persuade you to change it. At this time, I found that some product managers are particularly "tough". They would say, "I will just follow this requirement. If there is any problem, I will take responsibility.
Who told me to be a product manager?" Some iranian phone numbers product managers are a little weak. As long as R&D can finish the work with peace of mind, you can change it in any way you say. At this point, everyone may be a little confused. What should we do about it or not? Should we stick to it or let it go? In fact, these two ways are not quite right. How to define end products and end product manager methodology Compared with end products, the biggest feature of end products is that they are oriented to users in specific fields and are much smaller in number, but they pay more attention to the in-depth mining of the operating procedures in the user's professional field-that is, they are more professional and more closely integrated with the business.
View details> Simply refusing as a product manager or arbitrarily changing requirements to please R&D are not the best ways to solve problems. Next, I will share with you the coping strategies for this problem. Why would a developer ask you to change the requirements? . The requirements are not designed reasonably and there are loopholes in the logical implementation. For developers, whether a requirement is well written is not to judge whether it is easy to use for users, but to study whether the product requirements document you wrote is logically rigorous. As long as your prototype has designed all the logical considerations and clearly written all the possible situations, the developers will not be able to find any problems and can only follow your requirements.
Who told me to be a product manager?" Some iranian phone numbers product managers are a little weak. As long as R&D can finish the work with peace of mind, you can change it in any way you say. At this point, everyone may be a little confused. What should we do about it or not? Should we stick to it or let it go? In fact, these two ways are not quite right. How to define end products and end product manager methodology Compared with end products, the biggest feature of end products is that they are oriented to users in specific fields and are much smaller in number, but they pay more attention to the in-depth mining of the operating procedures in the user's professional field-that is, they are more professional and more closely integrated with the business.
View details> Simply refusing as a product manager or arbitrarily changing requirements to please R&D are not the best ways to solve problems. Next, I will share with you the coping strategies for this problem. Why would a developer ask you to change the requirements? . The requirements are not designed reasonably and there are loopholes in the logical implementation. For developers, whether a requirement is well written is not to judge whether it is easy to use for users, but to study whether the product requirements document you wrote is logically rigorous. As long as your prototype has designed all the logical considerations and clearly written all the possible situations, the developers will not be able to find any problems and can only follow your requirements.