AsProduct Manager, we design products not only to seize the user pain points, design human interaction, but also to follow some micro-product principles. Specific product people need to follow a number of micro-product principles, this article will be introduced to everyone, hope to help you. 1. user demand deep digging to the end is the human dimension The depth of the user's needs, representing the level of the product. From the perspective of user needs to continue to infer, to the end must be attributed to the human dimension (greed, laziness, glory, social, beauty, cheaper, etc.). The need for human nature does not change greatly with the times. For example, if users say they need a carriage, the product manager will want to build a carriage, but in fact the deep-seated needs of the user is faster, so Ford gives the user a car, and essentially satisfies the user's needs. Here is also to encourage people to dig into the image needs, the use of empathy to understand the user's psychology, and ultimately deep digging to the user's human nature level of demand. It is recommended to take a look at the Suger teacher's proposalYuser needs analysis model. In "Everyone is a product manager2.0is detailed in the ". Let's not repeat it here. 2. Good products are continuously iterative We do a product, is to rely on the rapid iteration and gradually become perfect, it is impossible to do all the functions in place, the user needs are gradually expanded. Recall of the function of the iterative process, from the initial chat, then to voice chat, and then shake, circle of friends, and then the public number, information flow, search, and then to the current small program, is through continuous iteration of new functions to continuously meet the needs of users, user groups and thus constantly expanding, to achieve more connections. many product managers in the iteration of a function, always want to think of a comprehensive, thoughtful, experience to be perfect to dare to go online. There is no problem with the beginner's mind of this approach, but the problem is that it takes a lot of effort to move a single function from80points to do -The best time to collect feedback and performance data quickly. The courage to be imperfect is a rare quality for a product manager. the core of the lean entrepreneurship approach is to advocateMvp(minimum feasible product), the pursuit of rapid product launch, continuous based on user feedback and data iteration, in the end can quickly become perfect. 3. the core of product design lies in the business and operation Process from the interface design began to do product design is a lot of novice product manager of the way, although no derogatory meaning, but the interface design is just packaging, ugly is not okay. The key is whether the goods in the package can solve the user problem. The more core design is the operation flow of the function and the final output effect. For the tool attributes of the product core, it is much more important to work and to be useful than to look good. This aspect is more agreeable to the view of sterling silver. The product is more important to choose a promising track, product prototypes,Uisuch as design is only add sub-items, not to determine the result of winning or losing the role. The product manager has to focus on more important areas. For example, research market, users, product positioning, thinking about innovation and differentiation of competition, simulating the user's real habits and psychology. 4. product features to be deep, concise enough a single product feature that captures and solves some of the core issues of a user, rather than several issues. As little as possible to split the function points, to ensure the centralization of functionality, so that the depth is concise enough. Often the wrong thing to do is to do a bunch of shallow and full functional points, resulting in a dispersion of the user's attention when using the product, and each function is difficult to reach or exceed the user's expectations. This is in fact with the macro less that is the principle of more consistent. For example, for example, calculating the battery loss function of an Android phone, the core key point is to accurately estimate the percentage of loss, followed by the time required to calculate it is short enough. Other information and data around the battery should not be extended in the battery loss function, such as instantaneous current, battery voltage and other information, this information for most users1is not understood,2is not much use even if you understand it. In terms of product function design only, the inverse example of this isAndroidversionAccubattery, example isIOSversionBatterylife. 5. The product must have the continuity, the stability good products to be able to continue, stable output, to the user with a stable and reliable impression. first, sustainability, the difference between the phenomenon-level product and the continuous product is the need and frequency of satisfying the user's needs. The product of the foot mind and face Meng is destined to be just red and then rapidly declining. Meet the needs are also non-demand, low-frequency. The demand for continuous products is often a requirement, high frequency, and has the characteristics of continuous value. stability, stability of the product, can be done every time80in order to give users a trustworthy impression. And that sometimes thepoints, sometimes -products will be not stable enough to allow users to wait and see attitude, and do not want to quickly try new features, and then gradually fled, product reputation is difficult to form. 6. Replace personal feeling with data support the principle is to emphasize data-driven product design and iteration rather than subjective decision-making based on personal experience. People's feelings tend to be inconsistent with the facts. Product managers should actively develop their own data sensitivity, learn to use data mining user needs, with data evaluation product results, so as to find the shortcomings, based on the data proposed optimization scheme, and data validation. when we discover a user's needs, we learn to use data to support and validate the need and frequency of that requirement, the size of the target user, and the cost, expected output, and revenue needed to meet that demand, thus evaluatingRoi. In order to prioritize demand, it is possible to combine product stages, market and competition patterns, plus different needsROIThe priority of this discharge will be more scientific. when the product single function on-line, to establish the effectiveness of evaluation indicators, and timely summary of the function on-line effect, to find the points can be improved and problematic, continuous optimization and improvement of product functions. again, data analysis capabilities and data sensitivity will increasingly becomePmcore Competencies, which is also an improvementPMproductivity and stability of the product program output of the tool. 7. combination of Practice and theory, re-practice and reflection in fact, these micro-principles are summarized, refined in my usual product practice, paper on the end of the light, I know this matter to preach. For each product manager, the methodology that he sums up will be more or less different from others. But the methodology of listening and learning from others is just a bunch of seemingly simple ideas and words, the real transformation of absorption also needs to be applied in the daily work, according to the effect and problems in the process of practice, and constantly summarize and reflect, this will really form their own methodology. When the methodology reached a certain scale, and then refined, you can get their own general product structure thinking, which is to do the final pursuit of products. Source: Network
What micro-product principles should be followed in making products?
