The test is whether users can always answer what the system is doing and where they are

What it is

This heuristic gives visibility of system status a measurable test: at any paused moment, users should answer two questions—what the system is processing now and where they are in the task or information space. The answer must come from the interface, not memory of the previous page or guesswork.

Why it happens

Tasks cross clicks, pages, asynchronous updates, and interruptions; the presence of a visual element does not mean users can connect it into a situational model. Evidence must be collected in users’ words because designers automatically fill gaps once they know the internal state. The two questions cover process awareness and location awareness; missing either produces duplicate actions, disorientation, or reluctance to continue.

Studying it

Freeze the interface at random task points and ask: “What is the system doing now? Where are you? What can you do next?” Record correct answers, wrong answers, backtracking, and time. Retrospective think-aloud, situation-awareness questionnaires, and log comparison also work; analyze by task stage, interruption, and asynchronous events rather than only final satisfaction.

Where it stops holding

The required grain depends on the task. Ordinary browsing need not expose service calls, but high-consequence flows require users to know whether saving, publication, review, or synchronization took effect. Experts may infer status from sparse cues while novices need explicit information; returning across pages, poor networks, and multiple tabs are common failure points.

Applying it

• Insert random pause questions into usability scripts and score correct answers on both process and location.
• Replay failed segments to find missing current object, stage, save state, or breadcrumb.
• For every critical page, define three things users should be able to state and add them to acceptance checks.

Related

• Same group: B3.01.1 Users should always know what the system is doing · B3.01.2 Status feedback must appear within a reasonable time · B3.01.3 Long tasks need progress rather than only a busy indicator · B3.01.5 After waiting long enough, feedback must upgrade from a momentary cue to a persistent status presentation · B3.01.6 Background tasks also need visibility; leaving the current screen does not make the task disappear · B3.01.7 Status should express progress and remaining work, not merely that the system is busy
• Nearby: G1 Navigation and Information Architecture · Q2 Usability Evaluation
• Search terms: situation awareness · think aloud protocol · wayfinding