SWOTThe SWOT model is a common strategic planning analysis method, which represents the analysis of the enterprise's advantages (strengths), disadvantage (weakness), Opportunity (opportunity) and threat (threats). Application Scenario: Competitor analysis, evaluation of product opportunitiesPESTELThe PESTEL model is an effective tool for analyzing the macro-environment, including 6 major factors: political, economic, social, technical, environmental and legal.
Application Scenario: Competitor analysis, evaluation of product opportunities, strategic analysisUser Experience featuresFrom the user experience elements: User-centric product design, although the original book is about website design, but the same applies to mobile products. The user Experience feature model can help us to comb our products from 0 to 1 of 5 stages, or we can use these 5 aspects to analyze the competitor's product.
Application Scenario: Competitor analysis, product designMaslow's hierarchy of needs theoryMaslow's demand hierarchy theory is one of the theories of behavioral science, which was put forward by psychologist Abraham Maslow in the theory of human motivation. The theory divides human needs from low to high: physical needs, security needs, social needs, respect for demand, and self-fulfilling needs. Popular Understanding: If a person lacks food, safety, love and respect at the same time, usually the demand for food is the strongest, other needs are less important. Only when people are liberated from the control of physical needs, can there be more advanced, more socialized needs such as security needs.
Application Scenario: Demand MiningSeven Deadly SinsThe Seven Sins of the Catholic doctrine reveal the primitive instinctive desires of man, namely arrogance, jealousy, rage, laziness, greed, lust and gluttony.
Application Scenario: Demand MiningKANO ModelJapanese Professor No Jizho (Noriaki Kano) built a Kano model. Divide the factors that affect user satisfaction into five types, including:
- Charm factor: Users unexpected, if not provide this demand, user satisfaction will not be reduced, but when providing this demand, user satisfaction will be greatly improved;
- Expected factor (one-dimensional factor): When this requirement is provided, user satisfaction will be increased and user satisfaction will be reduced when this requirement is not provided;
- Essential factors: When the demand is optimized, user satisfaction will not be improved, and when this requirement is not provided, the user satisfaction is greatly reduced;
- No difference factor: whether provide or not to provide this demand, the user satisfaction will not change, the user does not mean at all;
- The reverse factor: the user does not have this demand at all, after providing the user satisfaction degree will decline;
KANO ModelKANO analysis with four quadrant methodApplication Scenario: Demand AssessmentFogg Behavioral Modelto make a user's behavior happen, the product needs to have three features: behavioral motivation, execution capability, and trigger mechanism. in order for an action to occur, the user first needs enough motivation and motivation, and then has the ability to perform the action. The user has sufficient motivation and sufficient ability to execute, when the trigger mechanism appears, the operation will naturally occur. This simple model is a model of Fogg behavior.
Application Scenarios: Product design, interactive design, user experience design
Nielsen Ten Usability PrinciplesThe ten usability principles are presented by the man-machine interaction Dr. Nielsen for Web design, and also an important reference value for APP design. State Visibility principle (Visibility of System Status): The system should let the user know what happened and make appropriate feedback within the appropriate timeEnvironment-Appropriate principles (Match between system and the real World): The system should use the user's language, words, phrases and user-familiar concepts rather than system terminology. Follow the practice of the real world to make information conform to natural thinking logic. Undo Redo Principle (user control and freedom): Users often mistakenly select the system function and need to clearly identify the exit from this, without having to go through an extended dialog box. Features to support undo and redoconsistency principle (consistency and standards): Follow the conventions of the platform. The same terminology, function, and operation are consistent. Error -proof principle (Error prevention): It is better to have a more careful design to prevent this kind of problem than to have a wrong message hint. Easy access principle (recognition rather than recall): Minimize the user's memory load on the operating target, actions and options should be visible. Users do not have to remember the information of one page to another page. flexible and efficient principle (flexibility and efficiency of use): The number of intermediate users is much higher than the number of primary and advanced users. Designed for most users, do not underestimate, and do not belittle, to maintain flexibility and efficiency. Easy-sweep principle (aesthetic and minimalist design): The action of the Internet user browsing interface is not to read, not to look, but to sweep. Easy to sweep, which means highlighting the focus, weakening and rejecting irrelevant information. The fault tolerance principle (help users recognize, diagnose, and recover from errors): Helps the user recover from the error and minimizes the loss. If it cannot be redeemed automatically, provide detailed explanatory text and direction, not code, such as 404. Application Scenario: Product designhumanized Help principle (helps and documentation): If the system does not use the document is the best, but it is necessary to provide help and documentation. Any information should be easy to search, focus on the user's tasks, and list specific steps to proceed. The best way to help tips is:
- No prompts;
- disposable hints;
- Resident alert;
- Help documentation.
Application Scenarios: Product design, interactive design, user experience design
Funnel ModelIn short, the funnel model is the product's operation through the data feedback of each design step, then improve the product design through the specific analysis of each stage, and improve the user experience of the product.
Funnel Model Analysis ExampleScenario: Operational analysis, user experience optimization
SMARTThe Smart principle was first proposed by the management master Peter Drucker, this method not only helps employees to work more clearly and efficiently, but also allows the superior to better assess the staff, this principle is also applicable to their own goals.
- The goal must be specific (specific): the so-called specific clear is to use specific language to clearly explain the standards of conduct to be achieved. A clear goal is almost identical to the characteristics of all successful teams. One of the important reasons why many teams are unsuccessful is because the goal is ambiguous, or the target is not communicated to the relevant members effectively.
- The goal must be measurable (measureable): The goal is clear and there should be a clear set of data as the basis for measuring whether the goal is achieved.
- The goal must be attainable (attainable): The goal is to be able to be accepted by the executive, if the boss use some administrative means, using the power of the right to use the influence of wishful thinking to the subordinates, the typical reflection of subordinates is a psychological and behavioral resistance.
- Goals must be relevant to other goals (Relevement): The relevance of a goal is the association of achieving this goal with other goals. If this goal is achieved, but it is completely unrelated to the other goals, or the correlation is low, then the goal is not very significant even if it is achieved.
- The target must have a definite deadline (time-based): The time limit of the target characteristic means that the goal is limited by the period. There is no time limit to the goal of the assessment, or bring the assessment of injustice. Application scenario: Project management, Target management
SummaryOn the one hand, we should learn to use the experience summarized by predecessors, there are targeted, fast and effective problem solving, but on the other hand, but also with the development of the eye view of these existing methods, in practice, the existing knowledge to comb, integrate and expand, so as to summarize the new changes to adapt to the times of valuable experience.
Product Manager Analysis Model Daquan
