From the @ Know the problem has been sorted out, the original question is "Good product managers need what quality." Product Specialist and Product manager is the difference is responsibility, three-flow product manager and second-rate products are the difference is the professional skills, and second-rate product managers and first-class product managers is the idea of a different.
The following answers from the @ regular map:
Oneself is not a good product manager, so how to become a good product manager, only know to do a product manager must have some ability, hope to help you.
In the view of developers, you are the user, is the Product planner, is the designer, is the first to use their results, often give them the product problem people, the best understanding of what users need, can tell them which function priority high, those unimportant, can tell them what to do, why to do so, Occasionally you can tell them how to do it, and write beautiful documents and prototype designs.
So you have to have:
A. Some technical background (easy to communicate with technical staff, prioritization of functions, etc.)
B. Product prototype production capability (prototype document, requirement specification, flowchart, easy for research and development personnel to understand user needs, clear ideas, speed up the development process, etc.)
C. Product documentation capabilities (user manuals, white papers, to help developers complete other chores other than coding and technical research)
D. Communicate with them in a researcher's way, rather than a microphone (if you do a lot of work to reduce the development effort)
E. Collection and analysis of data (developers like to quantify things)
Research and development personnel most hate unable to control demand product manager, the demand often changes, just finished work is often overturned, the customer puts forward all demand does not analyze all request to do, the business logic oneself all understand product manager. The end result is that technicians have no output for a long time, no results.
In the eyes of users, you are technical staff, you are customer service personnel, you are pre-sales, you are to understand what they want, provide technical solutions to the people, can tell them what is right and what is wrong.
So you need to have:
A. Very familiar with the products and technology of your company
B. Familiarity with competitor products and newer technologies
C. Use graphics, Artboards, and other methods to guide customers to clear their mind and find out the real needs
D. Good at summarizing and analyzing, finding out the common needs
E. The courage to reject the needs of users and tell users why
Brainstorming can be very open, when planning and design can be collected very small. Users do not like the answer to the Sanbuzhi product manager.
In the eyes of the boss, as long as the product related to you can manage. Without the product, you can quickly deploy the company's resources, with the least cost of the product planning online. Products on the line, he expects you to improve product availability, improve product competitiveness, improve user viscosity, broaden product user domain, improve product income.
So you need to have:
A. Product planning capability (user group definition, product feature definition, core function definition, setting up competition threshold, functional planning)
B. Resource scheduling organizational capacity (project funds, hardware and software supporting resources, personnel)
C. Coordination and communication between departments (research and development, design, testing, customer service, operation, marketing, sales and other related departments of communication)
D. Product operation and promotion capacity (packaging, publicity, product pricing)
E. Keep up with the boss and quickly understand the intent of the instructions (the boss also as a user, understand the user needs)
F. Provision of decision material collection (competitor research, customer research, market research)
G. Cost awareness, time awareness (accounting costs, control the production line progress)
Bosses don't like to blame, often complain, often look for reasons, dare not bear, halves, no cost awareness, product online time dragged the product manager.
In their own eyes, the company is a handyman, other people do not want to do we are willing to do; All-round players, no resources, no one to do, we can top; want to be a successful product, there are many people use, many people say good; admire Chowa Lord and Zhangxiaolong; rarely admire a man, once admire pleasantly, as long as there is something new , is the first group of people to experience, often put Google, Facebook, T witter people on the mouth.
The following answers from @ Benjiang:
There are several points that I interviewed for PM
1. Ability to think about problems from the user's point of view
2, grasp the product's core user's ability to demand
3, the courage of self-denial
4. Ability to view the world objectively
5, Internet University is not a graduation, oneself is not heavy users do not good PM
If you need to add another one
6, experienced some rough, background complex some rebellious spirit at the same time understand the communication students often quickly limelight