The current sort must be visible

What it is

Which ordering the list is using must be readable from the control itself. The current sort must be visible means that with the dropdown closed, without guessing from what row one looks like, “Relevance,” “Newest,” or “Price low to high” is showing as on. The control is a display of state, not only an entrance to change state. When the current value is invisible, order still applies, and people treat the default as “natural order,” or treat a personalized ranking as general relevance.

What must be visible is the option state on the control, not an essay on the algorithm. Whether the criterion can be explained is a neighboring problem; here the only demand is that the option in force is not hidden by the widget.

Why it happens

Sort controls spend most of their life collapsed. Collapsed to an icon with no current value, state vanishes from the interface and lives only in the implementation. People predict what further down will look like from “the label I can see”; missing the label, prediction binds to common sense (newest first, relevance), and when common sense disagrees with the real default the whole page is misread. Mail that is assumed newest-on-top while “Important” has lifted a three-day-old thread cannot expose that misread without visible state.

Visibility also decides whether people will change it. Changing presupposes knowing “this is not the kind I want.” Invisible state makes even “should I open the dropdown” undecidable, so most sessions stay on the default—and the default’s power is amplified by invisibility. A placeholder “Sort” is not a current value; the current value must be one of the option names.

Studying it

With the control collapsed, test whether people can name the sort in force; do not only test whether the dropdown opens.

• Paradigms: after a search, without opening the sort menu, ask “what is this sorted by”; contrast a control that labels the current value with one that is icon-only. Hearst treats sort as persistent search chrome. In query logs, opening the sort menu and making no change is a weak signal of “I came to see what it is now.”
• Independent variables: whether the collapsed state writes the current option, whether the default is visually indistinguishable from other options, whether personalized ranking has a separate mark.
• Dependent variables: accuracy of paraphrasing from the collapsed state, times the menu is opened only because state was unclear, rate of mistaking the default for another common ordering.
• Methodological note: if the lab task says “change to time,” people open the menu and the collapsed state is never tested. Ask for the state before allowing the open. If timestamps and relevance happen to share an order, a correct paraphrase may be a guess; use materials where the two sorts clearly diverge.

Where it stops holding

With a single sort that matches common sense (logs always newest on top), the control can recede, but the moment a second kind appears, the collapsed state must write the current value. Table-header sorting uses a triangle for direction; the current column must be highlighted—a triangle bound to no column indicates nothing. When a narrow screen tucks sort into “More,” a short label of the current value must remain outside; an ellipsis alone is not enough. When personalized or A/B defaults differ per person, visibility matters more: a neighbor’s “current” may differ, and word of mouth will not carry it.

Applying it

• In the collapsed state, the sort control shows the name of the current option, not a generic label “Sort.”
• Style the default and a user-changed value with the same visible pattern; do not let the default go blank as if “not sorted.”
• Spell personalized or “smart” ranking on the control so it does not look like ordinary relevance.
• Verify after a search, without touching sort, by asking someone beside you what it is sorted by. If the word cannot be read off the control, state is invisible. Change the default from relevance to time; if the control still says “Sort” or still looks like relevance, visibility has not followed the real state.

Related

• Within the group: G3.09.2 Sort and filter are independent operations and must not reset each other · G3.09.3 The default sort determines what most users will ever see
• Adjacent: G3.05 Result ranking · G1.05 Metadata · G2.08 Predictability of navigation items
• Search terms: sort control · current sort · ranking