Why are users so sensitive to product changes?

#8
modal close button

Why are users so sensitive to product changes?

Copy linkCopied!

Possible answers (10)

. We misinterpreted users' wishes and did not notice how we created something that was more convenient for us than for them.
. We accidentally removed the part of product functionality that users considered as "their own." It doesn't matter if they used this functionality or not.
. The problem is the complexity of new features. Perhaps they solve users’ problems but are overly difficult to use.
. Our updates fall on that period of our user's life cycle when he has a gloomy mood. As a consequence, the user makes judgments based on emotional impulses rather than logical judgment ().
. Our updates affect one specific group of our users disproportionately compared to the others. Perhaps due to the nature of our product, users think that recent updates are making them "visible by others" ().
, , . With each update, we add overall value to the product, but we do not count the negative emotional weight of our users' losses. In other words, we ignore the emotional discomfort that we cause to users.
. We didn’t bother explaining the importance of the updates, which caused offense. As a result, users interpreted our inaction in a very negative way ().
. Users are not following the update instructions we made. The reason is in their disagreement to follow the rules that we have agreed with them previously (this is especially relevant for B2B clients).
. Our updates have affected those workflows of the product where our users had established habits.
Such issues can be solved by creating the , and/or .

Related questions

#5.

Why do users complain about product updates?

#11.

Users blame us for their own mistakes

#22.

Why didn’t users like or appreciate the recent product update?

#43.

What to consider when planning product releases?

#63.

What to do if a significant mistake occurred in the latest release?

#54.

What should be considered when adding new product functionality?

How useful you found this?
Not useful
1
2
3
4
5
6
7
8
9
10
Not useful
Very useful
Thank you for your contribution!
previous bias
next bias
keepsimple logo
picLog In
My ProfileSettingsLog Out
Useful Links
UX COREGUIDEPERSONAUX CATBob - AI AssistantBob - AI Assistant
keepsimple logo
UX CoreGuidePersonaAwareness TestBob - AI AssistantBob - AI Assistant
Useful Links
Cognitive biases in education
UX CORE GUIDE
Add your question
UX CORE PERSONA
Introduction ArticleMedium.com publishing platform logo
APIUX Core API
picLog In
My ProfileSaved PersonasSettingsLog Out

UX CORE GUIDE

arrow downHow to use

UXCG is a free tool that helps teams detect cognitive bias-related UX problems across all product stages, whether you're prototyping, testing, or improving a live product

How to use UXCG

  1. Choose your product stage below;
  2. Find your question (either manually or through search);
  3. Read possible answers.

Each answer explains how cognitive biases relate to your specific situation. Since you understand your context best, you can apply the insights directly. While the tool doesn't provide ready solutions due to each case's uniqueness, it reveals new perspectives backed by cognitive science.

Label description
Questions related to in-house team members cooperation (product, development teams and others).
Questions related to product development stage (from concept to first public release).
Questions related to sales, marketing funnels, prospects and leads communication, and overall product packaging.
Questions related to user interaction with actual product and its features.
Questions related to product analytical data analysis.
search icon
Select your product stage
#10.

Why do users complain about the quality of our support?

#30.

What common mistakes do we make when dealing with product analytics?

#41.

What should we do if our colleagues’ stubbornness is hurting teamwork?

#43.

What to consider when planning product releases?

#45.

What to do if our team members do not share their opinion?

#50.

How to deal with an incompetent colleague/manager?

#59.

What should we consider when referencing political, social, or economic events in our messages?

#61.

What should we do if our team wastes too much time on minor details?

Be Kind. Do Good.