HCI and User Experience Study Guide

Distinguishing Core HCI Concepts: Usability vs. User Experience

  • The fundamental difference between Usability and User Experience (UX) lies in their scope: Usability focuses on the pragmatic aspects of a system, such as efficiency, effectiveness, and user satisfaction in achieving specific goals. User Experience is a broader term encompassing all aspects of the user's interaction with the company, its services, and its products, including emotions, beliefs, preferences, and perceptions.

  • According to Hassenzahl’s model, the major components of User Experience are divided into pragmatic attributes (related to usability and utility) and hedonic attributes (related to stimulation, identification, and evocation). The model emphasizes that the overall quality of an interactive product is a combination of these two perspectives.

  • User Experience (UX) vs. Customer Experience (CX): While UX focuses specifically on the interaction between a user and a product or system, CX is a broader discipline that includes all interactions a person has with a brand, from marketing and sales to customer support and product usage over time.

  • The distinction between User Requirements and User Expectations is vital. Requirements refer to the functional and non-functional needs the system must fulfill, while expectations are the preconceived notions users have about how the system should behave, look, and feel. Managing expectations is critical for achieving high UX satisfaction.

Interface Design Principles, Standards, and Heuristics

  • Nielsen's Heuristics are 10 general principles for interaction design. Rather than just listing them, their application involves checking a design against these principles (e.g., Visibility of System Status, Match Between System and the Real World, User Control and Freedom) to identify potential usability issues during an expert review.

  • Consistency is achieved in the design process through the application of design patterns, adherence to style guides, and the use of centralized design systems. It ensures that similar actions and elements look and behave the same way throughout the application, reducing the user's cognitive load.

  • "User Interface Styleguides" are documents that contain rules and standards for the visual design and behavior of interface elements. They include specifications for typography, color palettes, iconography, and component behavior. UI/UX designers use them to maintain consistency across different screens and modules of a project.

  • "De facto standards" are solutions or patterns that have become universally accepted through wide usage rather than official mandates (e.g., the shopping cart icon for e-commerce). They are important because users expect familiar patterns; deviating from them can cause confusion.

  • Design patterns are repeatable solutions to commonly occurring design problems. Five popular examples include:   - The Hamburger Menu for mobile navigation.   - Breadcrumbs for orientation.   - Search bars with auto-suggestions.   - Infinite scrolling.   - Cards for content organization.

User Research and Requirements Elicitation

  • Five methods for cooperation with users during requirements elicitation include:   - Interviews (structured or semi-structured).   - Workshops (collaborative design sessions).   - Contextual Inquiries (observations in the users' actual environment).   - Focus Groups.   - Card Sorting.

  • The "Persona" technique involves creating fictional characters that represent different user types within a targeted demographic. It is useful for humanizing data, helping designers empathize with users, and ensuring design decisions are focused on specific user needs rather than a generic user.

  • Usually, two types of Personas (A and B) are prepared to represent different market segments or user behaviors (e.g., a "Power User" vs. a "Novice User" or different demographic targets).

  • The "Empathy Map" is a collaborative tool used to gain a deeper insight into the users. It records what users say, think, do, and feel during their interaction with a product, bringing the benefit of aligning the team on a shared understanding of user needs.

  • The Customer Journey Map is a visual representation of the process a customer goes through to achieve a goal with a company. It is useful for identifying pain points, moments of truth, and opportunities for improvement across multiple touchpoints.

  • User Research Areas in IT projects include:   - Generative research: Understanding user needs before building a solution.   - Evaluative research: Testing existing solutions or prototypes.   - Quantitative research: Measuring behaviors using data (e.g., analytics).   - Qualitative research: Understanding the "why" behind behaviors.

Prototyping Strategies in Interaction Design

  • Low-fi (Low-fidelity) Prototyping involves using simple, low-cost materials like paper, sketches, or basic wireframes. Its benefits include rapid iteration, early detection of conceptual flaws, and encouraging honest feedback from stakeholders who feel the design is not yet "finished."

  • Types of Low-fi prototypes include:   - Paper prototypes.   - Hand-drawn sketches.   - Digital wireframes without styling.   - Storyboards.

  • High-fi (High-fidelity) Prototyping uses digital tools to create interactions that closely resemble the final product. While Low-fi is better for testing concepts and navigation at early stages, High-fi is better for testing specific interactions, visual design, and transitions at later stages.

  • The "Storyboard" technique uses a series of drawings or pictures to visualize the sequence of events and the context in which a user interacts with a system. It helps designers understand the user's environment and the triggers for using the app.

  • "Wizard of Oz" prototyping is a method where a human simulates the system's responses behind the scenes without the user knowing. This is particularly useful for testing complex interactions like AI or voice interfaces before actually developing the backend logic.

Usability Testing and Evaluation Methodologies

  • A typical usability testing session follows these steps:   - Introduction and briefing of the participant.   - Signing of consent forms.   - Pre-test interview/questionnaire.   - Performing specific tasks using the prototype/system.   - Post-test interview/questionnaire.   - Debriefing and analysis of results.

  • Data categories collected during usability testing:   - Quantitative: Task completion rates, time on task, error rates.   - Qualitative: User comments, facial expressions, thinking-aloud transcripts.

  • The "Think Aloud" technique requires users to verbalize their thoughts, feelings, and actions while performing tasks. The benefit is gaining direct insight into the user's mental model and identifying where they encounter confusion.

  • Specific Testing Types:   - Remote Usability Testing: Conducted online when users are in different locations; useful for reaching a diverse or global audience.   - Hallway Usability Testing: Testing with random people in a hallway or public space; useful for quick, low-cost feedback on general usability.   - A/B Testing: Comparing two versions of a design to see which performs better based on specific metrics.   - Low-cost Usability Testing: Uses minimal resources and fewer participants to find the most glaring issues quickly.

  • Heuristic Evaluation vs. User-Based Evaluation: Heuristic evaluation is an expert review (designers checking against rules), while user-based evaluation involves real users performing tasks. Heuristic is faster and cheaper, but user-based uncovers actual behavioral issues.

Interaction Paradigms: GUI, NUI, and Specialized Interfaces

  • Comparison of Interface Styles:   - CLI (Command Line Interface): Text-based, relies on recall, high learning curve but efficient for experts.   - GUI (Graphical User Interface): Uses visual elements like windows, icons, and menus; relies on recognition.   - NUI (Natural User Interface): Uses "natural" actions like touch, voice, or gestures (e.g., iPad, Alexa).

  • GUI vs. Web-based Interfaces: GUIs are often platform-specific (OS-native) and can have complex multi-window layouts, whereas web-based interfaces run in a browser, rely on HTML/CSS, and must account for browser compatibility and varying internet speeds.

  • Multimodal Interfaces use multiple modes of input/output (e.g., combining voice and touch). Advantages include accessibility and flexibility; weaknesses include increased complexity for the user and system errors in interpreting conflicting inputs.

  • Mobile User Interface Limitations:   - Small screen real estate.   - Varying lighting conditions.   - Touch target size constraints.   - Limited battery life and processing power.   - One-handed vs. two-handed usage.

Virtual Reality (VR), Augmented Reality (AR), and AI in UX

  • Virtual Reality (VR) immerses the user in a completely digital environment. Interaction is shifted from screen-based to spatial-based, requiring tracking of head and hand movements.

  • Augmented Reality (AR) overlays digital information onto the real world. Interaction affects users by blending digital tasks with their physical surroundings (e.g., IKEA Place or Pokemon Go).

  • AI-Enabled Systems:   - Hierarchy of User Expectations: Users expect AI to be accurate, helpful, and eventually proactive/predictive.   - Explainability: The requirement for AI systems to clarify why a specific decision or recommendation was made (e.g., "Why am I seeing this ad?").   - Trust: Can be improved by being transparent about data usage, providing clear error messages, and allowing user control over AI settings.

  • Voice User Interfaces (VUI) architectures:   - Cascade Architecture: Processes user input in a sequence of independent modules (ASR -> NLU -> TTS).   - Voice-to-Voice Architecture: Uses end-to-end neural models to process voice directly to voice, often resulting in more natural-sounding interactions.

Practice, Process, and Implementation

  • Factors affecting test scenarios for a pizza delivery app:   - User context (at home vs. on the move).   - Environmental factors (noise, distractions).   - System constraints (payment methods, GPS accuracy).

  • Prioritizing Usability Problems:   - Severity ratings (Impact x Frequency).   - Cost of fix vs. benefit.   - Criticality to core business tasks.

  • User Stories: These should be built with the format "As a [user], I want to [action] so that [benefit]." They provide benefit by focusing developers on the value delivered to the end-user rather than just technical tasks. In some cases, a team may create user stories without real users if the domain is highly technical or based on established industry standards/analogous systems.

  • Accessibility Guidelines: For consumer websites, these include providing alt-text for images, ensuring high color contrast, keyboard navigability, and supporting screen readers (WCAG standards).

  • CRM (Customer Relationship Management) Systems: These play a role in e-commerce by tracking user history and preferences to personalize economic interactions and build long-term loyalty.