The user does not know the existence

tamim2369@gmail

Functional impact Generally, the health of a function is measured through the number of active users and key task completion indicators after launch. When the data performance is not ideal, you need to first investigate why users are not using it, and then investigate whether the function is necessary. All lack of motivation for use can be divided into three types: Don't know:


The user does not know the existence of this function (enhanced function guidance); No: I understand FR Numbers the pros and cons of the function but do not use it due to the complexity of the operation (to improve the user experience); Unwillingness: Know the pros and cons and operations of functions, lack of triggering usage scenarios (exploring motivation scenarios). Consider whether there is room for iterative rescue from the above three aspects.







If the growth of users of this function has reached a bottleneck and is in a state of being unable to make ends meet, it is necessary to conduct a survey on the users of the function. Instead of simply asking whether the function is needed, Asking how satisfied you are with the product without this feature (doesn’t affect it or will result in a points deduction), this can better identify the user’s true dependence on the product, and avoid the situation where the user says the feature is useful but doesn’t actually use it at all. After all, it seems like  Powerful can better satisfy your desires.