What should we consider when removing unnecessary product features?
English
Armenian
Russian
What should we consider when removing unnecessary product features?
Copy linkCopied!
Share
Possible answers (12)
. We need to understand how users relate to the removed functionality. At the same time, our personal opinion does not matter. We should double-check with the team any assumptions about how users will interpret the removal of functionality. We need the same knowledge for proper communication about the changes ().
. We should be cautious when removing the elements that are part of some workflow in the system.
. We should expect disappointment disproportionate to the degree of use of the removed functionality. Because of this, it is advisable to add something along with the removal of the functionality to "soften" the discomfort.
. Even if the user has used a certain product element once every six months, we should understand that this element is his property (for him). Removing such an element without explanation or referring to "usage statistics" can be perceived sharply negatively. Users may call our actions "dishonest" and "unfair" because we took them without their participation (, ).
. In explaining our decision, we may appeal to the desire to eliminate a specific risk.
. If we anticipate a sharply negative reaction to removing a certain functionality, we can take action to mitigate this reaction. So, a few months before the action, we can highlight the imperfection of the component that we are going to remove. The idea is that on the day of removal of the functionality, users can refer to some "constantly appearing" materials associated with the component that has been removed. Thus, it will be easier for them to rationalize what has happened.
. In some cases, we can first move a component to another part of the product, so that it falls out of context. Then, analyze users' reactions, and only after that remove the component as "obviously interfering."
. We need to be very careful when working with product components in which people "see themselves." For example, it may seem to us that the "Premium" prefix next to the users' nicknames is unnecessary and does not carry any semantic meaning. However, due to the effect of self-reference, if we remove this prefix, users can begin to leave without telling anything. Any element of the product that feeds the user's ego is critical.
. If our users are conservative due to their ideology, age, or something else, we should keep the number of changes to a minimum.
. Sometimes users find it difficult to assess the impact of changes. Especially if these changes affect several different components of the product. It might be a good idea to visualize the changes in one image in a "Before - After" format.
. If we remove a component that has been actively used in our marketing or post-purchase materials, users may have the feeling that they were "cheated."
. In some cases, users may dislike the changes without even understanding their meaning. This is especially true in the B2B sector, where it can often be convenient for the user to hide his incompetence in front of his management, referring to “extreme changes” in the product.
Related questions
#46.
How to simplify our product?
#55.
Which product components are most sensitive to change?
#8.
Why are users so sensitive to product changes?
#17.
Why don’t users use most of our product features?
#32.
How can we maximize the comfort of the product?
#54.
What should be considered when adding new product functionality?
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.