Product managers often make mistakes

Look around, see friends, see colleagues, look at our immature circle, good product managers are always very few. They have already made the mistakes they should make, and then they get better.

Reflecting on my long history as a product manager, I have made mistakes that I've committed before, and I've seen them when I'm chatting with friends, so that we can all be alerted.

1. Take it for granted.

This is the biggest mistake often made by product managers. We got a demand, we thought about it, and then we thought we were right. Because we used a lot of similar products, think a lot of similar things, and so on. We also want to do market research, but the long and often unreliable results of the city, often let us more overwhelmed. So we reflect: what else can we do besides take it for granted?

In order not to take it for granted, we find the target audience to listen to the demand, we draw the user model, we brainstorm, we strive to make each step of our own more reliable, hope that the final results prove that we are not taking for granted. Alas, we are not easy.

Of course, we don't want to take it for granted. How to get rid of the component in the initial stage of the project is a huge problem for the product manager.

2. Lack of communication.

Product Manager, as a product of the spiritual leader, we need to put our ideas, so that everyone on the team clearly clearly. At this point, communication seems to be extremely important. You have done ppt, written documents, documents and illustrated with audio and video; You meet again and again, and you emphasize the core functions and features of the product every moment. But countless times you have sadly discovered: the funnel principle is absolutely the truth of the special. Even you have no alternative to the existential creed: others are hell.

Yes, no one can fully understand another person. Thankfully, making a good product doesn't require a complete understanding of everyone in your team. Communication itself is a lot of skills that everyone can learn.

Well, there's a magic in communication. That is, never feel good about yourself and others are stupid. Listening is always more important than expression.

3. Ignore the prototype.

I prefer any product that needs to have a prototype phase. The prototype phase is a thinking and verification phase. The experience of the last two or three years is that we are all aware of prototyping, but the prototype does not play a real role and does not allow us to discover potential problems in the product. At this time, I would like to worship those who created the game category of people like Miyamoto, seats Meier, Peter Morinhox and other people. Only good, thorough, exciting prototypes can make them happy for thousands of players.

The prototypes aren't for the hell of it, XD.

4. Change of requirements.

No one is perfect, and we cannot insist that everyone is a great man. So there are times when we make mistakes. We often find ourselves thinking wrong and we need to change our original needs. However, in the prototype stage after the implementation, that is, the stage of thinking completed into the construction phase, the demand is really not a person's business, you this shot head, designers, front-end, back-end, UE have to follow you change Ah xd. According to incomplete statistics, the failure of all products, 60% of the reason is the need for changes too often led to the implementation of the people discouraged without thinking.

It is one thing to make a product and build a house. When you finish drawing the architectural drawings, you start the construction. You want to move the bathroom from east to west to move the study from south to north, hey, it is not a simple matter.

Certainly not to say cannot change. I believe in responsible product managers, the more the need to change the future product will be better. But not too casual.

5, the boss said ...

For the product manager, there is a disaster, called "the boss said." The boss says he doesn't like red. The boss said the product was for the elderly. Boss said the login box to the left is very eye-catching ...

What is the scariest person in the world? Everyone has a boss. But a product manager who knows how to deal with his boss can succeed.

The boss has a face-saving, but the boss wants to make money. Obviously, your product is not all for your boss, so most product managers after the "boss said", or change the demand, or biased direction, or change the progress, or what.

You want to be a successful product manager, learn how to listen to "Boss said", or learn how to deal with the boss, is a very important skill.

6. Failure to integrate resources effectively.

I have all of you in the course of the project, the deployment of manpower, resources are called resource. Your biggest headache must be the staff problem. The programmer can't understand you anyway. The designer has been livid with you. And you think they have a real problem with their abilities. You want to change to a more tacit understanding of the people. You'll have to call the HR manager or the boss directly. Whether you succeed or not, it boils down to how well you can integrate your resources.

Or, when you do half way, your product is not being looked at, the boss is unwilling to continue. It is also one of the resources to be able to persuade the boss to continue to invest in the project.

According to incomplete statistics, all failed products, 90% of the reason is attributed to resource integration is not in place.

7. The project cycle is reliable.

The boss always hopes to wake up the next morning and find that the project is complete and start making money. The product manager hopes to wake up the next morning and the project milestone has been completed. But hope is not reality, desire is just desire. Most product managers don't see what they should see at a given point in time. Delay is our eternal destiny.

Every time you fall into the trouble of stalling, you should understand that your team of partners, who do not want to delay, who know that youth is invaluable. The essence of Project management is resource management, while time is the most valuable resource.

If you start a new project, then I suggest you make sure that the cycle is finely grained and validated carefully at each verification point. If your project is now in tow, don't worry, as long as every member of the team has the desire to win, it will soon be reliable.

8. Look directly at the product quality.

The vast majority of products, especially the Internet class, the product is not finished, but also must be in the process of delivery, further verification, transformation, improve product quality.

The worst case scenario is when your product comes online, users flock in and hubbub. According to incomplete statistics, 80% of the product manager jumped off for this reason. The remaining 20% are strong, they resist the pressure, look at the product from another angle, analyze the data, convince the team to face the quick action, and then inspire the user back.

Of course, most of the products are online after no one. The product manager of the big concept also needs to be responsible for this. Unfortunately, a lot of product managers at this time shrink, dare not take responsibility. Back then, when my team to withstand this pressure, those who followed my brother, have offered to resign, the whole I Hang Wai smile.

In fact, to reflect on why our products do not win users, this process will let us grow faster. Don't be afraid to sum up your lessons, don't be afraid of failure, don't be afraid to face the past.

9. Effective learning.

Many product managers, when they have made one or two or more products, tend to cling to success and forget to learn more. Even if they think they are learning, they are learning how to make their own experience an unbreakable dogma. Well, there's nothing more terrible than that. Do you think that Microsoft, which has so many excellent products for God's horse, will walk hard in the internet age?

There are fables that you must have heard about empty cups. If we want to have been on the product line to go on, well, to maintain an ethereal heart, naïve and curious, never think that they are right, always ready to meet new knowledge of the new theory of preparation. And never say forever!

There are 16 points in my original outline, and after the concentration, the 9 points are left. It is not easy to avoid these 9 problems altogether. But we can be used to alert ourselves: Don't make two more.

Share。

This article is in the knowledge answers the Netizen question, reconsidering, summarizes. The "Incomplete statistics" section of this article is a joke. )