Look at the choices
a tool makes.

Remembering a choice

A preference can make a repeated task easier, but the tool needs to explain what is being remembered and where the choice applies. A setting on one device may behave differently from an account-wide setting.

This note considers sensible defaults, reversibility, and the difference between a convenience preference and permission to access information. It is useful when thinking about setup screens or settings pages.

Asking for attention

An update is not helpful merely because it arrives quickly. A person needs to understand why it matters and whether there is an action to take. Several messages about the same event can compete rather than clarify.

This note looks at status language, notification timing, and the difference between something being received and something being completed. These are distinct promises that an interface should not confuse.

Handling an interruption

A connection may disappear while someone is reading or editing. A tool needs to communicate which information is still available, whether a change has been saved, and what will happen when access returns.

This note explores visible states, duplicate actions, and the care needed when retrying. The goal is to make an interruption understandable rather than present a false sense of certainty.