Why don’t users use most of our product features?
English
Armenian
Russian
Possible answers (7)
, . We have emphasized a specific object (button, icon, other) too strongly in contrast with others.
. The problem is in rooted the behavioral patterns (habits) of our users. In such cases, we can play with elements positioning. For example, we can move elements from less popular features of the product to the most popular ones or vice versa. This should be done carefully since the slightest mistake can cause users tremendous anger (just imagine what would happen if Facebook simply swap places of “like” and “heart” reacts.)
, . Users are worried about the integrity of their data. They’re not sure that new functionality will not be a waste of time.
, . Users overestimate the value of the functionality they use because of the time they invested in it.
. Users feel that their current use of the product is the safest. This opinion could be without rational explanation.
, . Other components of our product are much worse than we think. It seems that they cannot be worse since one of the product components is very popular, but the data shows the opposite.
To encourage users to use other parts of the product, we can try , , , . In our communication where we promote other features of the product, we should consider the , .
Related questions
#2.
Why users aren't happy with product quality?
#3.
Why users don't use requested features?
#24.
How do we nudge users to take the actions we want with minimal cost?
#46.
How to simplify our product?
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.