What if you have a great grudge against the product manager?

I think the reason why some PMs are so hated by everyone is ostensibly focused on the following points: there is a problem with the profession or ability itself; the uncertainty and repetition of things; Blame and blame for problems, and find no one (or even blame others) for problems; Enjoyed the illusion of personal expansion caused by the title, the betrayal of relatives and other character problems. The above can also be seen as the stages of negativity from accumulation to venting.

The professional ability behind this is a hard injury, and if you don't master the basic quality of any profession, then wait to be sprayed; Some of them are problems of human nature, such as the problem of responsibility and character, which are the shortcomings of every profession and even everyone; There is also a category that is actually encountered by anyone: the uncertainty and repetition of things. In a practical job full of distractions, who is not a prophet who can come up with a perfect product development plan?

Except for the fact that the requirements are not executable due to professional ability), have you ever wondered why PM never fights with users? It is likely that the core values of empathy, perception, creativity and thinking that have been able to survive are all used to serve users, forgetting that the first thing to apply is the people who are walking side by side with us.

Teach you a trick, if you're willing to do it. Give him all the features he could think of, and CC for everyone to see. Let him choose for himself, and you add to the description.

During the period, you can also discuss it with him in the group "humbly". The advantage of this is that people will think that you are a brainchild, or that you really love the product company.

Complexity isn't terrible, the most frightening thing is that page requirements change extremely frequently for a variety of reasons. The back-end changes are not visible, so only the front-end can be tossed by the product. I want this today, I want that tomorrow, it's understandable to think about it, they also want to make results, but don't be too low.

Sun Tzu said in the Art of War: "On the army to fight, then to fight, then to attack the army, and then to attack the city", the corresponding product design is the same, the worst way is to change the interface, do addition, no head like a fly random trial and error. Complex and changeable, almost 2 force majeure, there is only so much we can do about it.

Uncle Wolf said: Complain less, think more, and the future will be better.

The advice to you is to be clear that you have limited resources, and that you are doing your best to do what you are doing well. If the Lun family does not bird you, it is more appropriate to suggest that you ask your head what to do, he should know how to ask and refuse to reject, directly to the first is to hurt the harmony, and the second is not a rank, don't take the things that can't be done, and the next things must be done.

Paradoxical to misconception, you don't understand what the product manager is doing, he doesn't understand what you're doing. Therefore, you should learn what the product manager position involves, especially the parts that are relevant to your role. If everyone always divides their responsibilities too clearly, it will leave a blank in the connection, and this gap is simply the Chu River and Han realm, and if you fight for me, there will naturally be contradictions that cannot communicate amicably.

In practice, programmers and product managers often get to an eye on each other. When this situation happens, if you really can't convince the other party, you can find a few more people to discuss together, and the reason will be clearer and clearer at the objective level, so as to eliminate the product manager's incomprehension and achieve your own goals, you can try.

First of all, the premise of perfect coordination is to recognize the necessity and rationality of conflict, establish the principle of treating things not people, and treat problems rationally! Keep the goal on the same page, communicate the current reasons and goals, especially when the specific plan is tangled, remember that you are partners and need to work together.

I think you should communicate more, show the most sincere attitude of cooperation, each show a higher level of professionalism, the goal is the same, and communication will be no problem. Not only between the product and the interaction, but also with the development, with the test, with the UI, it must be the same.

First of all, you need to understand that your performance is not the work of the product manager, and you do not need to report to the product manager. So he is strong, he is strong, the breeze caresses the hills, he is horizontal by him, and the bright moon shines on the river. Can't you do it for him to be able to do it himself.

Eight meetings a day, ten hours of meetings, each business party takes turns, you have your schedule, I have my priorities, no one obeys anyone, no one relaxes. In the dead of night, I can finally discredit and write a demand, and I have to be "wiped out", so I can only silently carry the computer home and fight until dawn.

Imagine the product working.

At the time of reporting, the project data performance exceeded expectations, the value was clear, the boss was important, and the promotion and salary increase were upgraded all the way.

The actual product works.

Ten projects a year, eight of which sink into the sea, and the other two have a bunch of failures, and various partners complain, feeling that the existence of the product is a waste of money and labor. Luckily, there is a project that has produced results, and it is also well commanded by the boss, the development architecture is well designed, and the operation strategy is specified well. Products?

What can be the use of a microphone for the product?

Haha, after listening to the above, if you think it's acceptable, then congratulations, you are a real product person, a strong heart, is the most important element to become a product. Don't be nervous, just follow the trend and blacken yourself, at work, you will encounter the scenes you imagine and actually mention. As the product ability becomes stronger and stronger, the experience is more and more abundant, and the more and more proficient to pull through all parties, life will become more and more envious and move forward towards imagination (know how to deal with things and deal with relationships, so that you will not cry in the bed in the dead of night).

In addition to the above self-deprecation, I also have a few suggestions for those who want to change careers as product managers, such as cultivating a basic understanding of the product from 0 to 1

The most annoying thing is the newcomer who can't be brought in; If you are still a newcomer, you have to bring a newcomer; The newcomer is the little white of the whites.

1.Endless newcomers, since I joined the company, the company has never stopped recruiting, after bringing one, familiar with the wheel of the point of another one, and have to start over, it can only be said that the liquidity of Internet companies is really large.

2.I'm still a newcomer, to be honest, I've only been on the job for half a year, but I'm already an old man, which is really scary, and you may not be familiar with many things, but other people are still waiting for you to answer him.

3.Newcomers are the little whites of the whites, such as fresh graduates, some fresh graduates are really scary, you have to explain a lot of terms for a long time, such as what is retention, what is pv, sometimes there is really no patience, there is a feeling that the fire can't be released, and there are some studious classmates, 100,000 whys a day, so that your head is bigger.

The most annoying thing is the newcomer who can't be brought in; If you are still a newcomer, you have to bring a newcomer; The newcomer is the little white of the whites.

1.I can't finish bringing new people, since I joined the company, the company has not stopped recruiting, after bringing one, I am familiar with another one, and I have to start over, I can only say that the liquidity of Internet companies is really large.

2.I'm still a newcomer, to be honest, I've only been in the company for half a year, but I'm already an old man, it's really scary, you may not be familiar with many things, but other people are still waiting for you to answer him.

3.Newcomers are the little whites of the whites, such as fresh graduates, some fresh graduates are really scary, you have to explain a lot of terms for a long time, such as what is retention, and what is pv, sometimes I am really impatient, I feel like I can't get angry, and there are some studious classmates, 100,000 whys a day, so that your head is bigger.

The answer is very representative, I am also an Internet product manager who has just transformed, and I used to do ** promotion. Internet product managers need to pay attention to details, and must consider the problem from the perspective of users, that is, user experience, and the biggest difference with traditional product managers is that they must be fast.

Product development needs to be fast, and the product life cycle is relatively short.

Conflict Balance Ability.

The so-called conflict balancing ability refers to the ability to balance the conflict between user needs and normal product design and development.

Because of the needs of industry users, it is difficult for general product design to meet their requirements, and many times you will find that the requirements completely violate the functional and logical design principles of the product. The reason for such a demand is not the reason for demand research, nor the reason for users, but the reason for industry background and usage habits.

Especially when you are facing a large customer in the industry, what is more tricky is that the demand is the demand of the person in charge of the large customer in the industry.

At this time, it is necessary for the ecological product manager to have the ability to balance the conflict between the special needs and the normal product design, because these special needs cannot be ignored at all, let alone be stupid enough to find such a user theory that such needs are problematic.

In my experience, this is the time to choose a compromise that does not affect the normal product design logic and allows these needs to be reflected.