UX glossary · engl. Contextual Inquiry
Contextual Inquiry
Contextual inquiry is a research method where you observe and interview people in their real work environment. It shows you how they actually get tasks done, not just how they describe it.
Imagine your team is building an app for nurses. In interviews, they tell you they log medication on the tablet right after giving it. When you visit the ward, you see something else: notes scribbled on a glove, entries added at the end of the shift, and the tablet mounted on a wall out in the hallway.
What people say about their work and what they actually do are often two different things. That gap is exactly what contextual inquiry is designed to close.
Explained simply
Contextual inquiry is a user research method where you observe and talk to people in the place where they really get their tasks done: the office, the workshop, the kitchen table. It combines observation and interviewing, but in the real environment instead of a meeting room.
Think of it this way: if you want to know how someone cooks, you could ask for the recipe. But you learn far more by standing next to them and noticing that they add salt by feel and switch the oven off five minutes early because it runs hot.
The method was developed in the late 1980s by Karen Holtzblatt and other researchers. Hugh Beyer and Karen Holtzblatt described it in detail in their 1998 book “Contextual Design,” where contextual inquiry is the first step in a larger design process.
The master and apprentice model
At its core is a simple relationship: the person you observe is the master of their craft, and you take the role of the apprentice. You let them show you their work, you watch, and you ask when something isn’t clear, for example “Why did you just double-check that?” You don’t judge, and you don’t suggest solutions.
Four principles round it out:
- Context: You go where the work happens and observe real tasks instead of listening to stories about them.
- Partnership: You build understanding together with the person, alternating between watching and talking.
- Interpretation: You share your interpretations on the spot and let the person confirm or correct them.
- Focus: You keep track of what matters for your project without clinging to a rigid script.
A session typically lasts around two hours. Afterwards, the team analyzes the notes together, often with an affinity diagram, where observations on sticky notes are grouped by theme. To learn what else UX researchers do, read What Does a UX Researcher Do?
An example
Here’s an example: a software team is asked to improve the job management tool for a trades business. Before any field research, based on a workshop with management, the team plans an elaborate desktop interface with lots of filters.
After three mornings on site, it becomes clear that the staff look at jobs almost exclusively on their phones in the van, often while wearing work gloves. So the team builds a lean mobile view with large buttons and moves the filters into a separate area for the office.
In practice
- Plan for time and access. The method takes effort: travel, on-site appointments and analysis cost much more than a remote interview.
- Stay in the apprentice role. Let people work and ask questions at the right moment instead of steering the conversation or debating solutions.
- Analyze as a team. Shared analysis sessions reveal patterns and give you a solid basis for a persona or a journey map.
Related terms
User Research, Persona, Journey Map, Human-Centered Design