User Research - Part II
CS408 Human Computer Interaction Lecture 20 explores ethnographic field research and contextual inquiry, providing Virtual University students with comprehensive methodologies to observe and analyze human activities within real-world environments. Originating in cultural anthropology, ethnography literally means 'writing the culture' and focuses on understanding how social activities are organized without imposing external analytical frameworks. In software engineering, researchers distinguish between ethnography of, for, and within development practices. A classic case study by Heath and colleagues in a London securities dealing room demonstrates the indispensability of ethnographic observation: proposed technological upgrades including touchscreen order terminals and noise-cancelling headphones threatened to destroy the traders' subtle peripheral awareness, inadvertent listening, and collaborative spatial orientation that made instantaneous deal execution possible. The curriculum structures ethnographic investigation around core dimensions: plans and procedures, awareness of mutual work, paperwork versus computer work, local knowledge workarounds, and spatial-temporal workspace organization. The lecture presents Beyer and Holtzblatt's Contextual Design framework, highlighting Contextual Inquiry based on the Master-Apprentice model. In this relationship, the user acts as a master craftsman while the researcher acts as an apprentice, observing tasks first-hand and asking clarifying questions without interrupting flow. Contextual Inquiry relies on four fundamental principles: Context (gathering data at the user's actual workplace), Partnership (establishing collaborative exploration rather than an interrogative dynamic), Interpretation (assigning shared meaning to observed behaviors while actively verifying hypotheses with users), and Focus (maintaining purposeful inquiry boundaries). Alan Cooper's Goal-Directed Design adapts these ethnographic techniques for agile product development by utilizing smaller design teams, identifying user goals before documenting granular tasks, and expanding beyond corporate offices into consumer domains. To prepare effectively for field studies, interaction designers construct Kim Goodwin's persona hypothesis. Rather than relying solely on demographic segmentation, the persona hypothesis maps expected behavioral variables, such as usage frequency, domain expertise versus technical expertise, motivation, and lifestyle attitudes. In business domains, roles frequently map to organizational job descriptions, whereas consumer products demand analysis of behavioral ranges and environmental variables like company scale, IT administration culture, and security restrictions. Designers plan interview schedules ensuring each behavioral variable is explored across four to six interviews through overlapping candidate screening profiles. Essential for CS408 midterm examination review, solved past papers by Moaaz, and Waqar Siddhu study notes, this lecture equips students with rigorous qualitative field inquiry skills.
No questions available yet.
There are currently no examination questions published for User Research - Part II. Explore other curriculum units or build a custom quiz with the practice builder.