Heuristic Evaluation

Spark Usability Issues

Jakob Nielsen

  1. Visibility of System Status
  2. Match between System and the Real World
  3. User Control and Freedom
  4. Consistency and Standards
  5. Error Prevention
  6. Recognition Rather than Recall
  7. Flexibility and Efficiency of Use
  8. Aesthetic and Minimalist Design
  9. Recognition and Recovering from Errors
  10. Help and Documentation

Visibility of System Status

Keep users informed about what is going on, through appropriate feedback within reasonable time.

#visibility_of_system_status

Keep users informed about what is going on, through appropriate feedback within reasonable time.

Match between System and the Real World

Speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

#match_between_system_and_the_real_world

Speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

User Control and Freedom

Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

#user_control_and_freedom

Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

Consistency and Standards

Users doesn't wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

#consistency_and_standards

Users doesn't wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

Error Prevention

Even better than good error messages is a careful design which prevents a problem 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

Even better than good error messages is a careful design which prevents a problem 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 Rather than Recall

Minimize the user's memory load by making objects, actions, and options visible. The user doesn't need to remember information from one part of the dialogue to another. Instructions for use of the system is visible or easily retrievable whenever appropriate.

#recognition_rather_than_recall

Minimize the user's memory load by making objects, actions, and options visible. The user doesn't need to remember information from one part of the dialogue to another. Instructions for use of the system is visible or easily retrievable whenever appropriate.

Flexibility and Efficiency of Use

Accelerators, unseen by the novice user, speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

#flexibility_and_efficiency_of_use

Accelerators, unseen by the novice user, speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

Aesthetic and Minimalist Design

Dialogues does not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

Recognition and Recovering from Errors

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

#recognition_and_recovering_from_errors

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

Help and Documentation

Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information is easy to search, focused on the user's task, lists concrete steps to be carried out, and isn't too large.

#help_and_documentation

Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information is easy to search, focused on the user's task, lists concrete steps to be carried out, and isn't too large.

Questions?