Excellent product Manager: Don't put too much emphasis on your ideas

Article Description: do some summary and introspection of product manager.

If you have done those kinds of occupations before, this is not a bad thing, on the contrary, this is your advantage, as long as appropriate in the product planning process to play, is also a good thing. Let's talk about the transformation process from the following points.

If you want to be a good product manager, at least have a peace of mind, if you do design, do development, there is a certain degree of passive implementation of the elements in the words, then the product manager is the overall product of the overall GRASP and progress recommended initiative is a very positive attitude, It's hard to adapt to this change if you don't change the mindset and focus of your previous career. I particularly agree with Peshoron predecessors, to have "I" and "ego" a mentality to treat the role of product manager. At the same time, if you suspect that you are a novice, all aspects of experience, there is inferiority, self-confidence in the psychological factors inside, and in the short term is not willing to change, then do not do product manager this career. If you do not have self-confidence, not strong, difficult to make the right and decisive decision, then a lot of people around the impact of your product core goals and values, to the end is to help others, help the boss, help the company to do products, it is not possible to make products for users. So the mentality does not change, it is difficult to have a breakthrough in the nature of work.

First of all, to understand their own product managers in the company's current situation and situation, I want to promote the point, line, face, do not blindly complain about the demand did not do well, the process is not standardized, technical interference requirements, testing old bugs, because the source of these problems is still not done, for example, three people write a same demand, may be different ways and means of writing. The same requirement three people write will have three versions. Therefore, the first to learn to write requirements statement documents, business flow diagram, wireframe, the function from the surface to every point to explain clearly, so that the business logic completely clear, the most important thing is the specification of the document writing methods and format, preferably with developers and testers can understand the situation down to write. And this you can only through practice and analysis to find the most suitable for the current product requirements of the document specification method. Do not believe too much on the network of some document norms, it is necessary to die in accordance with other people's way to do, this is very unwise, and there will be no substantive changes.

Take into account the overall strategic layout and direction of the product, at least in your heart to have such a firm belief, do a good job of global functional planning, business process logic sequence, function priority level, second to the interaction and user experience or design these performance layer. At first you don't have to focus too much on the user experience and the visual performance of the UI, especially the Axure prototype. Make a product prototype, even if you are drawing a rough wireframe, as long as each function and link and reflect the reminder mechanism to do, this is more important than anything. Even for a while, I was stuck in it. Do not excessively sink into a technology interactive implementation effect, there are many interactive effects, a word can understand things, spend 2 hours to do with the prototype, I really do not see what the benefits, or that sentence, as long as the team can understand your thoughts on the line, as far as possible in the requirements of the document to make it clear on the line, If the prototype is for future feasibility testing and user experience research, it is another matter.

Interactive designers turn over the biggest drawback is to see what functions are not, think this user experience is not good, that user experience is not good, finally nothing to do out. But user experience is only a "point" in the product planning process, do not go to this part, do not emphasize their own ideas.

A few days ago in Pmcaff saw such a picture, mainly to say that the product manager's ability model, of course, this picture almost the product manager to have the skills and responsibility to refine the scope of the work is very clear, but I still think this more or less exaggerated, there is a certain reference and learning value, Because a product starts at the end of the line, different stages require a product manager to demonstrate different skills and decision-making capabilities, and your skills and experience determine the nature of the product shift.

In other words, in the mind at least to understand their current strengths and weaknesses, if quickly let their product business ability to upgrade is the essence, more important to learn and predecessors more exchanges, learn to think actively to solve problems and improve their own.

I probably said that a good product manager must have:

Skill Tools: Office Office software, Mind Mapping, Visio, Axure, PPT.

Competency Model: Global view, requirement analysis, requirement document writing, product planning, execution and driving force. 6 Communication and coordination organizational ability: to be willing to run around, coordinate technology, testing, UI, high-level, organizational review, discussion, grasp the product from the beginning to the line of the process of control, the ideological have a macro understanding, implementation of the GRASP to be specific to things. Say 1000 good ideas and flow control do not do one thing to the jolly and practical.

Keen observation, user behavior analysis, user experience measurement of the dimensions and standards, visual design of the basic knowledge is needed.

At present, I know nothing but the above points, but also can refer to the above ability model to improve their own.

There are at least a few frequent and product learning discussions of the site, or the tragedy behind closed doors is likely to occur in their own quickly solve problems, identify function priority ranking, executive power and driving force.

The problem is good, when often the problem is not good, we will receive feedback from the operation of the user needs, testing provided functional bugs, technical development requirements of the functional business strict logical confirmation, which will make a new product manager is a headache. It's not a good thing to get caught up in these petty things all day, there is a change in the mentality of the inside, if or continue to continue to these problems and spend a lot of human resources to solve, a long time mentality will certainly have a sense of frustration, to solve these problems must grasp the source of the problem, this version has no way to control, Then the next version should be prepared in advance, strictly controlling demand and maximizing the need to filter out the core functions.

Very important point, that is actively promote all involved in the product of the progress and quality of the follow-up, a functional needs to be completed in three days, not necessarily wait until three days to see the results, in this three-day process to continue to focus on the line of sight process and potential functional logic rules.

Product Manager is the product as their own products to do, care, so that it can allow more users to accept, that is your value embodiment.

Why does the process exist, specify a new process and specification must have its purpose, without figuring out the root cause of the problem blindly to develop product planning process and related specifications also require other departments to support you, this I have done before, this lesson let me understand, All the processes and specifications are just for better service product derivative process, not limited, just a kind of auxiliary means, rely on process and system to prop up the product, it is difficult to embody the spirit of teamwork and tacit understanding. Of course, it needs to be used properly when necessary. Method used when, used to the blade, there will be a multiplier effect

Do not expect everyone to understand your ideas, including the boss, why? Let me tell you, no matter how a product company strategic planning and layout is, one of the core values it relies on is the motivation of the user's needs, so when we can't convince the leader or other department to agree with our proposal, it's best to add the user research and user testing mechanism to the product development earlier. There are a number of ways to get the user data to the town as much as possible.

Finally, one more point: executive power, say too much is useless! To do, to practice, to have all the things about this product done right!