Latest / 5 Minute UX / Contextual Inquiry: Planning and Conducting Sessions
Transcript
- 0:08This lesson is Contextual Inquiry: Planning and Conducting
- 0:11Sessions. Let's get started.
- 0:19Imagine a team convinced users skip steps, only to discover
- 0:22observation reveals a hidden workflow constraint they never
- 0:24anticipated. That disconnect happens because users behave
- 0:27differently in their actual environment than they ever would
- 0:30in a sterile lab. So when we move from assumptions to
- 0:32evidence-based insights through direct observation, we finally
- 0:35see what's actually driving behavior. This is why we must
- 0:38plan and conduct a contextual inquiry session that captures
- 0:41those real-world dynamics. We'll start by identifying the four
- 0:44key phases of a contextual inquiry study to build a solid
- 0:46foundation. Then we'll describe the balance between observation
- 0:49and probing questions to ensure we capture the full story
- 0:52without leading the witness. Finally, you'll apply the half-
- 0:55day session structure to a real workplace scenario where every
- 0:58minute counts. By the end, you won't just know the theory;
- 1:01you'll be ready to run a session that uncovers the truth. Now, to
- 1:04how context changes everything.
- 1:10By the end of this section, you'll be able to recruit the
- 1:13right participants and prepare your observation guide for a
- 1:16successful session. You'll learn to apply the half-day session
- 1:18structure to a real workplace scenario, ensuring you capture
- 1:21authentic workflows. Start by recruiting participants who
- 1:24represent the actual user base and specific tasks you need to
- 1:27study. If you pick the wrong people, your entire inquiry
- 1:29collapses because you won't see the real problems. You need
- 1:32individuals who actually perform the work, not just those who
- 1:35manage it. Next, prepare an observation guide with open-
- 1:37ended prompts, not a rigid script. A rigid script forces
- 1:40the conversation and kills the natural flow of the workplace.
- 1:43Your guide should help you remember key questions while
- 1:45leaving room for unexpected discoveries. Finally, schedule
- 1:48half-day sessions to allow for natural workflow rhythms and
- 1:51necessary breaks. Shorter visits often miss the complex patterns
- 1:54that emerge over several hours. This extended time lets you see
- 1:57how users recover from errors and handle interruptions.
- 2:04When you arrive at the workplace, your first move is to
- 2:06observe silently to establish a baseline of natural behavior.
- 2:09You must resist the urge to speak immediately because any
- 2:11interruption alters the very actions you are trying to study.
- 2:14This initial silence lets the user settle into their rhythm
- 2:16before you introduce your presence. Once that baseline is
- 2:18clear, you can begin asking probing questions only when a
- 2:20behavior seems unclear or unexpected. Do not interrupt the
- 2:23flow for minor details, because the goal is to understand the
- 2:25deep context behind a specific anomaly. You ask "why" only when
- 2:28the action does not match the expected workflow or when a tool
- 2:30is used in a strange way. The core challenge here is to
- 2:32describe the balance between observation and probing
- 2:34questions without disrupting the user's natural flow. If you talk
- 2:37too much, you become a distraction that forces the user
- 2:39to perform rather than work. So when you do speak, keep your
- 2:41questions brief and tied directly to what you just
- 2:43witnessed happening. While you are watching, you must take
- 2:46detailed notes on actions, tools used, and environmental
- 2:48constraints that shape the work. Write down exactly which
- 2:50software version they are running and how their desk setup
- 2:52limits their movement. These specific details are often the
- 2:55difference between a superficial finding and a breakthrough
- 2:57insight for your team. Remember that these sessions are
- 2:59typically structured as half-day sessions to allow enough time
- 3:02for deep immersion without exhausting the participant. A
- 3:04shorter window might not capture the full cycle of their work,
- 3:06but a full day creates fatigue that ruins the data quality. You
- 3:09aim for that sweet spot where the user is engaged but not
- 3:11drained by the process. This approach ensures you can apply
- 3:14the half-day session structure to a real workplace scenario
- 3:16with confidence and precision. By following this rhythm of
- 3:18silent watching, targeted questioning, and rigorous note-
- 3:20taking, you gather the rich data needed for true understanding.
- 3:23You are not just watching a user; you are mapping the entire
- 3:25ecosystem of their daily work. By the end of this lesson, you
- 3:28will be able to plan and conduct a contextual inquiry session
- 3:30that yields actionable insights. You will know exactly when to
- 3:33stay silent and when to speak, ensuring your data remains
- 3:35authentic and reliable. This is the practical skill that
- 3:37separates a good researcher from a great one in the field.
- 3:45Let's say you have a participant who is a cashier struggling with
- 3:48a slow inventory system during peak hours. This concrete
- 3:51scenario sets the stage for your observation guide. You're not
- 3:53just watching; you're looking for the friction points that
- 3:56matter most. Instead of asking a vague question like "Is this
- 3:59slow?", the researcher asks, "What happens when the system
- 4:01lags?" This shift in phrasing is critical. It moves the
- 4:04conversation from a simple yes or no to a detailed account of
- 4:06their actual workflow. That specific probing question
- 4:09reveals a workaround where staff manually track stock, bypassing
- 4:12the system entirely. This is the kind of hidden insight you only
- 4:15find by balancing observation with targeted questions. You are
- 4:17effectively applying the half- day session structure to a real
- 4:20workplace scenario.
- 4:27Pause and think about your last project, and ask yourself if you
- 4:30truly applied the half-day session structure to a real
- 4:32workplace scenario. Most of us skip the planning phase, but
- 4:35that is exactly where your study gains its power. Now, draft a
- 4:38five-point observation guide for your next user task, focusing
- 4:40strictly on what you see before you speak. This simple list
- 4:43forces you to respect the balance between observation and
- 4:46probing questions, which is critical for authentic insights.
- 4:48Identify one real workplace scenario to observe this week,
- 4:51then practice asking just one open-ended probing question
- 4:53during that routine interaction. By taking these three concrete
- 4:56steps, you will be ready to plan and conduct a contextual inquiry
- 4:59session with confidence. Remember, the goal is to move
- 5:01from theory to practice, turning your observation skills into
- 5:04actionable research that drives real change.
- 5:09Welcome to The Take. I'm joined by a fellow practitioner and
- 5:12together we're going to dig into Contextual Inquiry: Planning and
- 5:15Conducting Sessions — what it means in practice and what's
- 5:18worth remembering.
- 5:20[HOST] That tension between observing silently and probing
- 5:23for the "why" is where most field studies actually break
- 5:26down. [LEARNER] I've seen researchers talk too soon, and
- 5:29the participant immediately switches to "performance mode"
- 5:32instead of real work. [HOST] Exactly, and that performance
- 5:34mode hides the messy workarounds we're actually trying to find.
- 5:37[LEARNER] It's a hard discipline to hold back when you see a
- 5:40weird tool use, but interrupting kills the context you need.
- 5:43[HOST] That's why the half-day window matters so much, since
- 5:46shorter visits just catch the surface layer of their routine.
- 5:49[LEARNER] I agree, but fitting a four-hour block into a manager's
- 5:52schedule is often the hardest part of the recruiting phase.
- 5:55[HOST] You have to sell the value of seeing the full cycle,
- 5:58including how they recover from errors after lunch. [LEARNER]
- 6:01Speaking of capturing that data, I'm wondering if AI
- 6:04transcription tools might actually help us take better
- 6:06notes without looking up. [HOST] They can handle the verbatim
- 6:09stuff, but AI still misses the environmental constraints like a
- 6:12crowded desk or a bad screen angle. [LEARNER] True, the tool
- 6:15can't feel the friction of a cramped workspace or the glare
- 6:18on the monitor. [HOST] So the tech handles the transcript, but
- 6:21we still need to be the ones mapping the ecosystem around the
- 6:24user. [LEARNER] That distinction is crucial, because the real
- 6:27insight usually lives in the gap between what they say and what
- 6:30they do. [HOST] And if we lose that gap by talking too much or
- 6:33looking at a screen, we've missed the point of the inquiry
- 6:36entirely.