10 Usability Hueristics for UI (nn/g study guide)

Question 1

Visibility of System Status

Answer 1

The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.

Give users the outcome of their prior interactions and determine next steps

No action with consequences to users should be taken without informing them

Real world likeness: “You are here” on maps

Question 2

Match Between the System and the Real World

Answer 2

The design should use layman’s terms. Follow the design of things in the real world (like the knobs on a stove)

Question 3

User Control and Freedom

Answer 3

Give users a clearly marked “emergency exit”

Question 4

Consistency and Standards

Answer 4

Jakob’s Law. Follow platform and industry conventions. Follow what designs have been used on website prior to. Follow what designs have been used on website prior

Question 5

Error Prevention

Answer 5

Best design=prevent problems from occurring. Eliminate error-prone conditions, or check for them and present users with a confirmation option before they commit to the action.

Avoid slips (errors by user inattention): provide constraints and defaults

Prevent mistakes: remove memory burdens, supporting undo option, and warning users

Question 6

Recognition Rather than Recall

Answer 6

Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed.

Lessen memory load by making elements, actions, and options
available.
-give “help in context” rather than a long tutorial

Question 7

Flexibility and Efficiency of Use

Answer 7

Provide shortcuts for expert users. Allow users to tailor frequent actions.

Provide Accelerators (keyboard shortcuts), Personalization, and Customization

Question 8

Aesthetic and Minimalist Design

Answer 8

Do not include information that is irrelevant or rarely needed. Every extra element diminishes visibility of more useful information

Question 9

Help Users Recognize, Diagnose, and Recover from Errors

Answer 9

Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.

Use bold, red text

Question 10

Help and Documentation

Answer 10

Best to present the help/documentation in context right when the users need it. List exact steps the users should follow.