The 10 Usability Heuristics

10 Usability Heuristics

10 Usability Heuristics

1. Visibility of System Status

2. Match Between System & the Real World

3. User Control & Freedom

4. Consistency & Standard

5. Error Prevention

6. Recognition Rather than Recall

7. Flexibility & Efficiency of Use

8. Aesthetic & Minimalist Design

9. Help Users Recognize, Diagnose & Recover from Errors

10. Help & Documentation

Visibility of system status

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. When a design is predictable, it builds trust in the product.

Match Between System & the Real World

Use what the user knows already. The system should speak the user’s language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

Match Between System & the Real World

People’s mental model of technology is based on their offline experiences combined with their prior digital interactions.

User Control & Freedom

A good UI design should never impose an action on the user or make decisions for them. Instead, the system should only suggest which paths the users can take.

User Control & Freedom

Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

Consistency & Standard

When users interact with a product, they should have no doubts about the meaning of words, icons, or symbols used.

Consistency & Standard

Designers should create a consistent design that speaks the same language and treats similar things in the same way.

Error Prevention

Minimize the likelihood of users making mistakes seeing error messages. You can achieve this by eliminating error-prone conditions. Also, let users see a confirmation option before they commit to an action.

Error Prevention

Designers should create a consistent design that speaks the same language and treats similar things in the same way. Think of a delete files button, for example. We must assume that users might accidentally click this button or that they can imagine a different result from it.

Recognition Rather than Recall

Minimize the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another.

Recognition Rather than Recall

Therefore, always leave small reminders of information that can assist users in navigating your designs. For example, menu items should be visibile or easy to access when needed.

Flexibility & Efficiency of Use

Your designs should benefit both inexperienced and experienced users. Notice that inexperienced users need more detailed information. But as they keep using a product, they became experienced users. This way, allowing them to customize processes like creating keyboard shortcuts is a good practice.

Aesthetic & Minimalist Design

each extra piece of information will compete with relevant, indispensable data and deviate attention from the most essential. Create interactions that contain only essential information. Avoid unnecessary visual elements that can overwhelm and distract users.

Help Users Recognize, Diagnose & Recover from Errors

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

Help & Documentation

Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.