Human Error and Interaction Styles in HCI

Human Error:

In HCI, human error refers to any mistakes or unintended actions users make while
interacting with a computer system. These errors can lead to frustration, wasted time,
and even safety hazards. Understanding how and why errors occur is crucial for
designing interfaces that minimize their likelihood. Here's a breakdown of some
common types of human errors:

• Slips: These are unintentional errors that occur during routine actions. For
example, a user might mistype a password or accidentally delete a file.
• Mistakes: These errors involve incorrect decisions based on faulty knowledge or
misunderstandings. For instance, a user might choose the wrong option from a
menu because the wording is unclear.
• Lapses: These errors happen due to lapses in attention or memory. For
example, a user might forget to save a document before closing the program.
HCI principles to minimize human error:
• Clear and consistent design: Interfaces should be predictable and use
consistent design patterns to minimize confusion.
• Minimizing distractions: Reduce unnecessary elements or animations that
compete for user attention.
• Providing feedback: The system should provide clear feedback to confirm user
actions and prevent accidental mistakes.
• Error prevention: Design interfaces that make it difficult to commit errors (e.g.,
confirmation prompts for critical actions).
• Error recovery: Provide mechanisms for users to easily recover from mistakes
(e.g., undo/redo functionality).
Interaction Styles:

Interaction style refers to the way users interact with a computer system. HCI
professionals consider different styles to cater to diverse user preferences and task
requirements. Here are some common interaction styles:

• Command Line Interface (CLI): Users interact with the system by typing
commands. This style is powerful but can be challenging for novice users.
 • Menu-driven Interface: Users select options from pre-defined menus. This style
is user-friendly but can be limiting for complex tasks.
• Graphical User Interface (GUI): Users interact with visual elements like
windows, icons, and menus. This is the most common style today, offering a
balance of ease of use and functionality.
• Natural Language Processing (NLP): Users interact with the system using
spoken language or text that resembles natural language. This style is becoming
increasingly popular, particularly for voice assistants and chatbots.
• Touchscreen Interface: Users interact with the system by touching elements on
a touchscreen display. This style is prevalent in mobile devices and tablets.
Choosing the right interaction style:

The selection of the interaction style depends on several factors:

• Target audience: Consider the user's technical skills and experience level.
• Task complexity: Some tasks are better suited for specific interaction styles
(e.g., complex tasks might benefit from a GUI with more options).
• Platform and device: The capabilities of the device and the intended platform
(desktop, mobile, etc.) will influence the available interaction styles.

Usability heuristics

Usability heuristics are a set of well-established principles that guide user interface (UI)
design towards usability. These principles, developed by Jakob Nielsen and Rolf Molich,
act as rules of thumb to help create interfaces that are intuitive, efficient, and minimize
user frustration. Here are the 10 core usability heuristics:

1. Visibility of system status: The system should always keep users informed
about what's happening through clear and timely feedback. This includes
providing appropriate feedback during actions (e.g., loading indicators), keeping
users updated on the system's state (e.g., progress bars), and offering
confirmation messages for critical actions.
2. Match between system and the real world: The interface should use language,
concepts, and metaphors familiar to the user. This reduces the learning curve
and makes interaction more intuitive. Imagine using an ATM that has cryptic
symbols instead of clear labels for transactions - this goes against this heuristic.
 3. User control and freedom: Users should feel in control of the system and have
the ability to easily undo or redo mistakes. This includes providing clear exit
options, allowing users to navigate back to previous steps, and offering
functionality like "undo/redo" when applicable.
4. Consistency and standards: Maintain consistency in design patterns (e.g.,
layout, terminology, behavior) across the interface. This creates a predictable
experience for users and minimizes confusion. Imagine an app where buttons
look completely different on each screen - that would violate this principle.
5. Error prevention: The design should prevent errors from happening in the first
place. This can involve using data validation to catch incorrect input, offering
clear instructions to avoid misunderstandings, and designing interfaces that
make it difficult to perform unintended actions.
6. Recognition rather than recall: Users should be able to recognize options and
functions easily, minimizing the need to memorize complex instructions. This is
achieved by using clear and concise labels, self-explanatory icons, and
interfaces that are visually intuitive.
7. Flexibility and efficiency of use: Cater to users with varying experience levels.
Offer options for both novice and expert users. This might involve features like
tutorials for beginners and keyboard shortcuts for experienced users.
8. Aesthetic and minimalist design: Interfaces should be visually pleasing and
avoid unnecessary clutter. Focus on clarity and prioritize the most important
information. While visual design can be subjective, interfaces that are clean and
uncluttered tend to be easier to navigate and understand.
9. Help users recognize, diagnose, and recover from errors: Even with the best
design, errors can happen. Error messages should be clear, concise, and offer
solutions for the user to recover from the mistake. Avoid technical jargon and
offer guidance on how to fix the issue.
10. Help and documentation: Provide appropriate help documentation and support
resources within the interface for users who need additional guidance. This could
include FAQs, tutorials, or a user manual accessible within the application.

These heuristics are not a strict checklist, but rather a framework to guide the design
process.

Interface metaphors and models

Here's a breakdown of interface metaphors and models:

Interface Metaphors:
• Definition: An interface metaphor is a design concept that deliberately compares
a new computer system or feature to a familiar object or activity from the real
world. This comparison helps users understand the functionality and purpose of
the interface element by drawing on their existing knowledge.
• Benefits:
o Reduce learning curve: Metaphors can simplify complex concepts by
relating them to something users already understand.
o Improve usability: By using familiar references, metaphors can make
interfaces more intuitive and easier to learn.
o Enhance user experience: Well-chosen metaphors can make interacting
with a computer system more enjoyable and engaging.
• Examples:
o The desktop metaphor on personal computers, where files are stored in
folders on a virtual desktop, mimicking a physical workspace with folders
for documents.
o The trash can icon used to represent deleting unwanted files, referencing
the real-world action of throwing something away.
o Email clients that use a mailbox metaphor, with features like inbox, sent
mail, and drafts, mirroring a traditional mail system.
Interface Models:
• Definition: An interface model is a more general conceptual framework that
represents the underlying structure and organization of an information system. It
goes beyond visual resemblance and focuses on the overall functionality and
behavior of the system.
• Benefits:
o Improves communication: Models provide a shared understanding
between designers, developers, and users about how the system works.
 o Guides design decisions: Models can inform the design process by
outlining the system's functionalities and user interactions.
o Supports user expectations: A well-defined model can help users form
expectations about how the system will behave.
• Examples:
o The Model-View-Controller (MVC) model is a common software design
paradigm that separates the data (model) from the way it is presented
(view) and how the user interacts with it (controller).
o The Entity-Relationship (ER) model in databases represents the
relationships between different types of data entities (e.g., customers,
orders, products).
Choosing the Right Metaphor or Model:
• The effectiveness of a metaphor or model depends on the specific context and
target audience.
• A well-chosen metaphor should be clear, consistent, and not overused. A strained
metaphor can lead to confusion if it doesn't accurately represent the functionality.
• The chosen model should be appropriate for the complexity of the system and
effectively communicate the underlying structure.

Visual design for interfaces

Visual design plays a critical role in shaping the user experience (UX) of interfaces. It's
about creating not just aesthetically pleasing interfaces, but also ones that are
functional, communicate effectively, and guide users towards their goals. Here are
some key aspects of visual design for interfaces:

• Visual Hierarchy and Balance: Arranging elements on the screen with a clear
hierarchy helps users focus on the most important information. This can be
achieved through size, color, spacing, and typography variations. Imagine a
website where all elements are the same size and weight - it would be visually
overwhelming and difficult to navigate.
• Color Theory: Colors evoke emotions and can be used strategically to guide
user attention, create a specific mood, and enhance brand recognition.
Understanding color theory and user psychology helps designers choose color
palettes that are not only visually appealing but also serve a purpose.
 • Typography: The selection of fonts and their use plays a big role in readability
and user experience. Fonts should be clear, legible, and appropriate for the
brand and content. Using a variety of fonts strategically can also establish visual
hierarchy and guide users.
• White Space (Negative Space): Effective use of white space (empty space
around elements) is crucial for creating a balanced and uncluttered interface.
White space prevents visual overload and improves readability.
• Imagery and Icons: Well-chosen visuals can enhance communication, convey
information quickly, and add visual interest. Icons should be clear, recognizable,
and consistent with the overall design style.
• Alignment and Consistency: Maintaining consistent alignment of elements
across the interface creates a sense of order and professionalism. This applies to
spacing, margins, and the overall layout.
• Design for Accessibility: Visual design should consider users with visual
impairments. This includes using sufficient color contrast, providing alternative
text descriptions for images, and ensuring the interface is usable with assistive
technologies.
Benefits of Effective Visual Design:
• Improved User Experience: A well-designed interface is not only visually
appealing but also intuitive and easy to use. This leads to a more positive user
experience.
• Enhanced Brand Communication: Visual design elements like color,
typography, and imagery can effectively communicate a brand's personality and
values.
• Increased User Engagement: Visually engaging interfaces can capture user
attention, keep them interested, and encourage them to explore further.
• Clarity and Usability: Effective visual design promotes clear communication of
information and functionality, leading to a more usable interface.