Heuristic Evaluations in HCI

Heuristic Evaluations Overview

  • Heuristic evaluations serve as a structured method for providing design feedback.
  • They identify usability issues in interfaces through an experience-based assessment, especially when exhaustive evaluations are infeasible.
  • Heuristic evaluations are based on general guidelines which serve as rules of thumb regarding effective interface design.

Heuristic Approach to Design

  • Design problems frequently share commonalities; thus, similar guiding principles can be applied.
  • Various established guideline sets aid designers, such as:
    • Shneiderman’s Principles
    • GNOME Human Interface Guidelines
    • Tog’s First Principles (by Bruce Tognazzini)

Jakob Nielsen’s Heuristics

  • Established a set of 10 heuristic principles for design, initially published between 1989-1990 and updated over time.
  • The heuristics reflect the modern Western design philosophy.

Heuristic Rules Overview

Original Version (Nielsen’s Heuristics)
  1. Simple & natural dialogue
  2. Speak the users’ language
  3. Minimize users’ memory load
  4. Consistency
  5. Feedback
  6. Clearly marked exits
  7. Shortcuts
  8. Precise & constructive error messages
  9. Prevent errors
  10. Help and documentation
Current Version

H1: Visibility of system status
H2: Match between system and the real world
H3: User control and freedom
H4: Consistency and standards
H5: Error prevention
H6: Recognition rather than recall
H7: Flexibility and efficiency of use
H8: Aesthetic and minimalist design
H9: Help users recognize, diagnose, and recover from errors
H10: Help and documentation

Detailed Explanation of Heuristic Rules

H1: Visibility of System Status
  • Key Idea: The system should continuously inform users of its status through appropriate feedback in a reasonable timeframe.
  • Examples:
    • A lift control panel button lights up when pressed and stays lit while awaiting the elevator.
    • Google Chrome displays a downloads bar to inform users of file download progress.
H2: Match Between System and the Real World
  • Key Idea: The system should communicate in user-friendly language; familiar terms should be used rather than technical jargon.
  • Examples:
    • Online shopping platforms use icons akin to physical shopping carts and baskets to mimic real-world shopping experiences.
H3: User Control and Freedom
  • Key Idea: Users should easily exit unwanted states without lengthy dialogues, and should have undo/redo options available.
  • Examples:
    • Microsoft PowerPoint’s undo functionality allows users to revert changes through action history.
    • A cancel button can allow users to backtrack before permanently closing unsaved documents.
H4: Consistency and Standards
  • Key Idea: Interface elements should maintain consistent meanings across different contexts to prevent user confusion.
  • Examples:
    • Similar functionalities like copying, pasting, and saving should reflect consistent actions across Microsoft Office products.
    • Keybinding differences between macOS and Windows should be minimized for user familiarity.
H5: Error Prevention
  • Key Idea: Design should proactively prevent errors by either eliminating error-prone conditions or confirming actions before the user executes them.
  • Examples:
    • A prompt appears when attempting to delete an open PowerPoint file, preventing frustrating mistakes.
    • Confirmation dialogues for emptying the recycle bin alert users of multiple deletions to avoid accidental loss.
H6: Recognition Rather Than Recall
  • Key Idea: Users should not need to remember information from separate parts of the interface; relevant information should be visible or easily retrievable.
  • Examples:
    • Google Chrome tab icons allow users to identify open websites without needing to memorize tab names.
H7: Flexibility and Efficiency of Use
  • Key Idea: Provide shortcuts and interfaces that can cater to both novice and expert users, tailoring frequent actions for advanced users.
  • Examples:
    • Google Chrome's keyboard shortcuts speed up actions for experienced users, streamlining their workflow.
H8: Aesthetic and Minimalist Design
  • Key Idea: Avoid unnecessary information in dialogues that may distract or overwhelm the user.
  • Examples:
    • Google Chrome's home screen features a clean interface, while overloaded designs (like lingcars.com) detract user focus.
H9: Help Users Recognize, Diagnose, and Recover from Errors
  • Key Idea: Error messages should clearly articulate issues and suggest constructive solutions.
  • Examples:
    • Login error messages on platforms like Mailchimp or Pinterest explicitly state the problem and guide users to recovery steps.
H10: Help and Documentation
  • Key Idea: Although minimizing documentation is ideal, accessible help options should still be provided to assist users.
  • Examples:
    • The Google Chrome Help Center replicates the main search interface, allowing users to seek assistance intuitively.

Applying Heuristic Rules

  • Create a structured evaluation process encompassing:
    1. Planning/Preparation: Set specific use cases and evaluations.
    2. Briefing/Training: Familiarize evaluators with the product and context.
    3. Running Evaluation: Collect observations independently without discussion.
    4. Reporting Results: Prioritize identified issues based on severity.
  • Evaluation format includes problem descriptions, violated heuristics, severity ratings, and proposed fixes.