Trust

Unexpected product changes

What is it?

Adding or removing functionality from a product without notice or justification can cause confusion and frustration for users. Sudden and unexplained changes to an application's organization, style, or content can reduce the trust they place in it and the team behind it. Users rely on consistency and familiarity when using a product. When features or functions they are accustomed to suddenly disappear or are altered without explanation, it can disrupt their workflow and hinder their ability to effectively use the application. By providing clear communication about any changes being made, users can better understand the reasoning behind them and adjust their expectations accordingly. Furthermore, unexpected changes can lead to a loss of trust in the development team. Users may wonder if the changes were made haphazardly or without proper consideration for their needs and preferences. This can negatively impact the perception and reputation of the product and the team responsible for it.

Examples

No expectation settings for file format

Unexpected search modification leads to confusion

Underlying principles

Endowment Effect

Endowment Effect

Endowment Effect

Habit Disruption

Habit Disruption

Habit Disruption

Status Quo Bias

Status Quo Bias

Status Quo Bias

Guiding questions

Do users need specific guidance to adjust to the change?

Do users need specific guidance to adjust to the change?

Do users need specific guidance to adjust to the change?

How early should you communicate the change to clients?

How early should you communicate the change to clients?

How early should you communicate the change to clients?