UX

Summary heuristic evaluation

Heuristic evaluation
Freepik

On this page

What is a heuristic?

Don't let the word heuristic fool you: it means nothing more than a rule or a guideline. So heuristics are nothing more than rules, guidelines of how a software system should behave in order to create the best user experience. 

The list below can be used as a checklist to benchmark the user interface of a software system. 

Jakob Nielsen’s 10 principles for interaction design

  1. Visibility of system status
    The system should always keep users informed about what is going on. Through appropriate feedback and within a reasonable time.
  2. Match between system and the real world
    The system should speak the users' language, with words, phrases and concepts familiar to the user. Follow real-world conventions, making information appear in a natural and logical order.
  3. 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.
  4. Consistency and standards
    Users should not have to wonder whether different words, situations, or actions mean the same thing.
  5. Error prevention
    Even better than good error messages is a careful design which prevents a problem from occurring in the first place.
  6. Recognition rather than recall
    Instructions for use of the system should be visible or easily retrievable whenever appropriate. The user should not have to remember information from one part of the dialogue to another.
  7. Flexibility and efficiency of use
    Allow users to tailor frequent actions. Use ‘accelerators’ to make the system easy to use for experienced and inexperienced users.
  8. Aesthetic and minimalist design
    Dialogues should not contain information which is irrelevant or rarely needed.
  9. Help users recognize, diagnose, and recover from errors
    Error messages should be expressed in plain language, precisely indicate the problem, and constructively suggest a solution.
  10. 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 should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Source: Nielsen, J. (1994, April 24). 10 Usability Heuristics for User Interface Design. Retrieved November 7, 2019 from https://www.nngroup.com/articles/ten-usability-heuristics.

Complete list of heuristics

A. Visibility of system status

  1. Is status feedback provided continuously?
  2. Are warning messages displayed for long enough?
  3. Is there provision for some form of feedback?

B. Match between the system and the real world

  1. Are the words, phrases and concepts used familiar to the user?
  2. Does the task sequence parallel the user's work processes?
  3. Is information presented in a simple, natural and logical order?
  4. Is the use of metaphors easily understandable by the user?
  5. Does the system cater for users with no prior experience of electronic devices?
  6. Does the system make the user's work easier and quicker than without the system?
  7. Does the system fit in with the environment in which the user's tasks are carried out?
  8. Can the system realistically reflect real world situations and appear to respond to the user?
  9. Are important controls represented on the screen and is there an obvious mapping between them and the real controls?

C. User control and freedom

  1. Are facilities provided to "undo" (or "cancel") and "redo" actions?
  2. Are there clearly marked exits (for when the user finds themselves somewhere unexpected)?
  3. Are facilities provided to return to the top level at any stage (eg links back to homepage)?

D. Consistency and standards

  1. Is the use of terminology, controls, graphics and menus consistent throughout the system?
  2. Is there consistency between data entry and data display?
  3. Is the interface consistent with any platform conventions?
  4. Have ambiguous phrases/actions been avoided?
  5. Is the interface consistent with standard PC conventions?
  6. Have colour and style conventions been followed for links (and no other text)?

E. Error prevention

  1. Is a selection method provided (eg from a list) as an alternative to direct entry of information?
  2. Is user confirmation required before carrying out a potentially 'dangerous' action (eg deleting something)?
  3. Does the system ensure work is not lost either by user or system error?
  4. Does the system prevent calls being accidentally made?
  5. Are the options given in dialog boxes obvious?
  6. Does the system provide foolproof synchronization with a PC?
  7. Has the possibility of the user making errors been removed?
  8. Is the system robust and safe enough for its surroundings?

F. Recognition rather than recall

  1. Are help and instructions visible or easily accessible when needed?
  2. Is the relationship between controls and their actions obvious?
  3. Is it possible to search for information (eg a phone number) rather than entering the information directly?
  4. Is the functionality of the buttons on the device obvious from their labels?
  5. Are input formats (eg dates or lengths of names) and units of values indicated?
  6. Is the functionality of novel device controls (eg thumbwheels) obvious?

G. Flexibility and efficiency of use

  1. Does the system allow for a range of user expertise?
  2. Does the system guide novice users sufficiently?
  3. Is it possible for expert users to use shortcuts and to tailor frequent actions?
  4. Is it possible to access and re-use a recent history of instructions (eg recently called numbers)?
  5. Does the system allow for a range of user goals and interaction styles?
  6. Does the system allow all functionality to be accessed either using function buttons or using the stylus?
  7. Is it possible to replace and restore default settings easily?
  8. Have unnecessary registrations been avoided?

H. Aesthetic and minimalist design

  1. Is the design simple, intuitive, easy to learn and pleasing?
  2. Is the system free from irrelevant, unnecessary and distracting information?
  3. Are icons clear and buttons labelled and is the use of graphic controls obvious?
  4. Is the information displayed at any one time kept to a minimum?
  5. Is the number of applications provided appropriate (and has 'featuritis' been avoided)?
  6. Has the need to scroll been minimized and where necessary, are navigation facilities repeated at the bottom of the screen?
  7. Is the system easy to remember how to use?
  8. Have excessive scripts, applets, movies, graphics and images been avoided?

I. Help users recover from errors

  1. Do error messages describe problems sufficiently, assist in their diagnosis and suggest ways of recovery in a constructive way?
  2. Are error messages written in a non-derisory tone and refrain from attributing blame to the user?
  3. Is it clear how the user can recover from errors?

J. Help and documentation

  1. Is help clear and direct and simply expressed in plain English, free from jargon and buzzwords?
  2. Is help provided in a series of steps that can be easily followed?
  3. Is it easy for the user to search, understand and apply help text?

K. Navigation

  1. Is navigational feedback provided (eg showing a user's current and initial states, where they've been and what options they have for where to go)?
  2. Are any navigational aids provided (eg find facilities)?
  3. Does the system track where the user was in the last session (and any progress made)?
  4. Has opening unecessary new browser windows been avoided?

L. Use of modes

  1. Does the system use different modes appropriately and effectively?
  2. Is it easy to exit from each mode of use?

M. Structure of information

  1. Is there a hierarchical organization of information from general to specific?
  2. Are related pieces of information clustered together?
  3. Is the length of a piece of text appropriate to the display size and interaction device?
  4. Has the number of screens required per task been minimized?
  5. Does each screen comprise 1 document on 1 topic with the most important information appearing at the top?
  6. Has hypertext been used appropriately to structure content and are links intuitive and descriptive?
  7. Have pages been structured to facilitate scanning by the reader?
  8. Are the URLs, page titles and headlines straightforward, short and descriptive?
  9. Has excessive use of whitespace been avoided?
  10. Has textual content been kept to a maximum of two columns?

N. Enjoyment

  1. Is the system fun to use?

O. Physical constraints

  1. Are function buttons large enough to be usable?
  2. Is the screen visible at a range of distances and in various types of lighting?
  3. Does the touch-screen cater for users touching the screen quickly and slowly?
  4. Is the distance between targets (eg icons) and the size of the targets appropriate (size should be proportional to distance)?
  5. Has the use of text in images and large or irregular imagemaps been avoided?

P. Extraordinary users

  1. Is the use of colour restricted appropriately (and suitable for colour-blind users)?
  2. Do the buttons allow for use by older, less agile fingers or people wearing gloves?
  3. Do buttons give tactile feedback when selected?
  4. Is the touch-screen usable by people of all heights and those in wheelchairs?
  5. Are equivalent alternatives provided for visual and auditory content?
  6. Have accessibility and internationalization guidelines been applied if appropriate?

Source: ID-book (n.d.). Full set of heuristics. Retrieved November 7, 2019 from http://www.id-book.com/secondedition/catherb/Complete_heurs.php.