Ten Usability Heuristics Flashcards
Define the Visibility of System Status principle
Designs should keep users
informed about what is going
on, through appropriate,
timely feedback.
Define the Match between
System and
the Real World principle
The design should speak the
users’ language. Use words,
phrases, and concepts
familiar to the user, rather
than internal jargon.
Define the User Control and Freedom principle
Users often perform actions by
mistake. They need a clearly
marked “emergency exit” to
leave the unwanted state.
Define the Consistency and Standards principle
Users should not have to
wonder whether different
words, situations, or actions
mean the same thing. Follow
platform conventions.
Define the Error Prevention principle
Good error messages are
important, but the best
designs prevent problems from
occurring in the first place.
Define the Recognition Rather Than Recall principle
Minimize the user’s memory
load by making elements,
actions, and options visible.
Avoid making users
remember information.
Define the Flexibility and Effciency of Use principle
Shortcuts — hidden from novice
users — may speed up the
interaction for the expert user.
Define the Aesthetic and
Minimalist
Design principle
Interfaces should not contain
information which is irrelevant.
Every extra unit of information in
an interface competes with the
relevant units of information.
Define the Recognize,
Diagnose, and
Recover from Errors principle
Error messages should be
expressed in plain language (no
error codes), precisely indicate
the problem, and constructively
suggest a solution.
Define the Help and Documentation principle
It’s best if the design doesn’t
need any additional explanation.
However, it may be necessary to
provide documentation to help
users understand how to
complete their tasks.