Why didn’t our product meet user expectations?
English
Armenian
Russian
Possible answers (6)
, , . In our public communication and marketing materials, we have exaggerated the product's capabilities. After actually using the product, the user felt dissonance ().
, . The problem is our inability to put ourselves in the shoes of users. We attracted users to try our product by pointing out a real problem, but our solutions did not match their preferences.
. Users decided to use our product because "it’s good as it’s new." 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.
. Perhaps, with such complaints, users mask the fact that it is difficult for them to work with the product (low qualification/age/habit of working with paper documents/outdated approaches).
. Users did not like a particular element of the product compared to the rest ().
. Users refer to some of our statements that we have never made. This is especially common for B2B customers. Because of this bias, it is useless to convince them otherwise in most cases. To alleviate the negativity, we can try using , .
Related questions
#49.
What should we do when users ask for things we can’t deliver?
#3.
Why users don't use requested features?
#19.
Why do potential users mainly notice the flaws in our product?
#44.
What to consider when working with user feedback?
#48.
What to consider when involving users in product development
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.