English
Armenian
Russian
Why didn’t our product meet user expectations?
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!
UX CORE GUIDE
UXCG is a free tool that allows you to look at the most popular issues in product and project management from the perspective of cognitive science and behavioral economics.
Select your project stage
Team Assembly
Development
Marketing/BD
Released
Monitoring
Relevant questions for your project's Team Assembly stage
Product stage
Be Kind. Do Good.