Loading / Waiting
The system makes it clear that an operation is in progress and, when possible, communicates its duration or progress, reducing anxiety and uncertainty during the wait.
Interactive use case
The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. If the user is asking 'is something happening?', the system is failing this principle. If, however, the system consistently understands what is happening, when, and with what outcome, Visibility of System Status is respected.
The system makes it clear that an operation is in progress and, when possible, communicates its duration or progress, reducing anxiety and uncertainty during the wait.
Interactive use case
Every input produces immediate and perceptible feedback, so the user knows the action has been received and is being processed or completed.
Interactive use case
Activities that are not immediately active remain visible in the system state, preventing the user from losing context or repeating actions already initiated.
Interactive use case
The system promptly reports anomalies and crashes, explaining what is happening and whether any action is required.
Interactive use case
The interface clearly communicates the current position and progress within a path, preventing disorientation and abandonment.
Interactive use case
The status of the data entered is always clear, allowing the user to immediately know whether what they are doing is correct or requires correction.
Interactive use case
Configurations instantly reflect their actual state, so the user never has to guess whether a change has been applied or not.
Interactive use case