, , . We stopped reminding our users of those pleasant, successful moments that they experienced with our product. An example of an effective "reminder" is Facebook's features "On This Day," "Your most-liked post of last year," etc.
, . Our communication or the form of our actions has changed. In its turn, it has changed the product context for the users.
, . We have become a victim of direct or indirect discrediting/information campaigns of our competitors.
. In the recent product updates, we accidentally caused users strong emotional discomfort. Perhaps we even quickly resolved the problem but did not take sufficient measures to "smooth out" the incident.
, . We have lost contact with our users. Even though we continuously upgrade the product, we do not learn from users’ reaction. We are not fighting their hypotheses about drop-in product quality. Consequently, day after day, they continue to reassure themselves of their assessments of the "declining quality" of the product.
. Perhaps the frustration of users is related to product updates. It may be difficult for them to adapt to changes due to the habits of long-term use of the software with the old methods.
Depending on the intensity and duration of the disappointment, we can try to slow it down by conducting various polls ().
We can make updates more proportional in terms of evoked emotions ().
Also, we can try to create a positive emotional response in the part of the product where our users' interaction with it ends (Log out, Application closing, etc.) (). If for some reason, we can’t change the course and make any significant changes to the product, then it might be wise to provide users with .
#2.Why users aren't happy with product quality?
#10.Why do users complain about the quality of our support?
#21.Users don’t like how we talk to them — where did we mess up?
#34.How can we make the product look more modern without spending much?
#44.What to consider when working with user feedback?
#57.How can we add extra value to a product at minimal cost?