Visibility of System Status
The interface should always tell the user what is going on, through timely and appropriate feedback.
Definition
The first of Jakob Nielsen's ten usability heuristics. Users need a continuously accurate picture of the system's state so they can decide what to do next, and every action needs a visible consequence within a reasonable time.
Expert heuristic. A review criterion developed by practitioners. Useful and widely taught, but evaluated by judgement rather than measurement.
On this page
Three questions status has to answer
Where am I, what is happening right now, and did my action work. Almost every status failure is one of those three going unanswered.
Status is not only loading indicators. A selected navigation item, a saved indicator, an unread count, a connection state and a validation result are all system status.
Matching the indicator to the wait
| Situation | Right response |
|---|---|
| Instant local change | Change the state. No indicator. |
| Under 1 second network call | Optimistic update, or a disabled control. Delay any spinner by 200 to 400ms. |
| 1 to 10 seconds | Skeleton shaped like the result, or a determinate progress bar. |
| Over 10 seconds | Progress with an estimate, and a way to leave and be notified. |
| Background job | Persistent status surface the user can return to. |
| Failure | Inline message next to the cause, stating what happened and what to do. |
Do
- Mark the current location in navigation, with more than colour alone.
- Confirm saves explicitly, including autosaves.
- Surface offline and degraded states rather than failing silently.
- Announce dynamic status changes to assistive technology with a live region.
Do not
- Show a spinner for something that finishes in 150ms.
- Use a toast for a message the user needs to act on. Toasts vanish.
- Report success before the write has actually landed, unless you can roll back visibly.
- Leave a disabled button with no explanation of what would enable it.
In practice
Autosave indicators
Document editorsA quiet 'Saved' with a timestamp, replaced briefly by 'Saving' during the write, removes the anxiety that drives compulsive manual saving. Silence reads as risk.
Selected state in navigation
Web applicationsMarking the current section with weight and a rule, not just colour, answers 'where am I' for every user including those who cannot distinguish the colour.
Sources
Where a source establishes something narrower than the popular reading of it, the note says so.
10 Usability Heuristics for User Interface Design
J. Nielsen, Nielsen Norman Group, 1994, revised 2020
Understanding Success Criterion 4.1.3: Status Messages
W3C, WCAG 2.1
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Applied through
Where this shows up as a concrete interface decision.
- BreadcrumbComponent
- Progress IndicatorComponent
- ToastComponent
- CollaborationPattern
- Loading StatesPattern
- NotificationsPattern
- Optimistic UIPattern
- Skeleton ScreensPattern
- Heuristic EvaluationResearch method
- MotionUI foundation
- Error MessagesUX writing
Check your work
Review passes that test whether this was done properly.
- Dashboard UX ChecklistChecklist
Related concept
Connected closely enough to change how you apply this.
- Status Messages and Live RegionsAccessibility
- Doherty ThresholdLaw
- FeedbackPrinciple
- Gulfs of Execution and EvaluationPrinciple