Scribd
Upload
91 views3 pages

Visibility of System Status

The document discusses principles of user interface design including: - Providing feedback on system status so users are aware of outcomes and can plan next steps. - Communicating in language familiar to users instead of internal jargon. Respecting real-world customs. - Allowing users to easily exit processes without lengthy procedures to maintain a sense of control. - Maintaining consistency with platform/industry conventions to reduce cognitive load on users.

Uploaded by

Sean Catapang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
91 views3 pages

Visibility of System Status

The document discusses principles of user interface design including: - Providing feedback on system status so users are aware of outcomes and can plan next steps. - Communicating in language familiar to users instead of internal jargon. Respecting real-world customs. - Allowing users to easily exit processes without lengthy procedures to maintain a sense of control. - Maintaining consistency with platform/industry conventions to reduce cognitive load on users.

Uploaded by

Sean Catapang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Sean Catapang

IT12S9

Visibility of system status


The design should always keep consumers up to date on what is going on by providing
suitable feedback in a timely manner.
When users are aware of the current system status, they can learn the outcome of their
previous interactions and plan their next steps. Predictable encounters build trust in both
the product and the brand.

Match between system and the real world


The design should communicate in the language of the users. Instead of internal jargon,
utilize words, phrases, and concepts that the user is familiar with. Respect real-world
customs by arranging information in a natural and logical manner.

The manner you should design is heavily influenced by your target audience. Terms,
concepts, iconography, and visuals that appear to you and your colleagues to be completely
clear may be unknown or confusing to your users.

User control and freedom


Users frequently make mistakes when doing actions. They require a clearly designated
"emergency exit" in order to leave the unpleasant action without having to go through a
lengthy procedure.

It generates a sense of independence and confidence when people may easily back out of a
process or undo an activity. Exits help users to keep control of the system and avoid being
stuck or upset.
Consistency and standards
Users should not have to guess whether various words, contexts, or actions indicate the
same thing. Adhere to platform and industry conventions.

According to Jakob's Law, individuals spend the majority of their time utilizing digital
items other than yours. Users' expectations are set by their previous experiences with
other products. Failure to maintain consistency may increase the cognitive load of
consumers by requiring them to learn something new.

Error prevention
Good error messages are vital, but the finest designs take care to avoid problems in the
first place. Eliminate error-prone situations, or check for them and provide users with a
confirmation choice before committing to an action.

Recognition rather than recall


Make items, actions, and options visible to reduce the user's memory load. The user should
not have to recall information from one section of the interface to the next. When using
the design, information such as field labels or menu items should be visible or easily
accessible.

Flexibility and efficiency of use


Hidden from novice users, shortcuts may speed up the interaction for the expert user,
allowing the design to cater to both naïve and experienced users. Allow users to customize
frequently performed tasks. Flexible procedures can be carried out in a variety of ways,
allowing people to choose the approach that works best for them.

Aesthetic and minimalist design


Interfaces should not include information that is irrelevant or is only used infrequently.
Every additional unit of information in an interface competes with the relevant pieces of
information, lowering their relative visibility.

Help users recognize, diagnose, and recover from


errors
Error messages should be written in straightforward language (no error codes), describe
the problem precisely, and constructively offer a remedy. These error notifications should
also have graphic modifications to assist people notice and recognize them.

Help and documentation


It is preferable if the system does not require any further explanation. However,
documentation may be required to assist users in understanding how to complete their
tasks. The content of help and documentation should be easy to find and focused on the
user's task. Keep it brief, and state specific steps that must be taken.

You might also like