The price of effortless.

A saved preference removes work while carrying an old assumption forward. Simplicity depends on what happens when the assumption no longer fits.

A form remembers the address from your previous order. You press the button, pleased that the product has saved you some typing. Then you notice the parcel is going to the place you lived last year. The product removed an action while preserving an assumption. The action was visible. The assumption was easier to miss.

This is the difficulty with effortless design. Fewer steps can mean less needless work, or fewer chances to notice that the situation has changed. Both experiences can look equally simple in a prototype.

Remembering a preference is a useful service when the preference remains valid and the person can review it. The stakes change when the saved value determines a payment, a permission, or an obligation. The cost of a wrong assumption belongs beside the benefit of avoiding another choice.

Who makes the missing decision?

Consider the work being moved. When the product presents every option, the person has to understand and choose among them. When it hides the options, the team chooses on their behalf. The team then needs to judge what works for the likely situation, make important assumptions visible and support the cases that do not fit.

A quiet screen can conceal an elaborate responsibility. Defaults need reasons. Exceptions need a route. Changes need to be understandable to someone who relied on the earlier behavior. Removing a control does not remove the range of circumstances that control was intended to handle.

A useful way to judge a default is to examine what happens when it is wrong. Can the person notice before committing? Can they correct it without losing their work? If it takes effect, how difficult is the result to reverse? These questions reveal why carrying forward a display preference deserves different treatment from carrying forward a delivery address.

Visible without asking again

There is a choice between hiding a decision and asking the person to make it again. The destination can remain clearly visible beside the order, with a way to change it, without requiring another full form or a separate confirmation dialog. Information can preserve control without demanding a repeated decision.

The team still has to choose which assumptions deserve that visibility. Asking about everything makes a routine task exhausting and gives important questions more competition for attention. A useful interruption puts a consequential assumption in front of the person whose circumstances determine whether it is correct.

The remembered address captures both sides of the appeal. We like a product that saves us typing. We also want it to leave room for a life that has changed since the last order. The more a product remembers and decides on someone's behalf, the more its apparent ease depends on how it accommodates that change.