Users need to be able to switch units

What it is

User-selectable units let a person override units inferred from region and usage while leaving the underlying physical quantity unchanged. Unit preference must not be tied to interface language, and it need not be one global metric/imperial choice. Migration, professional training, instrument origin, and collaborators can give one person different preferences for temperature, height, distance, and mass. The switch changes presentation and input interpretation, not the physical quantity represented by the data.

Why it happens

An automatic default can only estimate a common convention from locale, region, and usage; it cannot know an individual's learned practice. Unicode locale mechanisms such as the mu, ms, and rg keys likewise treat the measurement unit, measurement system, and regional override as separable signals. A robust system keeps canonical quantities and user preferences, resolving the effective unit at presentation time. After a switch, every value is reformatted from the canonical quantity rather than reverse-converted from a rounded screen value. The input parser must change with the displayed unit too, or a new label can conceal an old interpretation of submitted numbers.

Studying it

Contextual interviews with migrants, international teams, and people who use professional unit conventions can reveal where a regional default fails the individual's task. Start usability sessions with both saved data and unsubmitted input, then ask participants to switch units and continue comparing, editing, filtering, and exporting. Observe whether they think the stored quantity changed, understand the scope, and find the preference preserved on return. When comparing a global setting, an inline switch, and a temporary dual-unit view, measure discovery, post-switch comprehension, submission errors, and cross-device consistency—not clicks alone.

Where it stops holding

Preference cannot override physical dimension, device capability, or mandatory professional expression. Consequential contexts such as drug concentration, aviation altitude, or mechanical tolerance may require a fixed unit, dual display, or explicit confirmation. Statutory submissions and interchange formats may prescribe a unit. In shared records, “the unit I see” must remain separate from the stored quantity so one person's preference does not rewrite another person's view. If unsubmitted text cannot be reinterpreted unambiguously from the old unit, switching should pause for confirmation rather than guess.

Applying it

• Start from a sound default resolved by category, usage, region, and magnitude, then expose a visible override. Allow separate preferences for temperature, distance, person height, or mass where tasks demand them.
• State whether a switch affects one field, the current view, or the account. Synchronize account preferences across sessions and devices, while keeping temporary overrides from silently changing the long-term setting.
• Regenerate lists, charts, threshold labels, supporting copy, and export previews from canonical quantities. When an input unit changes, update suffixes, hints, step size, range, and parsing together.
• For unsubmitted values, parse into a unit-bearing quantity before changing presentation. Show old and new values for ambiguous or consequential cases. Test refresh, back navigation, offline sync, and collaborative accounts for stable preference without shared-data contamination.

Related

• Same group: S2.04.1 Length, weight, and temperature use different measurement conventions · S2.04.2 Conversion rounding can create inconsistencies · S2.04.4 A missing unit is a safety hazard, not a typography issue
• Adjacent: S4.01.1 Automatic detection must be overridable · S4.02.1 Language, region, and time zone are independent settings
• Search terms: user-selectable units · measurement unit override · unit preference