Usability Principles

Front

Visibility of System Status

Back

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

Front

Match between System and Real World

Back

The system should speak the users’ language, using familiar words and concepts instead of technical terms.

Front

User Control and Freedom

Back

Users should have clearly marked 'emergency exits' (e.g., Undo, Redo, Cancel) to leave unwanted states without going through long processes.

Front

Consistency and Standards

Back

Follow platform and industry conventions so that users don’t get confused by different words, icons, or actions that mean the same thing.

Front

Error Prevention

Back

Design should aim to prevent problems before they happen, such as confirmations before destructive actions.

Front

Recognition rather than Recall

Back

Minimize the user’s memory load by making options, actions, and objects visible, so users don’t have to remember information across steps.

Front

Flexibility and Efficiency of Use

Back

Allow both novice and expert users to use the system efficiently (e.g., shortcuts for experienced users).

Front

Aesthetic and Minimalist Design

Back

Interfaces should not contain irrelevant or rarely needed information. Every extra element competes with relevant information.

Front

Help Users Recognize, Diagnose, and Recover from Errors

Back

Error messages should be expressed in plain language, precisely indicate the problem, and suggest a constructive solution.

Front

Help and Documentation

Back

Provide easy-to-search, task-focused, and concise instructions to help users complete tasks when needed.