What Is Contextual Inquiry?

Watching what people do, not just hearing what they say

Contextual inquiry is a research method that combines observation with interviewing, carried out in the place where the activity actually happens: someone's workplace, their home, a clinic, a warehouse floor, wherever your product or service gets used in real life. Instead of bringing someone to you and asking them to recall how they do something, you go to them and watch them do it, asking questions as it happens.

The approach is sometimes described as a "master and apprentice" relationship. The participant is the expert in their own work or life; the researcher is there to learn, asking questions like "what are you doing now?", "why did you do it that way?", or "what would you normally do at this point?" as the activity unfolds, rather than reconstructing it from memory afterwards.

How this differs from an interview

A standard interview relies on recall: you ask someone to describe how they do something, and they tell you, from memory, in a conversation that is usually disconnected from the moment the activity actually happens. This works well for opinions, attitudes, and feelings. It works less well for process and behaviour, because people are surprisingly bad at accurately describing their own habits.

This is not because people are trying to mislead you. Much of how we actually carry out familiar tasks happens automatically, the small workarounds, the steps we skip, the order we actually do things in (as opposed to the order we would describe if asked). A workaround someone has used every day for two years has often become so normal that they no longer think to mention it, or do not consciously register that it is a workaround at all. Watching the activity happen surfaces these details directly, without relying on someone noticing and remembering to report them.

How this differs from usability testing

Usability testing and contextual inquiry can look superficially similar, both involve watching someone use something, but the setting and the task are different in ways that matter. In a usability testing session, the researcher sets the task ("please find and book an appointment"), the environment is controlled (often a quiet room or a remote video call), and the participant is consciously aware they are being tested.

In contextual inquiry, the task is whatever the person would normally be doing, the environment is their real one, with all its real interruptions, other people, background noise, and competing demands, and the goal is to understand the work as it actually happens, not how it performs when someone is paying close attention to it. A clinical system that works fine in a quiet usability testing room can behave very differently when a nurse is using it between two other tasks, with a patient in front of them and a phone ringing. Contextual inquiry is built to surface that difference; usability testing, on its own, generally is not. See our usability testing page for more on the lab-style approach, and how the two can complement each other.

When contextual inquiry earns its cost

Complex workflows with many steps or systems. When a task involves moving between several tools, screens, or pieces of paper, often switching between them in ways that are not obvious from looking at any single system, observing the whole sequence in context reveals friction points that would never come up in a conversation about any one part of it.

Environments that shape behaviour. Clinical settings, people's homes, shop floors, vehicles: anywhere the physical environment, interruptions, or other people materially affect how a task gets done. A form that is easy to fill in while sitting at a desk may be genuinely difficult to use standing up, holding other things, or with someone watching.

Workarounds and "shadow processes". If you suspect people are not using your product or process the way it was designed, perhaps they have built their own spreadsheet alongside your system, or print things out because they do not trust the digital version, contextual inquiry is one of the few methods reliably able to surface this, because the workaround is part of the environment you are observing.

Early-stage discovery for something genuinely new. When you are designing for a context your team does not have first-hand experience of, understanding how people currently get by without your product, what tools they cobble together, what they value, what frustrates them, gives you a far richer starting point than starting from assumptions and testing them later. This sits within the broader discovery toolkit covered on our in-depth user research page, alongside extended ethnographic research for studies that need observation over days or weeks rather than single sessions.

What a contextual inquiry session actually looks like

A typical session takes place where the work happens and lasts one to two hours, sometimes longer for complex roles. The researcher asks the participant to carry on with their normal activities as much as possible, observing quietly and noting what happens, then asking questions at natural pauses rather than interrupting mid-task: "what made you choose that option?", "is that the order you'd normally do these in?", "has that always worked that way, or did you find another way around it at some point?"

The output is not a transcript of answers to a fixed question list, but a rich picture of the actual workflow: the steps people take, the tools and artefacts involved (including the unofficial ones), the points where things go smoothly, and the points where something gets worked around, skipped, or causes visible friction. This is usually synthesised into journey maps, workflow diagrams, or a set of findings that feed directly into design or service improvements.

Where this fits alongside other methods

Contextual inquiry is qualitative, in-depth research, so it sits alongside (and is sometimes part of) the broader question of whether qualitative or quantitative research is the right starting point. If the question is "how do people actually do this, in the messy reality of their day", contextual inquiry is hard to beat. If the question is "does this specific design work", a more controlled usability session is usually faster and more focused. And if the question is "how widespread is this problem across our whole user base", that points towards quantitative research, often after a smaller contextual study has told you what to measure.

If you are weighing up whether your project needs this level of in-context depth, tell us about the workflow or environment you are trying to understand. We will help you scope the right balance of contextual research, usability testing, and broader validation for your timeline and budget.