Contextual inquiry takes research out of the meeting room and into the places where work actually happens. By observing users in their natural environment, designers discover the workarounds, shortcuts, environmental pressures, and invisible constraints that no interview could ever reveal. The gap between what people say they do and what they actually do is often enormous, and contextual inquiry is built specifically to close that gap.
What It Is
Contextual inquiry is a structured field research method developed by Hugh Beyer and Karen Holtzblatt as part of their Contextual Design approach. It combines observation with an ongoing conversation: the researcher watches a participant do their real work, asks questions in the moment, and interprets what they see collaboratively with the participant. This master-apprentice dynamic, where the researcher acts as a curious learner and the participant acts as the expert, produces exceptionally grounded, actionable insights.
How to Run It
Schedule sessions at the participant's actual workplace or wherever they perform the relevant activity. Arrive ready to observe, not to lead. Ask the participant to carry on with real tasks while you watch and ask clarifying questions as they arise. Use prompts like 'I noticed you just did X — can you tell me more about why?' rather than interrupting with pre-planned questions. Sessions typically run one to two hours. Photograph the environment, tools, and artefacts with permission. Debrief with your team the same day to capture interpretations while context is still vivid.
When to Use It
Contextual inquiry is most powerful early in a project when the team needs to understand a work domain deeply before defining a solution. It is especially valuable when designing for specialised professional contexts, such as healthcare, manufacturing, or finance, where the complexity of real work is difficult to describe in abstract interviews. It is also useful when existing products are being redesigned and the team wants to understand actual usage patterns rather than assumed ones.
Tips for Success
Resist the temptation to help when participants struggle. Their struggle is data. Build a rapport that feels collaborative rather than evaluative so participants do not hide their workarounds. Document physical artefacts like sticky notes, printouts, and personal filing systems: these reveal mental models better than words alone. Debrief in pairs so one person can focus entirely on observation while the other manages the conversation.
