Contextual Inquiry
A collaborative field interview in which researchers observe people doing real work and ask questions within the activity’s natural context.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/contextual-inquiry/
01What it means
Contextual inquiry combines observation and interview in the place where an activity normally occurs. The participant acts as the domain expert, performing or reconstructing real work while the researcher watches, asks timely questions, and tests interpretations. The method attends to tools, interruptions, workarounds, social relationships, physical constraints, and tacit knowledge that ordinary interviews often miss.[1][2]
- 01Frame inquiryWork practice, decisions, participants, and ethics
- 02Observe real activityTools, environment, interruptions, and workarounds
- 03Ask in the momentClarify intent without taking over the task
- 04Interpret togetherCheck meanings, exceptions, and hidden knowledge
- 05Synthesize modelsSequence, artifacts, roles, breakdowns, and opportunities
- 06Validate gapsFollow up across people and contexts
The researcher is present and can change behavior; consent, privacy, operational safety, and the limits of a small contextual sample remain explicit.
02Why it matters
People routinely omit steps that feel obvious to them and may describe an ideal process rather than the messy one they use. Contextual inquiry reveals the surrounding system: paper notes beside software, unofficial handoffs, environmental constraints, and exceptions. This evidence supports products that fit real practice instead of a simplified workflow imagined in a meeting room.
03When to use it
Use it when designing for complex work, unfamiliar domains, multi-tool workflows, physical environments, or activities shaped by interruptions and collaboration. It is particularly useful before changing operational systems where undocumented workarounds carry important knowledge.
04How it works
- Choose a work activity and recruit participants who can demonstrate it in a representative context.
- Agree on consent, recording, confidentiality, safety, and what may not be observed.
- Observe with an apprentice mindset, asking brief questions at natural pauses without taking control.
- Probe artifacts, decisions, interruptions, handoffs, and differences between prescribed and actual practice.
- Review interpretations with the participant, then model patterns and exceptions across sessions.
05A practical example
A team redesigning inventory software shadows store receivers during deliveries. Workers repeatedly photograph damaged boxes with personal phones, jot supplier codes on cardboard, and enter data later because Wi-Fi fails at the loading bay. The resulting concept adds offline capture and a documented damage workflow rather than merely rearranging the existing desktop form.
06Where it breaks
Observation can affect behavior, and access may be restricted by privacy, safety, labor, or commercial concerns. A few sites may not represent other environments or shifts. Researchers can misread specialized practice, while participants may be unable to demonstrate rare events. The method requires careful consent and should not become covert surveillance or performance evaluation.
Common mistakes
- Turning the visit into a conference-room interview instead of observing actual activity.
- Interrupting constantly and preventing the participant from entering a natural workflow.
- Assuming one workplace or expert represents all contexts, roles, and exception cases.
07Sources
- Contextual Interviews and How to Handle ThemInteraction Design Foundation · Professional referenceContextual Interviews and How to Handle Them
- Contextual DesignInteraction Design Foundation · Academic referenceContextual Design