Forum Posts

Md Rifat
Jun 16, 2022
In General Discussion
They will not do it first. If you don't do it, you won't be wrong, but if you do it, it will be difficult to delete it if it is found to be wrong later. Here, I would also like to say job function email list one more thing to the friends who are new to the product: If you want to make a job function email list user-oriented product in the future, you must be the party with the right to speak and decide, and try to avoid entering the project-based Party B team as much as possible. Because Party B does not have the decision-making power over the product, When we lack the right to speak about the job function email list product, it will become inert over time, resulting in a lack of thinking about the product, and eventually job function email list become a microphone that only needs to be developed and can only draw prototypes. tool man. 2. Reject demands that do not improve efficiency A large part of the requirements are put forward by various business teams. The business teams are usually marketing, operations, sales, channels and other departments. They also often put forward some requirements that "can improve product efficiency". You can’t just let them go because the other party has passed job function email list on performance anxiety to you, and you can’t do it “smoothly” just because a certain function job function email list point is small. It's the same sentence: if you don't do it, you won't be wrong, but if you do it, if it's wrong, there's no way to undo it. So how do I assess their needs? In addition to clearly introducing the background and purpose of the demand, I have two tips to share with you:
You Can’t Just Let Them Go Job Function Email List content media
0
0
4
 

Md Rifat

More actions