Lec 6: Contexual Inquiry

Usability Requirement Gathering in Human-Computer Interfaces

Introduction to Usability Requirement Gathering

• The lecture focuses on the requirement gathering stage of the interactive system development life cycle, specifically emphasizing usability requirements.

• The first stage, feasibility study, is skipped; the focus is on analyzing and specifying requirements.

Stages of Interactive System Development Life Cycle

• The life cycle includes several stages: design, prototyping, evaluation, coding and implementation, testing for usability, deployment, and maintenance.

• This lecture will delve into one specific approach for gathering usability requirements known as contextual inquiry.

Importance of Understanding Users

• A key aspect of developing an interactive system is having knowledge about the users (end users or laymen). The motto emphasized is "know the user."

• Usability is defined by ISO as how effectively a product can be used by specified users to achieve specific goals with efficiency and satisfaction in a specified context.

Contextual Inquiry Methodology

• Contextual inquiry is highlighted as a method to gather end-user requirements that equate to usability requirements. It has historical significance dating back over 30 years in user-centered design practices.

• This method combines observations and interviews; it’s not merely an interview process but involves observing users performing tasks in their natural work settings.

Observational Insights During Contextual Inquiry

• Observations allow designers to learn about task domains, work culture, and constraints within the workplace through direct interaction with users during their regular activities.

Understanding Usability Through Contextual Inquiry

The Importance of Observations in Design

• Usability is defined through observations, allowing designers to understand the specific work context and create usable products tailored to user needs.

• Identifying the target user group (e.g., managerial staff) is crucial; without understanding their behavior, design efforts may rely on intuition rather than informed decisions.

• Conducting contextual inquiries reveals key activities users engage in, such as setting meeting dates and reminders, which informs feature development for usability.

• If essential features are omitted from a product like a calendar app, it becomes less usable for users who would otherwise need to resort to other tools.

• Contextual inquiry emphasizes observing user behavior in natural settings to gather requirements effectively.

Methodologies of Contextual Inquiry

Active vs. Passive Modes

• Contextual inquiry can be conducted actively (observer present during observation) or passively (user activities recorded for later review).

• In active mode, observers take notes or record videos while physically present; passive mode relies on pre-recorded sessions reviewed afterward.

Observer's Role

• Observers should adopt an apprentice mindset, learning from users rather than instructing them; this master-apprentice model fosters genuine insights into user behavior.

• It’s critical that observers avoid lecturing users about their tasks during the observation process.

Stages of Contextual Inquiry

Five Key Stages

1. Planning

• This stage involves defining observation goals, gathering knowledge about the task domain, and arranging how observations will be recorded.

2. Initiating

Data Collection and Analysis Stages

Overview of Data Collection Stages

• The third stage involves actual data collection through observation, which is crucial for gathering relevant information.

• The fourth stage, known as the "closed stage," includes sending thank-you notes to participants and authorities, ensuring goodwill for future engagements if additional data is needed.

• The fifth and final stage is the "reflect stage," where collected data is analyzed to identify design goals, a process that can be complex due to the volume of data.

Analyzing Data with Affinity Diagram Method

• The affinity diagram method consists of five steps: generate ideas, display ideas, sort ideas into groups, create group headers, and finalize the diagram.

• An example application being developed is a class note-taking tool aimed at college students; contextual inquiry has been performed to gather user requirements.

Observations Recorded During Contextual Inquiry

Tools Used for Observations

• Three tools were utilized: traditional pen-and-paper note-taking, a web application (Notion), and Xournal++ desktop software to observe user behavior in real settings.

Key Observations from User Behavior

• Notable observations include challenges such as multi-level organization of notes not being possible and inaccuracies in freehand drawing during note-taking.

• Additional issues identified are cumbersome navigation between topics and difficulties in relocating content within physical notes.

Sorting Observations into Groups

Grouping Similar Behavioral Observations

• The sorting phase involves categorizing similar behavioral observations; for instance, "multi-level organization of notes not possible" aligns with "sorting lectures by dates torturous."

• Other grouped observations include navigation difficulties pointing towards similar user experience issues related to searching keywords in notes.

Analyzing Observations through Affinity Diagrams

Grouping Observations

• The process begins by correlating observations and categorizing them into groups, assigning names or headers to these groups based on the nature of the observations.

• For instance, three observations regarding note organization can be grouped under a header like "Navigation in Notebook," highlighting usability issues that need addressing.

Identifying Usability Issues

• Two observations about difficulties in searching keywords and cumbersome navigation are combined under the header "Navigation in Notes," indicating specific design challenges.

• Another group is formed around the challenges of erasing content and relocating notes, labeled as "Not Organization," further clarifying usability concerns.

Finalizing Groups and Headers

• After analyzing 19 total observations from contextual inquiries, they are organized into six distinct groups with corresponding headers for clarity.

• The method involves generating ideas during or after observations, brainstorming to sort similar insights into groups, which culminates in a structured outcome.

Design Recommendations

• Based on grouped observations, design recommendations emerge; for example, providing an option to erase content helps maintain neatness in notes.

• These recommendations stem from user feedback collected through contextual inquiry methods aimed at improving usability rather than detailing implementation strategies.

Understanding Functional Requirements

• The affinity diagram method leads to identifying functional requirements essential for system design while implicitly addressing usability needs.

• Key takeaways include understanding contextual inquiry as primarily observational rather than just interviews, supported by semi-structured interviews for clarification.

Conclusion of Learning Outcomes