. Any change that will limit the users’ capabilities is a highly sensitive one.
. Any component that users considered "their own" is a highly sensitive change. It does not matter whether the user used the functionality or not ().
. Any product component that was customized or built by the user, is highly sensitive to change.
. Any component that is fresh in the user's memory becomes sensitive to changes.
. Any component that is used by the majority of users is sensitive to change.
. Any product has a basic set of features that provide the "context" of the entire product. Such components are highly sensitive to changes.
. Any change affecting the moral, ethical, or ideological values of our audience is critically sensitive.
. The components we have used to help the user rationalize their purchases/decisions are particularly sensitive to change.
. Any change in a common workflow in a product is highly sensitive.
. Any change that brings uncertainty into the future of a component/product may cause a sharp reaction from users.
. This may sound obvious, but the most sensitive components are always those that the user considers most important. Often, especially in the B2B model, the user's incompetence can lead to the fact that we will not be able to make changes to those system components that are redundant or incomplete.
#37.What are the risks of major changes to the product’s ideology or functionality?
#53.What should we consider when removing unnecessary product features?
#54.What should be considered when adding new product functionality?
#63.What to do if a significant mistake occurred in the latest release?
#5.Why do users complain about product updates?
#8.Why are users so sensitive to product changes?