Nielsen's Heuristics
A Visual Guide to Usability Principles
Jakob Nielsen's 10 usability heuristics are general principles for interaction design. They are called "heuristics" because they are broad rules of thumb rather than specific usability guidelines. These principles help identify usability problems in user interface design.
1
Visibility of System Status
Keep users informed
The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. Users should never wonder about the current state of the system.
2
Match System & Real World
Speak the user's language
The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions.
3
User Control & Freedom
Provide emergency exits
Users often choose system functions by mistake and need clearly marked "emergency exits" to leave unwanted states without having to go through extended dialogue.
4
Consistency & Standards
Follow platform conventions
Users should not wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions to maintain consistency.
5
Error Prevention
Prevent problems
Better than good error messages is careful design that prevents problems from occurring. Eliminate error-prone conditions or check for them and present confirmation options.
6
Recognition vs Recall
Minimize memory load
Minimize the user's memory load by making objects, actions, and options visible. Instructions for use should be visible or easily retrievable whenever appropriate.
7
Flexibility & Efficiency
Accommodate all users
Accelerators may speed up interaction for expert users. Allow users to tailor frequent actions and provide both novice and expert paths through the interface.
8
Aesthetic & Minimalist Design
Less is more
Dialogues should not contain irrelevant or rarely needed information. Every extra unit of information competes with relevant units and diminishes their relative visibility.
9
Help Users with Errors
Constructive error messages
Error messages should be expressed in plain language, precisely indicate the problem, and constructively suggest a solution to help users recover from errors.
10
Help & Documentation
When needed, make it helpful
Even though it's better if the system can be used without documentation, it may be necessary to provide help. Such information should be easy to search and focused on the user's task.
Your subscription could not be validated.
You have successfully subscribed
Posts recentes
Tags
Páginas
Categorias
Menu
