HCI Flashcards
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.
For example, the light on the elevator button.
Match between system and 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
For example, if you were instructing someone to build a car, you wouldn’t use technical words that they wouldn’t understand. You would do things in logical order, get wood before put in nail.
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.
For example, arrow arrows at the top of my page
Consistency and standards
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.
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.
Recognition versus recall
Minimize the user’s memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed.
Flexibility and efficiency
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.
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.
Help users recognise, diagnose, recover
Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.
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.
The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.
For example, the light on the elevator button.
Visibility of system status
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
For example, if you were instructing someone to build a car, you wouldn’t use technical words that they wouldn’t understand. You would do things in logical order, get wood before put in nail.
Match between system and real world
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.
For example, arrow arrows at the top of my page
User control and freedom
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.
Consistency and standards
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.
error prevention
