Visibility of system status

The law

A product should always let people know what it is doing and what just happened.

Feedback has to arrive quickly enough to be connected to the action that caused it. Without it, people repeat actions, abandon tasks that were working, or trust results they should have questioned.

Where it comes from

Jakob Nielsen and Rolf Molich introduced heuristic evaluation in 1990, with a list of principles that experts could check an interface against. In 1994 Nielsen analysed 249 usability problems from real evaluations and derived the revised list of ten heuristics that is still used. Visibility of system status is the first of them. Nielsen Norman Group's article on Visibility of System Status explains the heuristic with current examples.

The idea is older than the list: it reflects research on response times and feedback in interactive systems from the 1960s onward. What the heuristic adds is a single, checkable question for every screen: can people tell what state the system is in?

What it means for an interface

• Acknowledge every action. A pressed button changes state, a saved form says so, an added item shows up in the cart.
• Show progress for anything slow. For waits of more than a second or so, show that work is happening. For long waits, show how far along it is.
• Make the current state obvious. Which page am I on, which filter is applied, am I signed in, is this saved? These should be answerable at a glance.
• Tell people about changes they did not cause. A lost connection, an expired session or a changed price should be visible before it causes an error.

Examples

File uploads. An upload with a progress bar, a percentage and a clear finished state lets people wait calmly. A silent upload makes them click again or leave the page.

Autosave. A document editor that shows "Saving…" and then "Saved" removes the fear of losing work. Without it, people save manually out of habit or doubt.

Navigation state. A highlighted current item in the navigation and a page title that matches it answer "where am I?" without any thought.

Where it is misapplied

• Feedback noise. Toasts for every trivial action train people to ignore all of them, including the important ones.
• Fake progress. Progress bars that do not reflect real progress break trust once people notice.
• Status only in colour. A state shown only by a colour change is invisible to some people. Use text or an icon too.
• Status that disappears too fast. A confirmation that vanishes in a second may never be seen. Keep important outcomes on screen.

Checklist

• Every action produces visible feedback within a moment.
• Operations longer than a second show that work is in progress.
• The current location, filters and sign-in state are visible on every screen.
• Saving, sending and payment outcomes are stated in words, not only by colour.
• System changes, such as lost connection or expired sessions, are announced before they cause errors.

Related

• The Doherty Threshold: how fast feedback has to be to feel immediate.
• User control and freedom: people can only undo what they can see happened.
• Goal-Gradient Effect: visible progress keeps people going.
• Course: Heuristic evaluation.
• Pillar: UX audit.