# Contextual Inquiry

A collaborative field interview in which researchers observe people doing real work and ask questions within the activity’s natural context.

- Type: method
- Domain: Research & behavior
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/contextual-inquiry/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Choose a work activity and recruit participants who can demonstrate it in a representative context.
2. Agree on consent, recording, confidentiality, safety, and what may not be observed.
3. Observe with an apprentice mindset, asking brief questions at natural pauses without taking control.
4. Probe artifacts, decisions, interruptions, handoffs, and differences between prescribed and actual practice.
5. Review interpretations with the participant, then model patterns and exceptions across sessions.

## A 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.

## Where 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.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/contextual-inquiry/#visualization-contextual-inquiry>)

## Sources

1. [Contextual Interviews and How to Handle Them](<https://www.interaction-design.org/literature/article/contextual-interviews-and-how-to-handle-them>) — Interaction Design Foundation · Professional reference
2. [Contextual Design](<https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/contextual-design>) — Interaction Design Foundation · Academic reference

## Related topics

- [Field Study](<https://wiki.soroush.uk/topic/field-study/>)
- [Ethnographic Research](<https://wiki.soroush.uk/topic/ethnographic-research/>)
- [User Interviews](<https://wiki.soroush.uk/topic/user-interviews/>)
