There is a very interesting topic discussed in the community recently. I just arrived at the company and found that there are big problems with the development rules of many of the company's products. It happened that my last company did this, and I also category email list did some research. Do you want to? Give advice to leaders and discuss ideas with colleagues? The question this friend is worried about is, will I have no authority when I just came to the company, and no one category email list will believe me? The answer is yes, even if you have extensive product experience, colleagues will think that you are jumping to conclusions without knowing the company.
Of course, it can't push the development of the product line very well. When you work hard to enter a new company and prepare to show your talents, you always hope category email list that you can do well in a project or in one thing. Let the company feel that it can feel its own value, that's right. But usually you know very few people at this time, your e-mail about the company is category email list empty, and there is no project document and simple data support. If you get the first few weeks wrong, you will also lose the human foundation that predates the company's success. I have seen too many product managers start working on company projects as soon as they arrive at the company.
The effect of course is that they are in a hurry. In the first few weeks, they want to show their talents like crazy, lest the world be inferior. They think they should be on the front lines talking about products with users, discussing users with their teams, and being bold category email list enough to say that they are not afraid to take mistakes. However, without knowing the background of the company's products, you start to contact the product and think that you have made some decisions category email list that are beneficial to the product. However, in this initial period of time, you have nothing but a preliminary understanding of the product.