Jakob Nielsen's Usability Heuristics
Ten heuristic evaluation checkpoints proposed by Jakob Nielsen. When there is no time for user research, they help quickly assess usability and identify improvements.1
1. Visibility of System Status
The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time. (The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.)
2. Match Between the System and the Real World
The design should speak the users’ language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Follow real-world conventions, making information appear in a natural and logical order. (The design should speak the users’ language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Follow real-world conventions, making information appear in a natural and logical order.)
3. User Control and Freedom
Users often perform actions by mistake. They need a clearly marked “emergency exit” to leave the unwanted action without having to go through an extended process. (Users often perform actions by mistake. They need a clearly marked “emergency exit” to leave the unwanted action without having to go through an extended process.)
4. Consistency and Standards
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions. (Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.)
5. Error Prevention
Good error messages are important, but the best designs carefully prevent problems from occurring in the first place. Either eliminate error-prone conditions, or check for them and present users with a confirmation option before they commit to the action. (Good error messages are important, but the best designs carefully prevent problems from occurring in the first place. Either eliminate error-prone conditions, or check for them and present users with a confirmation option before they commit to the action.)
6. Recognition Rather than Recall
e.g. field labels or menu items) should be visible or easily retrievable when needed. (e.g. field labels or menu items) should be visible or easily retrievable when needed.)
- Recall: Remembering without cues. Harder than recognition.
- Recognition: Remembering when relevant cues are provided. Easier than recall.
7. Flexibility and Efficiency of Use
Shortcuts - hidden from novice users - may speed up the interaction for the expert user so that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions. (Shortcuts - hidden from novice users - may speed up the interaction for the expert user so that the design can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.)
- Jef Raskin, however, cautions against the expert/novice dichotomy, arguing that a single interface should be provided for everyone wherever possible. See: The humane interface
8. Aesthetic and Minimalist Design
Interfaces should not contain information that is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility. (Interfaces should not contain information that is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility.)
- Aesthetics in design are more than “eye candy”; they also affect usability. See: Emotional design
9. Help Users Recognize, Diagnose, and Recover from Errors
no error codes), precisely indicate the problem, and constructively suggest a solution. (no error codes), precisely indicate the problem, and constructively suggest a solution.)
10. Help and Documentation
It’s best if the system doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks. (It’s best if the system doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks.)