What should be considered when adding new product functionality?
English
Armenian
Russian
What should be considered when adding new product functionality?
Copy linkCopied!
Share
Possible answers (10)
, . If we are unsure whether the users will like the new functionality, we should put it in an implicit place. If we put the functionality in a visible place, and later it turns out that most users do not need it, it will be much more difficult to remove it without causing a negative reaction from the users.
. The functionality should harmoniously fit into the context of both the product and the specific page where we place it.
. The way we present the new functionality sets the tone for future updates. The more pompous we present the functionality, the higher we put the expectation bar ().
. We should investigate users' expectations from the added functionality, and during the presentation, put special emphasis on them.
. If by adding functionality, we change any of the established workflows, then it can cause a sharply negative reaction.
. We should explain all the advantages of the functionality as simply as possible, even if we think that everything is self-explanatory.
. We can significantly overestimate our ability to implement functionality within the agreed time frame.
. If we introduce functionality that can significantly change the product, but at the same time do not allow users to refuse (at least temporarily) these changes, we run the risk of running into a sharply negative reaction.
. We should minimize the threshold for using the functionality and the learning cycle time of it. All team members should consider the assumptions about the simplicity of the new functionality. Besides, it would be very useful to evaluate usability in advance by giving a group of users access to the functionality.
. If we are constantly looking for additional information about the launch of the functionality, we should determine how exactly this information will affect our decision. In other words, we should define the success criteria for our researches.
Related questions
#8.
Why are users so sensitive to product changes?
#5.
Why do users complain about product updates?
#37.
What are the risks of major changes to the product’s ideology or functionality?
#40.
How can we show content to users more effectively?
#42.
How can we generate new products "out of thin air" while keeping costs minimal?
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.