Default Label Review¶
Configuration review — instantiates Marked Default Audit
Finds the unlabeled or 'standard' default buried in settings, options, and interface states, makes that baseline an explicitly named choice, and tells users the default now has a name.
Default Label Review targets the marked/default relation where it lives in configurable systems — settings, toggles, document templates, the initial state a user lands in before touching anything. In these systems the baseline isn't just described neutrally; it is preselected, and it is often either unlabeled or labeled with an empty word like "Standard," "Normal," or "Default." The review's distinctive move is to name that preselected baseline as one explicit option among peers and then carry the fix all the way through — relabeling it and communicating the change to existing users. Unlike an audit that only reads words and stops, this mechanism intervenes in interactive defaults and closes the loop; unlike a status-inference audit, it does not spell out what the default implies — it makes the default choosable.
Example¶
When a meeting opens in a video-conferencing app, participants land in a layout the interface never names — it is just "what you see." The menu, meanwhile, offers "Speaker View," "Gallery View," and "Immersive View" as explicitly named alternatives. A Default Label Review discovers that the unnamed initial state is Gallery, silently preselected, and that naming every alternative while leaving the default nameless makes the default feel like reality rather than a choice users could revisit. The review renames it "Gallery View (default)" so all layouts sit in one vocabulary as peers, holds the actual preselection unchanged, and adds a one-time tooltip: "We gave your default view a name — you can switch it anytime in Settings." What was previously invisible is now findable, comparable, and changeable.
How it works¶
- Enumerate the configurable surface. Settings, toggles, templates, and the states shown when the user does nothing.
- Find the do-nothing outcome. For each, identify what is preselected or displayed by default.
- Test its visibility. Is that default named as a peer of its alternatives, or hidden as "just how it is"?
- Relabel it as an explicit choice in the same vocabulary its alternatives use — without necessarily changing which option is selected.
- Communicate the change so users who relied on the old, unnamed behavior aren't disoriented by a suddenly-named default.
Tuning parameters¶
- Default-explicitness level — from a quiet parenthetical "(default)" to a full first-run chooser. More explicitness weakens the default's silent pull but adds setup friction.
- Change vs. preserve — whether to keep the same option selected or re-pick it. Naming a default need not, and usually should not, change it.
- Notification intensity — silent relabel, passive banner, or forced acknowledgement. Trades user awareness against annoyance.
- Scope — fix one conspicuous setting or sweep every default in the product for a consistent vocabulary.
When it helps, and when it misleads¶
Its strength is that it attacks the strongest form of hidden norm — the default effect, where people disproportionately keep whatever is preselected[1], so an unnamed default is doubly powerful. Its failure mode is that naming a default clumsily can itself imply the alternatives are deviations, and, more dangerously, "just relabeling" is an easy cover for quietly changing a default and disrupting users who depended on the old behavior. The classic misuse is a dark pattern: relabeling as pretext for flipping the default toward what the vendor prefers. The guarding discipline is to hold the naming decision and the change decision strictly apart — when you name a default, keep its behavior constant unless a separate, justified decision changes it, and communicate both moves openly.
How it implements the components¶
unmarked_default— its entire target: the preselected, unnamed baseline in a configurable system.label_or_category_revision— renames that default as an explicit, peer-level option in the shared vocabulary.transition_communication— notifies existing users so a newly-named default does not disorient them.
It does not infer the hidden_norm or spell out the status_implication behind the default (that's Naming Markedness Audit), and it does not test how affected users read the change through stakeholder_review (that's Stakeholder Interpretation Review); this review acts on interactive defaults and closes the loop to relabel and notify.
Related¶
- Instantiates: Marked Default Audit — supplies the repair for the specific case of preselected, unlabeled defaults.
- Consumes: Naming Markedness Audit flags which unlabeled defaults hide a norm; this review acts on the ones worth naming.
- Sibling mechanisms: Naming Markedness Audit · Inclusive Language Markedness Review · Classification Markedness Audit · Symmetry Labeling Matrix · Style Guide Revision · Search and Documentation Scan · Stakeholder Interpretation Review
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Default Label Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it finds the unlabeled or 'standard' default buried in settings, options, and interface states, makes that baseline an explicitly named choice, and tells users the default now has a name.
Independent corroboration: The frozen evidence defines Default Label Review as 'Finds the unlabeled or 'standard' default buried in settings, options, and interface states, makes that baseline an explicitly named choice, and tells users the default now has a name', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Interaction design cohered review and repair of configurable default states so the preselected baseline is visible, named, and revisitable as an option among peers.
Related originating lineages:
- Behavioral Economics — Default-effect research supplied the diagnosis that an unnamed preselection exerts recommendation and inertia effects.
- Linguistics & Semiotics — Markedness and labeling analysis supplied attention to how 'normal' or 'standard' naturalizes one baseline.
Review resolution: Interaction design cohered review and repair of configurable default states so the preselected baseline is visible, named, and revisitable as an option among peers.
Attribution caveat: The intervention is interface-focused, synthesizing behavioral defaults with linguistic markedness.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
References¶
[1] Johnson, E. J., and Goldstein, D. "Do Defaults Save Lives?". Science 302(5649), 1338–1339 (2003). Shows that changing the preselected no-action default sharply changes organ-donor consent choices. registry ↩