Why users don't use requested features?
English
Armenian
Russian
Possible answers (13)
. Users are worried about losing the data that they worked on using previous functionality. They do not feel confident that new functionality will not be a waste of time.
. Users wanted functionality by appealing to the fact that competitors have it or to the "novelty" of the technology. Desire was driven by an emotional impulse, not a rational assessment of utility. In fact, the functionality turned out to be way less useful than they thought.
. When it became possible to assess the requested features, users realized that the previous system/functionality was better.
. We could not put ourselves in the user's shoes and misinterpreted their wishes. The error can also be related to the .
. We did not notice how we created something that was more convenient for us than for our users.
. It is difficult for users to adapt to changes due to the habits they formed when working with previous functionality.
. We overestimated the ability of our users to use the requested features. The functionality turned out to be too complicated for them.
. Users did not consider the scale of the requested changes. This led to the desire to return to the old methods of work.
. The new functionality implies that users will stop using the old system and switch to the new one. Users didn’t take into account their emotions towards the old functionality in which they put a lot of time and energy.
. We added functionality without considering Miller's Law. The number of objects required for memorization made it challenging to master the new features.
. Users, whose opinion was accepted as the basis for the feature’s development, turned out to be incompetent in the issue under discussion.
. If users voted for a feature publicly, their responses might reflect a desire to appear preferable in the eyes of others. In fact, instead of carefully analyzing proposed options, they stuck to a line of conduct that correlated with their public image.
Users might simply not notice the new functionality. Perhaps we poorly presented new features (). If the design allows, we can emphasize the features using the .
Related questions
#48.
What to consider when involving users in product development
#53.
What should we consider when removing unnecessary product features?
#6.
Why didn’t our product meet user expectations?
#7.
Why don’t users like the product anymore?
#17.
Why don’t users use most of our product features?
#39.
How can we make our product users more responsible?
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!
Useful Links
Useful Links
UX CORE GUIDE
(UXCG - Finding solutions for your problems)
How to useUXCG 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
- Choose your product stage below;
- Find your question (either manually or through search);
- 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.
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.