VOCABULARY / ENTRY
Visibility of System Status
visibility-of-system-status
A system should always keep users informed about what is going on, through appropriate feedback within a reasonable time; this is the first of Nielsen's ten usability heuristics.
Recognizing it
- Any operation with delay or an uncertain outcome has a corresponding status presentation
- Feedback arrives within a timeframe matched to that interaction, not after the person has already retried
- The status shown reflects a fact the system has verified, not an assumed outcome
Concept boundary
This is a principle, not a concrete mechanism: the determinate progress bar, indeterminate progress, status message, and pressed-state feedback are all concrete realizations of it in different situations. It cares about whether state is communicated, not about how fast the system actually runs — being faster is a performance concern, outside this entry's scope.
When to consider it
- An action has delay, multiple steps, or an uncertain outcome, and people need to know whether the system received their input
- Choosing which concrete mechanism (progress bar, status message, pressed-state feedback, etc.) should represent the current status
- Evaluating whether an existing interface leaves people feeling disconnected or prompts repeated actions while waiting
When to be cautious
- Treating this principle as a spec for one specific control's pixels or duration
- Using it to argue the system must be faster — it constrains whether communication happens, not performance metrics
- Stacking irrelevant status indicators just to satisfy visibility, creating visual and auditory noise
Tradeoff
Continuously communicating status builds trust and reduces mistaken actions, but the status presentation itself takes up interface space and attention, and implementing and maintaining multiple kinds of status display adds cost.
Conditional rules · Editorial advice
Related entries
The determinate progress bar is one concrete realization of this principle for quantifiable tasks.
The status message is a concrete realization of this principle for outcome feedback.
Visibility requires that status be communicated; calm technology constrains how that communication should avoid seizing attention — together they shape the actual experience.
Letting people see the current status is one precondition for preventing mistaken actions; the two often work together.
Sources and what they support
Lists "visibility of system status" as the first usability heuristic, stated as: the design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.
Retrieved: 2026-09-15Elaborates on the heuristic: the better a system conveys its status, the better people understand the current situation, decide what to do next, and build trust in the system and the brand; the article emphasizes that immediate feedback helps people identify and correct errors quickly.
Retrieved: 2026-09-15 · Archived 2026-09-16The Level AA criterion requires that status messages be programmatically determinable through role or properties so assistive technology can present them to users without receiving focus — a concrete accessibility requirement for status visibility.
Retrieved: 2026-09-15 · Archived 2026-09-21Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.
Type extensions and implementation notes
No operable specimen yet; the illustration is editorial. A product must still verify that state changes are actually announced by assistive technology, that feedback latency in practice matches the interaction, and that any status wording shown corresponds to a result the system has genuinely verified.
{
"evidenceType": "Usability heuristic and accessibility standard",
"limit": "This entry constrains only whether and how status is communicated, not the pixels, duration, or actual performance of any concrete mechanism."
}Open the Agent JSON file for this entryThis file repeats every field of this entry verbatim and adds its sources, archive status, and editorial scope.