What is the duty?
1, to be close to the user, to be able to think from the user's point of view
Products are ultimately to millions of people to use, you can not very self to consider the problem, but to stand in the end user's point of view, and to be able to understand how users think, and how to use, this is the fundamental.
In addition, itself should be the product of the heavy users, and then to be able to experience a user to use the basic problems, but even so, please do not consider yourself to be the ultimate user, because there is a difference.
2, to analyze the needs, to be able to extract from the root of the problem
User feedback has tens of thousands of people, we need to derive from the user's behavior and psychological needs of the fundamental, and to verify this. Analysis of the requirements of the more difficult is not analysis, but to determine whether the user needs to meet, if the user's hundreds of requirements are fully met, the definition of the product may be a very complex freak. Here are a few ways to use:
A.80|20 principle: On the one hand the user 80% of the time to do things, need to help users solve, this is the user's pain point, on the other hand, the addition or not of a function is affected by 80% of the user;
B. Requirements are primary and secondary: the necessary functions, minor functions and functions that can not be used; Some of the features must be asked the user many times, if not what will happen to you have influence?
C. Less is more: one example that has been seen before is how to put a mountain (user needs) in a small bowl (the final product)? In fact, as long as the stone thrown away in the mountains, the inside of the diamond in the bowl is good, the stone is not what users want.
3, imagine the product, and determine its business model
The possibility of translating requirements into final imaginations and determining how they are realized and how to make money. Money can be direct or indirect, for example, some sites have several products, one of which can directly make money, while the other pieces are for its pull flow, but also indirectly money.
The imagined product should not just be "product", he should also include prophase development input, medium-term promotion, as well as later maintenance and related follow-up service, the middle of the cost-performance is to be calculated clearly.
4, design products, pay to the user to use
The demand is just input, and the final product is the output. For Internet products, I prefer to divide the product into three layers to see, the first layer is the performance layer, the second layer is the technical layer, the third layer is the service layer, three levels of detail how to achieve you do not need to participate (you have the energy of course the best), but the most basic situation you have to understand, or the possibility of implementation, how do you know?
Performance layer: Need to have the ability to interface, interaction, details, etc. can grasp very well. Some of the content is Wang's web site is usually ignored, but an easy to start, simple and effective products, is a can retain users, and let it spread to this mouth.
Technology layer: Here to be very strong, high-performance, high stability, high expansion. This is to support the rapid pace of product walking, rapid expansion of the foundation, I prefer a word, is to let the speed of the code to keep up with the speed of thinking.
Service layer: Before making a product that doesn't have anything to do with money, it's not a feeling, once the need to make money, this layer is directly exposed, this layer of feeling is easy to ignore, but he is an important part of the product, and the user experience, whether the future will use your products, and will be passed on to others, Notice here that the user's bad experience will be passed on to others.
5, the operation of products, and ultimately long-term retention of users and get more returns
This layer, also do not have to actually want you to operate, but must understand. Through what kind of way can finally make to pull the user, retain the user, turn into the long-term user, and the input and output of the first paragraph should also be very clear.
What qualities do you want to have?
Here is a brief explanation:
1. Comprehensive knowledge
User experience, industry understanding, interface design, technology implementation, promotion, operation ... You must understand!
2, good at communication
Be able to listen to what people say, talk to anyone, and dig into problems!
3. Clear logic
Thinking must be clear, at every point there is a clear or not judgment, if there is a third possibility, there must be a problem.
4. Data Analysis Ability
Have the ability to analyze data, and can make good use of data, in some cases, first make assumptions, then accumulate data, and then analyze and verify!
5. Learning Ability
The industry itself is changing fast, to learn things and to experience the product too much!
6. Understand Project management
There is no confusion between product management and project management, one is focusing on what is, and the other is focusing on what the task is.
7. Strong executive Power
We are not short of ideas, but lack of people who can do it!
8, passionate and energetic
This is the love product, has the responsibility one kind of performance!
9. Leadership
Must not be a person in the fight, who would like to fight with you, who would like to do the best!
10. Introspection and summary
Not ripe to mature bar!