Contextual Inquiry: Planning and Conducting Sessions

Learn the essential steps to plan and execute a contextual inquiry study in a real workplace. You will master recruiting participants, preparing observation guides, and balancing observation with probing questions to uncover deep user insights. Learning Objective: By the end of this lesson, learners will be able to plan and conduct a contextual inquiry session. Transcript The Need for Contextual Inquiry Imagine a team convinced users skip steps, only to discover observation reveals a hidden workflow constraint they never anticipated. That disconnect happens because users behave differently in their actual environment than they ever would in a sterile lab. So when we move from assumptions to evidence-based insights through direct observation, we finally see what's actually driving behavior. This is why we must plan and conduct a contextual inquiry session that captures those real-world dynamics. We'll start by identifying the four key phases of a contextual inquiry study to build a solid foundation. Then we'll describe the balance between observation and probing questions to ensure we capture the full story without leading the witness. Finally, you'll apply the half-day session structure to a real workplace scenario where every minute counts. By the end, you won't just know the theory; you'll be ready to run a session that uncovers the truth. Now, to how context changes everything. Key Points: Scenario: A team assumes users skip steps, but observation reveals a hidden workflow constraint. Why context matters: Users behave differently in their actual environment than in a lab. Goal: Move from assumptions to evidence-based insights through direct observation. Recruiting and Preparing By the end of this section, you'll be able to recruit the right participants and prepare your observation guide for a successful session. You'll learn to apply the half-day session structure to a real workplace scenario, ensuring you capture authentic workflows. Start by recruiting participants who represent the actual user base and specific tasks you need to study. If you pick the wrong people, your entire inquiry collapses because you won't see the real problems. You need individuals who actually perform the work, not just those who manage it. Next, prepare an observation guide with open-ended prompts, not a rigid script. A rigid script forces the conversation and kills the natural flow of the workplace. Your guide should help you remember key questions while leaving room for unexpected discoveries. Finally, schedule half-day sessions to allow for natural workflow rhythms and necessary breaks. Shorter visits often miss the complex patterns that emerge over several hours. This extended time lets you see how users recover from errors and handle interruptions. Key Points: Recruit participants who represent the actual user base and specific tasks. Prepare an observation guide with open-ended prompts, not a rigid script. Schedule half-day sessions to allow for natural workflow rhythms and breaks. Conducting the Session When you arrive at the workplace, your first move is to observe silently to establish a baseline of natural behavior. You must resist the urge to speak immediately because any interruption alters the very actions you are trying to study. This initial silence lets the user settle into their rhythm before you introduce your presence. Once that baseline is clear, you can begin asking probing questions only when a behavior seems unclear or unexpected. Do not interrupt the flow for minor details, because the goal is to understand the deep context behind a specific anomaly. You ask "why" only when the action does not match the expected workflow or when a tool is used in a strange way. The core challenge here is to describe the balance between observation and probing questions without disrupting the user's natural flow. If you talk too much, you become a distraction that forces the user to perform rather than work. So when you do speak, keep your questions brief and tied directly to what you just witnessed happening. While you are watching, you must take detailed notes on actions, tools used, and environmental constraints that shape the work. Write down exactly which software version they are running and how their desk setup limits their movement. These specific details are often the difference between a superficial finding and a breakthrough insight for your team. Remember that these sessions are typically structured as half-day sessions to allow enough time for deep immersion without exhausting the participant. A shorter window might not capture the full cycle of their work, but a full day creates fatigue that ruins the data quality. You aim for that sweet spot where the user is engaged but not drained by the process. This approach ensures you can apply the half-day session structure to a real workplace scenario with confidence and precision. By following this rhythm of silent watching, targeted questioning, and rigorous note-taking, you gather the rich data needed for true understanding. You are not just watching a user; you are mapping the entire ecosystem of their daily work. By the end of this lesson, you will be able to plan and conduct a contextual inquiry session that yields actionable insights. You will know exactly when to stay silent and when to speak, ensuring your data remains authentic and reliable. This is the practical skill that separates a good researcher from a great one in the field. Key Points: Step 1: Observe silently first to establish baseline behavior before intervening. Step 2: Ask probing questions only when behavior is unclear or unexpected. Step 3: Balance observation with inquiry to avoid disrupting the user's natural flow. Step 4: Take detailed notes on actions, tools used, and environmental constraints. Worked Example: The Checkout Process Let's say you have a participant who is a cashier struggling with a slow inventory system during peak hours. This concrete scenario sets the stage for your observation guide. You're not just watching; you're looking for the friction points that matter most. Instead of asking a vague question like "Is this slow?", the researcher asks, "What happens when the system lags?" This shift in phrasing is critical. It moves the conversation from a simple yes or no to a detailed account of their actual workflow. That specific probing question reveals a workaround where staff manually track stock, bypassing the system entirely. This is the kind of hidden insight you only find by balancing observation with targeted questions. You are effectively applying the half-day session structure to a real workplace scenario. Key Points: Example: Watching a cashier struggle with a slow inventory system during peak hours. Action: Researcher asks, 'What happens when the system lags?' instead of 'Is this slow?' Insight: Reveals a workaround where staff manually track stock, bypassing the system entirely. Your Next Step Pause and think about your last project, and ask yourself if you truly applied the half-day session structure to a real workplace scenario. Most of us skip the planning phase, but that is exactly where your study gains its power. Now, draft a five-point observation guide for your next user task, focusing strictly on what you see before you speak. This simple list forces you to respect the balance between observation and probing questions, which is critical for authentic insights. Identify one real workplace scenario to observe this week, then practice asking just one open-ended probing question during that routine interaction. By taking these three concrete steps, you will be ready to plan and conduct a contextual inquiry session with confidence. Remember, the goal is to move from theory to practice, turning your observation skills into actionable research that drives real change. Key Points: Draft a 5-point observation guide for your next user task. Identify one real workplace scenario to observe this week. Practice asking one open-ended probing question during a routine interaction.