What should we do when users ask for things we can’t deliver?
English
Armenian
Russian
What should we do when users ask for things we can’t deliver?
Copy linkCopied!
Share
Possible answers (8)
. Do not ignore requests.
, . We can explain as transparently as possible all the difficulties that we will face if we follow the users’ requests.
. We can modify user requirements and bring several similar options to a general vote. At the same time, each of the options must be feasible and consistent with our business goals. The voting itself can be held without specifying the absolute number of participants (only percentages). Then, we can appeal to the majority and implement those that won the voting. At the same time, we emphasize that we do everything following the wishes of users ().
, . We can show users how the changes they requested may modify the workflow of the familiar components of the product. The idea is to show users how much they underestimate the convenience of current practices.
. We can distract users from their requirements with a series of short-term bonus offers/rewards.
. If what the users suggest falls out of the product's context, we should frankly explain it in as much detail as possible. Of course, users are not required to understand the importance of product integrity and uniformity of context, but we should at least show our concerns.
. Users may want to see the difference in “before” and “after” views. Based on our goals we have to think if it is feasible for us to show the changes so explicit, or not.
. Sometimes it may be enough for us to show the time it will take to develop solutions requested by users. If we are talking about several months required for development, then we can explain that the requested features probably will not seem as useful by the time the update is launched.
Related questions
#44.
What to consider when working with user feedback?
#55.
Which product components are most sensitive to change?
#2.
Why users aren't happy with product quality?
#3.
Why users don't use requested features?
#22.
Why didn’t users like or appreciate the recent product update?
#57.
How can we add extra value to a product at minimal cost?
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.