How to avoid being disgusted by programmers (RD)-to those bloody product managers (pm)

Editor's note: This article is the fourth article contributed by Miss X. The first article "a product manager who has not yet made reliable products is so alive", the second article "An Internet p-citizen who started his business for the first time was rejected by investors like this-written on a cold night without any letter of intent on investment", the third article is "do you dare to think male about Internet products developed for women-crying and tears from the white rich and beautiful women's tickets".

Recently, a guy who just worked as a PM (Product Manager) came to complain to me, saying that the RD staff (programmers) in the company's Technology Department were not very good. After a thousand times of requirement, I still understand the problem, or simply say "I can't do it". The expression is like a dead face.

The PM was so full of blood that Zhang JiaWu captured the idea of 10 million new products in his mind. He repeatedly complained that the RD staff did not cooperate. They had poor abilities, laziness, lack of ability to think, and had no taste. He also strongly condemned such things. "Wipe, I will learn programming tomorrow !" Ah, I found that PM really liked to say this very inspirational word!

Face to him, my heart suddenly melancholy. A few years ago, I was almost like this, and I was confused about it. But who knows this PM is a dumb in the eyes of many RD. As a female pm, I have worked with more than 200 RD teams in over 8 groups so far (a turbulent and tortuous career ), the tears of grievance will not be repeated here. I plan to keep my novels later. Today, I just want to talk about my summary about how PM gets along with RD. I hope you can better understand each other's "not easy" positions after reading this article.

There are two types of RD in PM's eyes: communication and communication. The latter accounts for 90%. (Haha)

Like me, you are a PM with no technical background. It is estimated that you will think that there are more than of the "rd that cannot be communicated" in the world. Isn't it! Every time you talk about a great product plan with high enthusiasm, looking forward to seeing RD's excited eyes, you will find that they are really not excited. The face-recognition RD will give a dry question: "When should I start designing the Draft? Are you sure you have finished writing the product documentation ." If you do not give face to face, RD will question you on the spot. "Do you have a clear idea about this new feature ?! My boss is taking a big picture, right ?! Is there any data basis for this ?! Have you done market research ?! Will old users lose traffic ?! Can I ensure that I will not change it after I go online !? @ # $ % ^ % $ # @ % # $ % ^ % "Is really not a friend!

Once there was a director of RD who thought he was awesome but could not keep up with the times. At the kickoff conference, he overturned all my needs and left me almost crying in front of a dozen old men. It is said that, after suffering, people will either become better or worse. This kind of urgent desire to deal with RD makes them listen to me. It is so strong that I learned how to buy rd through informal channels-for example, asking them to eat KFC, chat with them about the yellow joke, and show the black thigh with a low-case outfit. With these efforts, the relationship between me and RD has improved a lot. They started to open their hearts and explain where their negative feelings for new needs came from: Sometimes it is because they are too busy, sometimes it is because they really cannot understand the significance of this function (at least they certainly won't use it), sometimes it is because PM not only does not mediate the priority of the existing project, but also dream every day, they were very annoyed to think about something they didn't. The biggest cause of negative sentiment is that they lose confidence in the project and feel that there has been no major breakthrough in the repeated revisions. Both the boss and PM should go to Shi.

Just as I was complacent and thought that I had won the battle by the beautiful legs, a ruby programmer quietly told me, "I like your front teeth ." (Crow... You are really a creature that cannot communicate ...)

There are two kinds of PM in the eyes of RD: brainless and brainless. The latter accounts for 90%. (Heheh)

PM with no brains, RD guys are keen to abandon you. You may have the following reasons:

Reason 1: You don't have your own ideas. Well, what I'm talking about is that RD people "think" you don't have your own ideas. This topic is really bitter. Which PM does not have its own idea? It's just that there are too many ideas to come and become a PM !! However, the living environment of PM is extremely difficult, and many decisions are beyond your control (especially when you have a boss with a strong mind ). As a result, some PM chose to shirk their responsibilities and put them together, "the boss says they must do it." They are eager to clear the relationship and emphasize that only the boss is stupid. No, I am not. In this case, your image in RD is ruined.

PM must be the soul of the product. No matter what the old board decides, you must translate this decision into reasons that can be accepted by everyone and build your own reputation and trust. When talking to RD, don't say "I have been arguing with my boss for a long time, but he doesn't listen to me." This highlights your incompetence; do not lie and say, "I think the boss has a good idea." Then, I will give you some reason for being an idiot. This is especially hypocritical. A better way to deal with it is to be open and honest, and to say your own real thoughts. If you think the boss is really overactive, you should also explain why the boss has such an obsession (it was forced by investors, I was forced by my wife, but I was still jealous of what my competitors were doing.) Then I comforted the hard work of the RD and showed my determination to work with them.

Reason 2: You have no logic. It is said that the PM that can make awesome products should be both emotional and rational, because awesome products can directly stamp human nature and meet the user's physiological and emotional needs at multiple levels, this requires that PM is sensitive to the details of life and has rich emotions. However, a PM with rich emotions usually jumps in mind (for artists, all of them are like this), and their mood fluctuates greatly. When they are depressed, they will smoke for an afternoon in the balcony, when I was excited, I sat down on the toilet and took my cell phone to write documents. At this pace, RD people could not afford it. They think you have to eat brain fragments! (Intercept: after my previous article was published, someone suggested that I take my brain fragments !) Therefore, in terms of PM self-cultivation, you must have an easy-to-use emotion and a rational logical thinking to support every inspiration.

You can ask yourself three questions: 1. Does this function serve the main business of the product? For example, does the software for listening to songs need to switch between daytime and nighttime modes? If the use scenario is less than 10% of the overall cost, you are advised to spend time at home after you learn to write code. 2. What is the technical cost of this function, if the expected work volume is not intuitive enough at the time of employment or the number of days, go to the HR department to ask about the total daily salary of all RD staff, and multiply it by the required development time, this amount should be enough for you to think about "demand cost-effectiveness! (This is especially useful for startups.) 3. Can the effects of this function be evaluated? In this way, at least you can test whether your judgment is correct. In any case, you can accumulate valuable experience.

Reason 3: Do not trust RD's ability. Haha, it's just an intersection of feelings. In every tearful day, we are repeating this series: PM asked how long the RD function will take. RD said it should be at least three weeks, PM asked his technical friends, "does it really take three weeks? ", Kiyou patted the table and said, "What's the problem? I will do it in 3 days !" Then the two men frowned and began to discuss whether the company's RD staff were in poor capacity or laziness. I used to do the same, because I was afraid of being cheated because I didn't know the technology, so I hooked up with various folk technical experts and asked them to become a captain for me. In order to maintain their own image of Wei 'an, the military engineers usually boast a variety of exaggerated costumes. What's worse, the Military Division also ruined the trust between me and RD in disguise. (Oh, how painful it is to comprehend ~~~)

Finally, there is only one type of RD in the eyes of RD: better than yourself.

The remaining capabilities are not as good as themselves, and their existence has long been dispersed in smog.

........................................ .... I am the split line of the stream .................................. .........

Make RD think you are an excellent method...

With profound knowledge, understanding all kinds of dynamics in the industry, analyzing market trends, and looking at umeng data when it's okay, all kinds of new foreign products are used. Rd will think that you know everything, and your judgment will be reliable.

Mixed circles, accumulating a few awesome contacts, it is rare to take a photo and send it to a circle of friends when there is a dinner with a big man. From time to time, I want to answer some questions, brush my face at various activities, and match various cooperation, push the company to the lights whenever possible, which makes it easier to recruit excellent programmers and create a virtuous circle. Most RD people do not like to show up, so they will think that your contribution is irreplaceable (otherwise they always think that PM is a leisurely waste to read articles and chat every day ).

Whether it is a verbal requirement or a written document, the presentation of text and prototype graphs must be logical and organized. It is best to use the code writing idea to write product documents, the logic processing in the functional details is a matter of fact, which is very good for RD people.

When the boss asked why it was not yet online, he rushed forward and said, "it's my fault. I changed my needs a few days ago ".

When the RD staff are attacked at the same time by the needs of various departments, they should be given the most reasonable priority and promise to bear all consequences (including being scolded by a department director ).

Recruit a pretty intern girl to raise an eye for RD staff.

Give them a raise, give them a raise, give them a raise.

At the end of this article, I want to say to all product managers who are still struggling, even if your industry environment constantly limits your innovation and imagination, even if the programmers around you always suppress your enthusiasm and attack your decision-making and judgment, you feel that no one in the world is sure of your efforts, and no one understands your helplessness, you cannot give up. Do not forget the ideal, do not forget the initial heart. You are the hope of a bright future.