#1

Visibility of System Status

Designs should keep users informed about what is going on, through appropriate, timely feedback.

Example:

Interactive mail maps have to show people where they currently are, to help them understand where to go next.

#2

Match between 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.

Example:

Users can quickly understand which stovetop control maps to each heating element.

#3

User Control and Freedom

Users often perform actions by mistake. They need a clearly marked “emergency exit” to leave the unwanted action.

Example:

Just like physical spaces, digital spaces need quick “emergency” exits too.

#4

Consistency and Standards

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform convenctions.

Example:

Check-in counters are usually located at the front of hotels, which meets expectations.

#5

Error prevention

Good error messages are important, but the best designs carefully prevent problems from occurring in the first place.

Example:

Guard rails on curvy mountain roads prevent drivers from failing off cliffs.

#6

Recognition rather than recall

Minimize the user’s memory load by making elements, actions, and options visible. Avoid making users remember information.

Example:

People are likely to correctly answer “is Lisbon the capital of Portugal?”.

#7

Flexibility and efficiency of use

Shortcuts — hidden from novice users — may speed up the interaction for the expert user.

Example:

Regular routes are listed on mpas, but locals with more knowledge of the area can take shortcuts.

#8

Aesthetic and minimal design

Interfaces should not contain information which is irrelevant. Every extra unit of information in an interface competes with the relevant unites of information.

Example:

A minimalist three-legged stool is still a place to sit.

#9

Recognize, diagnose , and recover from errors

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

Example:

Wrong-way signs on the road remind drivers that they are heading in the wrong direction.

#10

Help and documentation

It’s best if the design doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users complete their tasks.

Example:

Information kiosks at airports are easily recognizable and solve customers’ problems in context and immediately.

Resource: Nielsen Norman Group