EDITORIAL, the topic tonight is both a summary of the work on their own more than six months since, and it is the accumulation of a self-growth, inadequacies also hope you heroes, the great God give correction, seventh certainly teachable, if and you can practice in their work, like Mr. Yang Ming said, but not know, just unknown.
Preparatory work before product design, that mainly depends on the seventh day decision-making team organizational structure, corporate culture, communication, collaboration and corporate leaders. Good product does not depend on experience, product manager, capabilities and advanced way of working. Like Steve Jobs is not God as a product manager talk to equate a good product, is beside the point above, the following entry to the topic.
One day, the boss suddenly decided to join function on a very large sound functions in existing products, or you want to take charge of a new product, as the product used to do, solve any problem, it has long been the boss stereotypes, before you say it is not broken Dian flutter, 000-consistently. Product Manager either choose to do or not to reason the necessity to convince the boss and the boss's analysis in this case. Here we focus on the product manager chose to talk about this product go how to think how to do, which is the focus of this article.
Many product manager needs to get from the boss here, then output BRD, BRD output but why even Datong expected in the gap between the boss, after several revisions boss is still not satisfied, after several modifications, product manager myself unhappy, trying to describe the boss of a large coffee sets have already been defined specifications are good, logical way, but always with a strong boss dismissed the ceremony, in this case, the product manager mostly distraught, crying in the corner, this is actually Contact product manager needs to get ready after work has a very large association.
Here we get the product manager chat in demand, how to do the preparatory work and how to refine demand boss given me here it comes down to three points, respectively, clear objectives, needs and develop refining plan.
First, clear objectives
After the product manager needs to get the first goal is clear, to think about how to do, how to do, to what extent to do. I would recommend the following when used to define common goals of my own to the three methods.
1, 5W2H analysis, namely:
1> What to do (What)?
2> What to do (How)?
3> Why (why)?
4> When (when)?
5> where (where)?
6> Who (who)?
7> How much (How much)?
2, 5-step product positioning, namely:
1) Who meet the needs?
2) Some of what they need?
3) We offer meets the needs?
4) How to choose the required point with a unique combination offered?
5) How to effectively implement these requirements?
3, FIG fishbone analysis
Fishbone able to focus on the problem why it happened? The reason concerns the team, rather than a symptom of the problem.
Fishbone diagram to concentrate on the substance of the problem, not the problem of a different history or personal views.
Fishbone able to identify all the causes of the problem or situation and find the root cause.
Fishbone able to analyze mutual relations between the various cause of the problem.
Fishbone also what kind of data collected provide guidance.
Second, the demand for refining
When we get the demand, in particular the demand is not clear premise, it is necessary to refine requirements, determine the authenticity of demand will not be required as a demand, not the nature of the product as a product form.
Kai-fu Lee, chairman of Innovation Works has made micro-Bo said: "A lot of engineers and product managers do not understand: the customer is not actually buy a product, but they need to use a piece of a product to complete a task or solve a problem well-known saying. the words: "the customer not to buy a drill, customers buy a cave. "
Product manager should not only ask the user: "My function is to satisfy you?", But also to understand: "? What are your needs and pain"
How demand for refined product manager, where I recommended approach is to build their own product managers need to pool demand, will focus on the demand for pool next article, here simply to talk about the role of demand pool, the pool can be a good demand for product help manager categorized collection needs, the needs analysis and screening requirements for product functionality, interactivity and prototyping, but also give a clear idea to product manager. Good pool needs to better determine the source of version iterations.
When we get the demand from the boss here, most are incomplete, which requires a complete product demand collection manager, product manager, in addition to over-rely on their own digging, the excavation begins outside the company, external mining mainly by users, customers and partners to get. Mining methods are user research conclusions, user feedback records, data analysis products and competing products analysis.
After we collect demand, we need to demand classified analysis, we will be divided into five categories, namely, functional class, data type, operation type, class and experience design class. Then we carry out in-depth analysis of each class which needs a method I used to here, four-quadrant positioning method, it is an important and much-needed, much-needed but not important, but not important and not important nor urgent need of urgent need, As shown below:
About four-quadrant positioning method, we need to note that, for a certain demand, product manager feel may be important but not urgent, but it seems the boss is important and urgent, while the other members of the department seemed like a UED not important nor urgent need, at this point may be disagreement and dispute, where I will recommend two methods, if UED department and the boss is relatively user to understand, here KANO model analysis to decide. Conversely, if the owner of UED departments and users do not quite understand, the user who creates portraits of recommendation to analyze the way here, right through the scene to determine the needs, behavior, age, environmental factors such as weight.
Finally, we need to demand screening process, screening mainly from three aspects to consider, a strategic positioning, two, product positioning, three user demand, when demand after the completion of refining, product manager output PRD, into the review stage.
Third, the plan
PRD UED department after review by the need to develop research and development programs into the product development stage, in the product development stage, suddenly changing needs of this often happens in the R & D team, even though product manager with designers, programmers war are swords, bee, but it has been determined to modify the severity of final demand needs repairs, if not to find problems in the development process, the final output of the product may cause considerable seriousness of the team. Here is the recommended method PDCA cycle management methods, namely:
P (Program PLAN): specific problems and possible causes and solutions assumptions.
D (implementation DO): implementation of action plans.
C (check CHECK): evaluation results.
A (processing ACT): If you are not satisfied with the results returned to the planning stage, or if it is satisfied with the results of standardized solutions.
Summary: Product Manager in getting demand, not hurried to find a reference, but clear goals, clear objectives in three ways: 1,5W2H analysis, 2, 5-step product positioning, 3, fishbone diagram analysis. After the completion of a clear goal, if not a thorough understanding of the needs, product managers need to fill gaps in demand and refining the core requirements, the recommended method here is product manager needs to have its own pool, complete demand for refined products output manager PRD began to enter the review, review invested by the product development stage, product managers need to plan, the irrational, the impact of product strategy goals, the team, the user threaten, injure, security functional requirements and non-functional requirements for early detection and propose immediately UED team convened a meeting to resolve.
Reproduced in: https: //my.oschina.net/hfq/blog/1829717