Since most users never re-sort, whatever order a view opens with decides what nearly everyone concludes

What it is

Users rarely re-sort: whatever order the view opens with is the only order most people ever see. The default sort is therefore not a technical detail but an editorial decision — it decides whom readers see first, what reads as "number one," which structures surface, and which stay buried. The cost of a wrong default is amplified by the fact that almost nobody changes it.

Why it happens

The default's power compounds behavioural and perceptual facts: behaviourally, changing the sort takes a deliberate interaction, most viewing is passive, and the default state is the final state; perceptually, first-screen position and arrangement fix the first impression — a value-descending default makes head-concentration visible instantly, while an alphabetical default buries the same concentration inside the alphabet. Data teams already know the structure (they know who the top few are), so sorting feels inconsequential to them; readers do not, and the default order is their entire evidence. This is also the doorway to misleading: a carefully chosen default can make a mediocre distribution look dominant or limp — the default sort is part of the narrative and must be chosen as consciously as the title.

Where it stops holding

The legitimate basis for a default is the view's primary task: comparison takes value-descending, lookup takes name or category order, time-series work takes chronological. With no single dominant task, default to the most common one and keep the switch prominent. The editorial power also carries responsibility: value sorting spotlights extremes and dims the middle; when that crosses from emphasis into unfair presentation — say, deliberately folding the long tail out of sight — it crosses into selective-presentation ethics. The choice process should be traceable — why this default belongs in the design document.

Applying it

• Choose the default sort explicitly for every delivered view and record it in the design notes ("sorted by GMV descending, serving the comparison task"); accidental implementation defaults are banned.
• Run a cold-eye test before release: does a fresh reader's first-glance summary match the view's task? If not, check the default sort first.
• Verification: audit live views for match between default sort and documented task; a missing note or a mismatch is a remediation item.

Related

• Same group: U6.08.1 Sorting is the cheapest device for discovering structure · U6.08.3 The sorting basis must stay visible
• Nearby: U5.04.1 Category-axis order is a designer's choice, not a property of the data · U10.02.1 The chosen time window decides the trend's direction
• Search terms: default sorting · first impression bias · editorial choices in visualization