Since it is to collect user feedback, then this matter has to start from the user. For users, submitting feedback is definitely a "superfluous" workload. However, as long as we open the port for submitting feedback on the product (which is usually open), we can receive more or less feedback from users, some of which are praised to the sky, and some who press on the ground to rub against the ground. So what makes users "give up" the option of "direct churn" to give feedback? We look at it from both positive and negative aspects: [Active users]: This product is great, my main demands have been satisfied, it would be even better if I could change it or add some peripheral functions!
Generally, it is a medium and long-term business email list development reference. For example, what other scenarios are not covered? Has the previously collected requirements changed? and many more. For those dissatisfied users, resolving the most urgent issues as quickly as possible is key. At the same time, such users usually lower their expectations consciously or unintentionally, and some more lofty needs can be temporarily abandoned. Such users will generally help the team find some undiscovered serious problems and corresponding recurrence cases. Through such an analysis, it is not difficult to see that if we use a lot of resources to satisfy the "icing on the cake" functions of active users at this time, then the passive users on the other side will be cursing.
These are the different criteria for "good" for the two types of users. In addition, with regard to user feedback and needs, there is still a saying in the product circle: "Don't listen to users completely. For users' direct appeals, you need to dig deeper into the essence." This situation is partly due to the willingness to raise Feedback users will put forward some appeals related to their own interests, but such personal appeals may not be able to be extended to more users. And for those users who have other options, it may really be lost. We can classify these lost users as a third category of "silent users" (in parallel with the previous active and passive users). To collect the "feedback" of these users, it is necessary to analyze the user's behavior data. automatically;