Product use occasions: When, where, and how do the target user groups use our products?

The geographical location of the target user group: Is it rural? City (first-tier city or second-tier city)?

The lifestyle of the target user group: determine their value orientation and attitude.

Product usage behavior among the target user group: How often do you use the product? What is their decision-making process? What are their consumption channels? What are the expenses incurred when purchasing?

Demographic characteristics of the target user group: gender, age, education level, income.

Estimate of the product’s potential to generate profits from its target user base: What is the cost of generating profits? What is the cost of providing the service?

Reverse judgment method: If a need cannot be met, causing the user to no longer continue to use or consume, it is a pain point.

Payment strategy method: The needs that users are willing to pay for are the pain points.

Change judgment method: Changes in user usage scenarios may cause non-pain point requirements to transform into pain point requirements.

Maslow's need judgment method: The lower the need, the more likely it is a pain point need.

Insight into human nature: Use human nature to determine the most real needs of users. Before implementing a function, check whether the function is consistent with human nature and matches the specific expression of human nature. If it matches, it is worth doing. The main manifestations of human nature include: the pursuit of happiness, the pursuit of high value, the love of beauty, laziness, the pursuit of novelty, the pursuit of fun, escaping from fear, establishing a sense of existence, etc.

Maslow's Hierarchy of Needs: The higher the needs at the upper level are satisfied, the higher the value the product can demonstrate, and the more users are willing to pay a higher price for it. Determine whether it should be done by looking at which level of Maslow's hierarchy the required function is. Functions corresponding to the needs of the bottom layer should be implemented, and at the same time, some functions corresponding to the needs of the middle or high-level layers should be selected.

Observation method: Since the needs expressed by users are not reliable, we can observe users and observe their words, deeds, and behaviors. Infer the inner world of users and determine what they really want.

KANO model method: Classify needs into basic needs, expected needs and exciting needs. Functions with basic requirements must be implemented; functions with expected requirements can be selectively implemented to improve product quality; functions with exciting requirements should be implemented in 1 or 2 to achieve the effect of making users scream.

Product positioning method: Evaluate whether the demand is to be done based on product positioning, and evaluate whether the demand meets the product positioning. Functions that are far away from product positioning do not need to be implemented.

Usage scenario method: Evaluate whether the requirements should be met based on the user's usage scenarios. List the main usage scenarios and secondary usage scenarios of the target user group, and based on the listed usage scenarios, determine whether to meet different needs in different scenarios.