System status needs a stable home on the interface
Aliases: status home · persistent status placement · where to look
What it is
“What is the system doing” has to live in a place you can find again. Sync always beside the title, connectivity always in the chrome, whether the draft is saved always in the same aside — that is a stable status locus. Nielsen’s heuristic visibility of system status is often taken as “put up a cue”. If the same fact is a toast this time, in-button copy the next, then a wandering speck, the pixels appeared and the looking habit did not.
The claim is about where to look, not how change is animated and not whether a notice fired. A fact that relocates is, for search, not expressed.
Why it happens
Closing the gulf of evaluation starts with knowing which patch of the interface to sample. A stable home lets the eyes form a shortcut — top-right chrome, trailing end of a row, beside the editor title — cost approaching one saccade. A drifting home forces a search on every check; a failed search is coded as “unknown”. Unknown is not neutral: people continue with the last value they did see, which is an expired model treated as current.
A second layer is channel competition. Transient cues (toasts, banners) steal attention but have no address; when they vanish the locus is empty. Parking global status only in a transient channel writes “now” as “a sentence that flashed”. Global status needs an anchor that remains during the task. Transients may overlay the anchor; they cannot replace it.
Studying it
When scoring the “visibility of system status” heuristic, split “it appeared” from “it can be found again”. Logging “the word sync was on screen once” overestimates. Interrupt the evaluator mid-task, wait a dozen seconds, and ask “how far has sync got”; watch where the eyes go first and whether the answer is right. Level-1 situation awareness — can you report the critical elements — maps onto an interface as: no hint, no menu-diving, spoken report of connection, save, and permission.
Independent variables: whether the status control keeps its place across screens, whether it lives only in a transient channel, delay between interrupt and query. Dependent variables: time to first fixation on the correct locus, accuracy of the spoken report, count of actions continued on stale status.
Lab participants who know they will be asked about status over-detect. Closer to product: insert an unrelated question mid-task, then suddenly ask about sync or connection, rather than running a detection task aimed at the status bar.
Where it stops holding
Flows whose whole surface is the status (install wizard, full-screen playback, a blocking payment page) do not need a spare corner — the page is the locus. Once that page is left, if the same fact must still be queryable elsewhere, it still needs a stable home. Watches and vehicle screens cannot spare a persistent bar; the locus may be a single dot by the crown, provided that dot does not move or share its slot with other badges. Screen readers have no “place”; stable expression becomes a queryable status region or a consistent spoken lead-in: every disconnect starts with the same phrase, not sometimes the title and sometimes the button. In live collaboration, other people’s cursors roam; that is content, not system status. Connection, permission, conflict still need an anchor that does not follow a cursor.
Applying it
- Give each class of system fact a home: connection, sync, save, permission, session — one locus per class, no moving house across routes.
- Use transients only to shout “this just changed”; after the shout the fact must still be readable at home.
- Do not bury global status in a menu that must be opened. The home has to be scannable in the primary task view.
- How to check: take three discontinuous screenshots and circle the same class of status. If the circles are not in the same relative place, or the class is missing on one shot, the locus is already unstable. Then an interrupt test: mid-task switch to another app for ten seconds, come back, one glance only — “are we online / is it saved”. If they cannot answer, it was displayed, not visible.