Product Manager experience (UP)

Wikipedia defines a product as anything that can be provided to the market, used and consumed by people, and satisfies a person's needs, including tangible items, intangible services, organizations, ideas or combinations of them.         My industry between the traditional and the Internet, the project manager to a large extent to undertake the project development, product planning and other important role, but the meaning of the existence of product managers have been plagued by people questioned. Most of the product workers are want their products, welcomed by users, but the reality is very cruel, the project manager body and multi-career, thinking and time will often fight, different positions require us to use different thinking way to think about the problem. The Product manager asks how the product meets the needs of the user to the maximum, and the project manager asks how to manage the project cost and project progress. Often in limited resources, a limited time to complete the scheduled workload. These two jobs are contradictory to each other and complement each other.         Often difficult to fit. Here's how I work as a product manager, and if you have a different opinion, you're welcome to shoot bricks.         Working methods I request the product design team weekly will be on their own product design experience to summarize, the word number should be in 500-1000 words between, and then by my weekend to review, if have good experience, get the Monday regular meeting above to share, study, work is nothing but condensed into three words "comparison", "looking", "thinking" comparison     To put it simply, we are always comparing our own products, comparing others ' products, comparing competing products of the same kind, and comparing potential competitive products. Looking for solutions, products, methodologies to meet the needs of users.     This process never ends, always on the way to find the best solution, someone walking in front, someone walking behind. Think based on the information you get, analyze it, and find out if you can innovate and transform to meet the needs of your users.         It is also a painful process of repeatedly validating ideas back and forth. Working methods commonly used are: product planning, data analysis, user research, demand analysis, functional design, project management, agile methods.
Thinking starting point: What kind of product can we use and what problem is solved. What are the similar products? How are people developing now? Whether such problems have commonalities.     There is no good way out.     Where are our target users, what kind of a word selling point to impress each other. What kind of products and services can we offer, and what are our core competencies? Whether our products have a competitive position in the industry as a whole.
Product Manager responsibility: Brand building, marketing, that is, planning the product life cycle. Listing strategies for products, pricing strategies, integrated marketing strategies, sales and distribution
Demand analysis: What is the demand, the color-eating sex is also, is the demand.         In this case, we have to mention Maslow's five needs theory: physical needs, security needs, social needs, respect for demand, self-fulfilling needs; This is an excellent product manager skills, analysis needs before we need to collect requirements, the method of collecting requirements are: data analysis, questionnaires, user interviews and other commonly used means, the user is the source of demand, we are closer to the user, the more we can get the most real demand pain point, and to understand the needs; We need to process the analysis of demand, the user needs, into the product requirements, we are always in the user-centric, but not to meet all users.         Instead, focus on the value of the core user (combined with business goals) to meet the needs of the core users, and if the needs of all users are met, the product becomes bloated and sibuxiang. Requirements analysis often used methods: revision, usability testing, quantitative do: data analysis, demand acquisition: Requirements tab; field research, AB test, Diary research, Card classification, self-demand, demand ultimately to translate into product demand, remember to do less even do more.
Strategy: We must constantly replenish our knowledge, don't let the soul keep up with the footsteps, need to think positively.     There is also a need for some simple feasibility analysis, such as asking more questions: where we are. To use our values, there are bigger picture, scan the market, analyze competitors, self-analysis, analyze what position in the market now, that stage.     Where are we going. The top level of the macro user needs the direction of where we can go into a field.     How are we going to go. By assessing the available resources around, everyone offers a proposal, a minority discussion, and a person's decision.
Tools (I prefer hand-drawn sketches) demo:axure, Dreamweaver; collaboration tools: Google Docs,office Live,wiki,
Thinking: Mindmanager,freemind,xmind All rights reserved Lyuzh Zhuoheng Lv@126.com