10 Usability implications

This article is the Usability master Jakob Nielsen summed up 10 years ago, still enjoy today. Through this time span, it can be concluded that the topic of usability is not a product of a certain era, some research experience is still worth learning today. The seemingly short 10 revelations, incorporating a lot of project experience, will continue to guide designers to create higher quality products with the help of new internet technologies.

Don't look at it as a tutorial, it's just the distillation of the essence of thought. In a variety of projects, you will encounter strange situations, with a variety of characters to work together to achieve the goal. Only when we reach a consensus can we better improve our efficiency, which is the 10 inspiration.

In fact, this is 10 basic principles of interface design. They are called "inspirations" because they come from practical experience rather than boring theoretical knowledge.

Visibility of System State
Always let users know what is happening and give feedback at the right time.

The match between system and real world
Speak the language that the user understands, regardless of the word, the phrase or the elaboration some concepts, the terminology leaves the machine to read. Follow the rules of the real world to make the information behave naturally and logically.

User control and freedom of movement
It is common for users to make mistakes in feature selection, which requires an "emergency exit" that eliminates the need for additional conversations. Provides undo and redo functionality.

Consistency and standards
Don't let users have doubts about whether different words, situations, and behaviors represent the same thing. Follow the ideas of the platform.

Wrong prevention
A design that can prevent mistakes in the first time is better than a bunch of pretty error messages. You should remove the conditions that can induce error before the user acts, and remind the user to confirm the operation if necessary. Prevent。

System to identify rather than allow users to remember
Minimize user memory costs for goals, behaviors, and visible options. Don't let them memorize the information from which paragraph. At the same time the instructions for the system should be visible and, if necessary, provide the appropriate information.

Flexibility and efficiency
Shortcuts-No special instructions for novice users-but can improve the efficiency of expert-level users, which take into account experienced and inexperienced users. At the same time allows users to customize the frequent action: Allow users to use a higher frequency of operations, or the function by personal arrangement.

Minimalist design Aesthetics
Dialogs should not contain unrelated or unwanted information. Because each additional information unit, to a certain extent, will weaken the relative visibility of the original related information unit.

Help users identify, diagnose, and recover from errors
The error message should be in a simple language (do not use code, numbering, this thing only engineers can understand), targeted to clarify the problem, and with a constructive solution.

Help document
Even if a system is great and can be used without relying on help, it may still need help documentation. Any information, such as user-focused tasks, should be easily found and provided with concise and concrete steps for action.

Via useit.com
image:www.gettyimages.cn

Source: http://blog.b3inside.com/......y-heuristics/