Content priority shifts with situation, so a static visual hierarchy can go stale

What it is

An mail home, empty: what should be seen first is how to connect an account. Thirty unread: the unread list. Account about to be cut off: a failed renewal. The same template still makes the top promo bar heaviest. Empty, full, incident — the promo is first every time, and whatever should have been first takes turns as supporting act. Content rank follows the state of the world; template rank follows the slot. The slots were right the year they were ranked. A state change ages them. This is not two audiences. It is one person needing a different first slot at different moments.

Why it happens

A static hierarchy writes weight onto slots: promo at the top is always heaviest, the list always medium. World state changes how important the proposition in a slot is, not the slot’s weight. “Renewal failed” can outrank everything semantically and still lose to an empty promo if it lives in a medium slot. People do not first rank the world’s importance and then look; they still encode by slot weight. Staleness is therefore structural: not copy going old, but weight bound to position instead of to state. To track state, the rule has to read “if incident, incident slot becomes first and promo drops,” not hope the user re-ranks.

Studying it

Take three states of one template: empty, normal, incident (or logged-out / logged-in / permission expiring). Write content item one for each, then measure first fixation or five-second first place. The independent variable is state; the dependent is whether visual first place stays nailed to the same slot. Nailed slot plus moving content item one convicts the static hierarchy of staleness. A treatment that re-ranks on state shows whether alignment returns in the target state, and whether false incidents (weighting normal as incident) create a new mismatch.

Where it stops holding

Some products barely have state (a leaflet, a static settings table); dynamic staleness has no object. If state changes every few seconds (a ticker), weight cannot follow every tick or the first slot will flash; set a minimum dwell, or show the number inside a slot that is already first rather than changing the slot’s grade. User-initiated modes (edit / preview) are state started by an action; re-ranking can follow the action without listening to the outside world. When notification permission is off, “incident” may not get a system banner, and in-UI re-ranking matters more.

Applying it

• For a critical template, list states: empty, normal, blocked, danger. One visual first slot per state, and write which slot rises and which must yield.
• Promo and campaign slots are preemptible by default, not undegradable. When incident or blocked rises, the campaign loses contrast or leaves.
• Re-rank whole slots. Do not tuck a red line into the old promo bar — that stuffs a second meaning into an already stale first slot, and both will be misread.
• Check: three screenshots of the same URL, empty / full / incident, five-second writing on each. If all three name the same campaign module first, and the incident shot’s content item one is a shutdown, the template is stale. Re-weight from the state table and shoot three again until each spoken first equals that state’s content first. Do not test only the normal comp.

Related

• Same group: F3.07.5 When audiences rank content differently, one visual hierarchy cannot serve them all · F3.07.1 Visual hierarchy must match content priority
• Nearby: E6.04 Global status messages · F3.11.4 A globally emphasised UI makes users immune to all emphasis
• Search terms: empty state · incident mode · visual hierarchy · priority shift