What is contextual inquiry in UX?
Contextual inquiry in UX is a research method where you observe and question users in their own environment while they do real work with a product.
also calledfield study · contextual interview · ethnographic observation
People are surprisingly bad at describing what they do. Ask a nurse how she updates a patient chart and she will give you the tidy version. Stand next to her during a night shift and you will see the sticky notes, the workarounds and the interruptions that the tidy version leaves out. Contextual inquiry is the practice of standing next to her.
- Contextual inquiry means observing and asking questions while users do real work in their own setting.
- It uncovers workarounds, tools and interruptions that people forget to mention in interviews.
- Treat the user as the expert and yourself as the learner.
- Use it early in a project, not to polish interface details.
How it differs from a normal interview
In a standard interview, the participant sits in a quiet room and recalls. In contextual inquiry, you go to where the work happens: the office, the kitchen, the warehouse, the commute. You watch the person do real tasks and ask questions as they go.
That changes what you learn. You see the physical setting, the tools nobody mentioned, the colleagues who interrupt, and the small hacks people invented because the official system did not fit. Memory edits those things out. Observation does not.
The master and apprentice idea
A classic way to frame the session is that the user is the master and you are the apprentice. They know the work, you are there to learn it. So you let them lead, you ask "Why did you do that?" rather than "Do you always do it this way?", and you check your understanding by saying back what you saw.
This stance keeps you from pushing your own assumptions. It also puts people at ease, because they are the expert in the room, not the subject of a test.
Running a session step by step
A simple structure works well:
- Agree on the focus with your team: which tasks or workflows matter.
- Recruit people who really do that work, and ask permission to observe in their space.
- Start with a short chat about their role, then move to watching them work.
- Take notes on actions, objects, interruptions and words they use. Ask for clarification in the moment.
- Near the end, summarize what you saw and let them correct you.
- Debrief with your team the same day while details are fresh.
What goes wrong
The biggest trap is turning into a salesperson or a teacher. If you start explaining how your product could fix their problem, you stop observing. Another is steering too much. Interrupting every few seconds breaks the natural flow of work and you end up with a staged demo.
It also takes time and access. Some environments, such as hospitals or factories, have privacy and safety rules, so plan permissions early. Keep sessions small and focused. Four or five good visits usually reveal more than a pile of shallow ones.
When to choose it
Use it when the work is complex, physical, collaborative or full of hidden steps. It shines at the start of a project, when you are still trying to understand what the real problem is.
Skip it when you only need to check whether a button label is clear. A short usability test does that faster and cheaper. Contextual inquiry is for understanding situations, not for polishing screens.
Contextual inquiry: your questions, answered
What is contextual inquiry in simple terms?
It is user research where you go to the person's real workplace or home and watch them do actual tasks, asking questions along the way. The goal is to understand what they do and why, not just what they say they do.
How long does a contextual inquiry session take?
Most sessions run between one and three hours, depending on the work being observed. Some tasks, like a full shift, may need longer. Plan enough time for a short introduction, the observation itself and a closing recap with the participant.
How many participants do you need for contextual inquiry?
Often four to eight, depending on how varied the users and settings are. The number matters less than choosing people who represent different roles or situations. Stop when new visits no longer reveal new patterns.
What is the difference between contextual inquiry and ethnography?
Ethnography is a long, deep immersion in a culture, sometimes lasting months. Contextual inquiry borrows the same spirit but is shorter and focused on specific tasks that inform a product decision.
Can contextual inquiry be done remotely?
Partly. With screen sharing or a participant filming their workspace you can observe much of the work, but you lose the surrounding environment. In-person visits still give the richest picture when they are possible.
More quick answers
What are the four principles of contextual inquiry?
They are commonly given as context, partnership, interpretation and focus: observe in the real setting, work as master and apprentice, share your interpretations for correction, and keep a clear research focus.
Is contextual inquiry qualitative or quantitative?
Qualitative. It gives rich detail about behavior and context rather than numbers.
What is the difference between contextual inquiry and a user interview?
An interview relies on what people recall and report. Contextual inquiry adds observation in the real environment, so you catch behavior people would not think to mention.
What do you do with contextual inquiry data?
Teams usually cluster observations into themes, often with an affinity map, and turn them into workflows, personas or opportunity areas.
What is a field study in UX?
A field study is research done in the user's natural environment. Contextual inquiry is one specific, structured kind of field study.
User research in UX is the practice of studying people who use or might use a product, to understand their needs and behavior so design rests on evidence.
A user interview in UX is a one-on-one conversation where a researcher asks people about their goals, habits and frustrations to understand their real needs.
A diary study in UX is a research method where participants record their own experiences, tasks or thoughts over days or weeks, in real contexts.
Task analysis in UX is the study of how people complete a goal, broken down into the individual steps, decisions and tools involved from start to finish.
Qualitative user research is the study of people's behavior, needs and motivations through observation and conversation, to learn why they act as they do.
An affinity map in UX is a visual grouping of research notes, quotes and observations into themes so patterns across many users become easy to see.
Found this useful? A GitHub star helps other designers find it.