Heuristic Evaluation

A heuristic evaluation has many benefits:

• It can be performed at any stage during the design process. However, conducting one at the very beginning means you get feedback early on.
• You can conduct it before or alongside other usability testing methods, such card sorting.
• It can be much easier and cheaper to conduct than other research methods e.g., large scale in-person user research or other field research.
• Depending on what you’re evaluating, it can be quite fast to conduct and obtain results.

Basic steps

1. Gather several evaluators (3-4 is good)
2. Determine users and context
3. Team members apply heuristics independently
4. Consolidate and prioritize findings     

Nielsen's Heuristics

• Visibility of system status
• Match between system and real world
• User control and freedom
• Consistency and standards
• Error prevention
• Recognition rather than recall
• Flexibility and efficiency of use
• Aesthetic and minimalist design
• Help with errors
• Provide help and documentation (if needed)

247 Web Usability Guidelines

Review the website using each of the 247 web usability guidelines and mark the site as either conforming or not conforming to the guideline. All guidelines are context-specific, so if a particular guideline does not apply to the site it's OK to ignore it. A summary of results is calculated based on input into qualifying guidelines, and an overall score is generated along with a radar plot visualization (see below) of that score.

• Home page usability - 20 guidelines
  
• Task orientation - 44 guidelines
  
• Navigation and ID - 29 guidelines
  
• Forms and data entry - 23 guidelines
  
• Trust and credibility - 13 guidelines
  
• Writing and content quality - 23 guidelines
  
• Page layout and visual design - 38 guidelines
  
• Search usability - 20 guidelines
  
• Help, feedback and error tolerance - 37 guidelines
  

Visualizations

• Radar Plot

Cognitive Walkthrough

Basic steps

1. Convene several analysts (typically usability experts)
2. Determine users and context
3. Specify representative task(s) and the actions needed to complete the task(s)
4. Walk through the action sequence, answering and documenting the analysis questions for each action     

Analysis Questions

1.  Will users be trying to produce whatever effect the action has?
2. Will users see the control (button, menu, switch, etc.) for the action?
3. Once users find the control, will they recognize that it produces the effect they want?
4. After the action is taken, will users understand the feedback they get, so they can go on to the next action with confidence?     

Pluralistic Walkthrough (Participatory Design Review)

Performed early in the design process with a group of users, developers and product owners

Basic steps

1. Determine users and context
2. Assemble design materials depicting the interface (may be paper and pencil prototypes)
3. Specify representative task(s) and the actions needed to complete the task(s)
4. Convene participants, which include usability specialists, product developers and representative users
5. For each step, each participant records what he or she believes the next correct action is
6. Participants discuss their recorded actions; the users start the discussion