Use adaptive defaults when the product proposes starting values from context or prior behavior; settings management when users inspect and change durable configuration; preference center when users manage communication, consent, privacy, and personalization choices; and recommendations when the system ranks optional items or actions.
Use adaptive defaults when the product proposes starting values from context or prior behavior; settings management when users inspect and change durable configuration; preference center when users manage communication, consent, privacy, and personalization choices; and recommendations when the system ranks optional items or actions.
Practice the judgment: Imagine this situation: An adaptive default keeps returning after a user corrects it because the system records the correction as noise instead of feedback. Write the person's goal, choose one of these patterns, and show the state that helps the person continue. Use the decision rules and source trail below to explain your choice.
Review the underlying principle →| Dimension | Adaptive defaults | Settings management | Preference center | Recommendations |
|---|---|---|---|---|
| UI or UX | UI + UX - Context-aware starting values for fields, filters, scopes, layouts, schedules, channels, or workflow options | UI + UX - Dedicated user or app configuration management surface | UI + UX - Persistent hub for communication, consent, topic, privacy, language, and personalization choices | UI + UX - Ranked suggestions generated from context, behavior, item similarity, popularity, editorial rules, or recommendation models |
| UI guidance | Render adaptive defaults as visible starting values with source labels, confidence or rule basis, scope, freshness, and a nearby way to change, reset, or stop using the signal. | Render settings management as a durable configuration surface with a clear Settings or Preferences entry point, grouped categories, current values, setting descriptions, ownership or scope labels, dependencies, save or immediate-apply behavior, status feedback, search or section navigation for larger sets, and reset or restore defaults where appropriate. | Render a preference center as a returnable hub with categories for communications, channels, topics or interests, notification delivery, privacy and data sharing, cookie or tracking consent, personalization, language or locale, required messages, managed values, source-of-truth status, and save feedback. | Render recommendations as a labelled set of suggested items with clear item identity, recommendation reason, source or basis, availability, and a visible way to dismiss or tune at least the current item. |
| UX guidance | Use adaptive defaults when the product can reduce repetitive setup by proposing values from current context, recent use, prior correction, locale, role, organization policy, device, or task history. | Use settings management when users need to review and change persistent app, account, workspace, notification, privacy, display, integration, or system behavior outside the immediate task flow. | Make the effective result clear before and after save: what changes now, what stays required, which rows are policy-managed, which external system owns the value, and where users can withdraw consent or unsubscribe. | Use recommendations to reduce discovery effort when the system has evidence that a small set of items, products, services, content, or next actions may be useful in the user's current context. |
| Good UI | A case export form defaults to Current queue and CSV because the user exported the same queue yesterday, labels the basis, and lets them switch scope before export. | A notification settings page groups channels, quiet hours, digest frequency, and workspace scope; each row shows current value, effect, dependency, and whether changes save immediately. | A customer account preference center shows Email, SMS, Push, Topics, Cookies, Data sharing, Language, and Required service messages, each with current status, scope, and last saved time. | A commerce product page shows Pairs well with this camera, hides out-of-stock accessories, limits the rail to three visible items, and marks manually selected merchant recommendations separately from generated recommendations. |
| Bad UI | A payment form preselects the highest donation amount because it predicts generosity and hides the source. | Users change the wrong scope because local, account, workspace, and organization settings look identical. | A single Receive updates switch hides whether it controls marketing email, SMS, push, product notices, analytics consent, or service messages. | A recommendation list keeps showing unavailable, out-of-stock, permission-restricted, or already dismissed items because the UI only validates card shape. |
| Good UX | A user opens a recurring report, sees Project: Acme and Range: Last month already filled from the previous run, changes the range to Quarter, and the system asks whether to remember that correction. | A user turns off weekly digest emails, sees the setting save immediately, keeps urgent security emails enabled, and understands the workspace-level override. | A user turns off promotional email, keeps outage SMS and account security email, changes language to Spanish, withdraws ad personalization, and sees which transactional messages remain required. | A signed-out shopper sees Popular in backpacks rather than fake personalized copy, then gets personalized reasons only after activity exists and consent settings allow it. |
| Bad UX | A manager changes an adapted value once and accidentally changes the saved default for the whole organization. | A user changes a privacy setting thinking it affects only one project, but the value applies to the whole account. | A user opts out of marketing email but continues receiving promotional SMS because the channel matrix was hidden. | Users assume recommendations are mandatory next steps because the UI mixes them with required workflow tasks. |
| Best fit | Users repeatedly choose similar values and the product can explain a likely starting value from current context or prior behavior. | Users need to inspect and change persistent app, account, workspace, privacy, notification, display, integration, device, or system behavior. | Users need to revisit and change communication, consent, topic, personalization, privacy, channel, language, or data-sharing choices. | Users need discovery help in a large item, product, content, service, or action space. |
| Avoid when | The user needs a durable settings page, preference center, recommendation list, or explicit confirmation instead. | The task is a one-time transaction, submission, setup wizard, or onboarding flow. | The product only needs a small app setting unrelated to communications, consent, or personalization. | The product has too few items for ranking to reduce effort. |
| Required state | Adaptive default state with proposed value, source, scope, and reason | Settings overview with categories and current values | Overview with preference categories and current effective status | Default recommended state with labelled section, item identity, reason, source, and action controls. |
| Accessibility burden | Associate source and consequence text with the affected input, select, filter, or action control. | Use headings, section labels, fieldsets, and persistent labels so settings groups and controls have clear programmatic names. | Group categories with headings, fieldsets, legends, and persistent labels that name the affected channel, purpose, topic, source, and scope. | Make recommendation reasons, sponsored labels, availability, and item type available as text. |
| Common misuse | Preselecting values to increase conversion, spend, sharing, or consent rather than to reduce honest user effort. | Using settings as a dumping ground for unrelated navigation, billing, help, profile setup, onboarding, or destructive account actions. | Using one master preference switch for communication, privacy, cookies, topics, and required messages. | Pretending generated suggestions are recently viewed, saved, or required steps. |