Many people begin using a tool without visiting every setting. The initial choices therefore shape the ordinary experience, including how information is shared and which features become active.
A thoughtful default should fit a clear purpose and make its boundary visible. Explain who can see an item, what is stored, or whether an action will affect other people. A familiar icon alone may not convey that information.
Make changes accessible from the task itself when possible. Someone adjusting a sharing decision should be able to confirm the result without searching through unrelated menus. The value of a default includes the clarity of the path away from it.
- State the initial audience or scope.
- Explain the consequence near the choice.
- Make the result of a change visible.
Bring the idea into a day.
Imagine an application starting with local storage only. The default becomes easier to evaluate when its limitation across devices is stated plainly.
Another angle on the story.
Consider a change in circumstances: another reader, a borrowed device, or an old account. A setting that suited yesterday may deserve a new decision.
Follow a related question
Ask which situations the examples cover.
Examples shape the model’s taskCheck the image’s actual display size.
One picture, several useful sizesKeep learning
Related background to continue exploring this subject.
MDN: privacy on the web W3C: accessibility, usability, and inclusion
