A field research method where a researcher observes and interviews users in their natural environment as they perform tasks. Contextual inquiry reveals real-world workflows, workarounds, and environmental factors that lab-based research often misses.
Common contexts
- Visiting warehouse workers on the floor to observe how they actually use a logistics app in noisy conditions
- Shadowing nurses during a shift to understand how an EMR system fits into a clinical workflow
- Watching home cooks use a recipe app at the counter, beside hot surfaces, with wet hands
Use when
Use contextual inquiry when you have reason to believe lab behavior and real-world behavior will diverge significantly — particularly for physical environments, professional workflows, or anything involving time pressure, distractions, or specialized domain knowledge the design team doesn't share.
Avoid when
Contextual inquiry is expensive in time and logistics — don't use it to answer questions that a remote interview or diary study would answer just as well. It's also inappropriate when the observation itself would disturb a sensitive or private workflow, such as financial decision-making or personal healthcare management.
The most valuable thing you see in a contextual inquiry is never what the user does — it's the workarounds they've built around what the product fails to do, because those workarounds are your design backlog written in human behavior.
Real-world examples
- IDEO researchers embedded with surgical teams in operating rooms to observe instrument handling in context, leading to redesigned tool grips that reduced hand fatigue.
- Microsoft sent researchers into people's homes to observe how families actually shared a single PC, directly informing the multiple-account and parental-control features in Windows XP.
- Intuit researchers sit beside small-business owners as they do their books, observing real workflows in TurboTax and QuickBooks to uncover pain points invisible in lab settings.