Ethnographic research: studying people where they actually are

A workflow may be shaped by things that never come up during a video interview. Maybe the employee is constantly interrupted. Maybe the software runs on a shared computer. Maybe they keep a printed reference sheet next to the monitor or copy information into a spreadsheet because the official system does not support what they need.

Take those details away, and you may be studying a different version of the work.

That makes ethnographic research particularly useful when your research question is less about what people think and more about what they actually do, where they do it, and what influences that behavior.

You go where the behavior happens.

That might be an office, warehouse, hospital, retail store, factory floor, classroom, or someone's home. The environment is treated as part of the experience rather than background noise to remove from the study.

Interviews depend heavily on what participants can remember and explain. Ethnographic research adds direct observation. You watch what happens and use questions to clarify what you see.

That distinction matters because people do not always notice every step in a familiar process. Experienced users may move through work almost automatically, while workarounds may feel so normal that they do not think to mention them.

Traditional ethnography involves prolonged immersion. Product research is usually much shorter, but time still matters.

The goal is to observe enough of the real situation to understand the surrounding context rather than dropping in for a few minutes and treating the resulting snapshot as representative of the entire experience.

Ask someone who has performed the same task for years to explain every step and you may get a simplified version.

That does not mean the participant is unreliable. Familiar behaviors often require less conscious thought, making some details difficult to recall or articulate. Observation lets you see those details directly.

A participant might say, “Then I submit the order,” while observation reveals that before submitting it, they check a paper list, message a colleague, open another system, and compare two numbers. Those steps may be essential to understanding the actual workflow.

Workarounds are especially easy to miss in interviews.

Someone may never tell you about the spreadsheet they maintain beside your product because, from their perspective, it is simply part of doing the job. Watch the work happen and suddenly the spreadsheet becomes visible.

That can expose a gap between what the product officially supports and what customers actually need to accomplish.

The environment itself may affect how someone uses a product.

A warehouse employee may be wearing gloves. A nurse may be interrupted repeatedly. Someone working from home may have a small laptop screen rather than the two-monitor setup your product team uses.

These conditions are difficult to recreate in a lab and easy for participants to overlook when describing their experience later.

Being in the environment also gives people access to the artifacts they use every day.

Instead of asking someone to remember an example, they can pull up last week's report, show you the handwritten note they keep beside their desk, or demonstrate the workaround they use when something goes wrong.

Those moments can generate much richer evidence than asking the same person to reconstruct the experience from memory.

Contextual inquiry combines observation with questions about what the participant is doing. The researcher observes someone performing real work and asks questions to understand the decisions, tools, and behaviors they see.

It is one of the most practical ways for product teams to bring ethnographic principles into their research without conducting a long-term field study. For the full process, see our guide to contextual inquiry.

Field observation puts more emphasis on watching than questioning.

The researcher observes people in their normal environment while trying to minimize disruption. This can be useful when interruptions would interfere with the activity or when you want to understand the rhythm of an environment rather than a single task.

For example, watching a customer service team for several hours might reveal when interruptions occur, how often employees switch systems, and who they turn to when they cannot find an answer.

In participant observation, the researcher takes part in the activity rather than only watching it. This can provide a different understanding of physical, procedural, or cognitive demands.

Trying to complete a process yourself may reveal why a seemingly minor inconvenience becomes frustrating when it happens dozens of times during a shift.

Participation is not appropriate in every setting, particularly where safety, privacy, or specialized training is involved. But where it is possible, it can add another layer of context.

Shadowing means following a participant through part of their normal day or workflow. Instead of focusing narrowly on one task, you observe how their responsibilities connect.

This can be particularly useful for understanding handoffs between people, transitions between tools, interruptions, and the difference between an official process and what happens in practice.

Diary studies are not ethnography in the strictest sense because the researcher is not continuously present. But they can answer some of the same questions.

Participants document experiences over days or weeks, which can help researchers study behaviors that happen unpredictably, infrequently, or in places where direct observation would be difficult.

Diary studies are particularly useful when you care about context over time but cannot realistically be there every time the behavior occurs.

Not every meaningful environment is physical. Digital ethnography studies behavior and culture in online spaces such as communities, forums, social platforms, and other digital environments.

For product teams, these spaces can show how people discuss problems, exchange advice, develop workarounds, and talk about products when a researcher is not actively asking the questions.

As with any observational research, researchers still need to consider privacy, consent, and the expectations people have within a particular digital space.

Ethnographic research is less useful when another method answers the question more directly. If you need to evaluate whether people can complete a particular flow in a design, usability testing is likely a better fit.

If you need to estimate how common a behavior or opinion is across a population, you need quantitative research rather than a small observational study. And if the behavior is already directly observable through product data, additional field research may not be the first method you need.

The method should follow the question, not the other way around. Our UX research methods guide can help you compare your options.

“Understand our customers better” is too broad.

Instead, identify the behavior or situation you need to investigate, like “How do warehouse supervisors handle a stock discrepancy during a shift?” That question tells you who to observe, what activity matters, and what circumstances need to be present.

A focused question also makes it easier to decide whether ethnographic research is actually the right method.

For field research, demographics alone rarely tell you whether someone is the right participant. Recruit people who actually experience the situation you need to observe.

If you are researching month-end reporting, for example, you need participants who are responsible for that process and a visit scheduled when the work actually happens.

A thoughtful screener survey can help you recruit for relevant behaviors, responsibilities, experience, and circumstances rather than relying on broad demographic characteristics. Great Question's research panel can also help teams recruit from their own customers and manage ongoing research participation.

Convenience should not determine the situation you study.

If the difficult part of the job happens during shift change, month end, or the morning rush, observing the quiet period may give you an incomplete picture. Try to schedule the research around the conditions most relevant to your question.

That does not mean deliberately manufacturing chaos. It means making sure the experience you observe is reasonably representative of the behavior you are trying to understand.

Give participants enough room to behave naturally. When you do ask questions, anchor them in something you actually observed.

Instead of “Why is this screen confusing?” try “I noticed you went back to that screen twice. What were you checking?” The second question does not assume there is a usability problem. It asks the participant to explain observable behavior.

If you need a more structured observation-and-question format, contextual inquiry may be the better specific method.

This is one of the most useful habits in field research. Record what happened separately from what you think it means. For example:

With permission, capture the physical and digital artifacts surrounding the work. That might include:

Do not rely on memory to reconstruct a field visit days later.

Soon after each session, review your notes, expand shorthand, identify open questions, and document initial observations while you still remember the context surrounding them.

If several researchers attended, compare notes. Differences in what each person noticed can themselves reveal assumptions worth examining.

For high-stakes decisions, a small ethnographic study may generate hypotheses that need to be tested with additional qualitative or quantitative research.

Decide how these situations will be handled before entering the field.

De-identification also requires more than removing someone's name. In a small organization, a job title, team, location, or description of responsibilities may be enough to identify a participant.

The goal is not simply to obtain consent once. It is to respect the boundaries of that consent throughout collection, analysis, and reporting.

Pay particular attention to workarounds. A workaround tells you that someone encountered a problem important enough to solve for themselves. It does not automatically tell you what your product should build, but it can reveal an unmet need worth investigating.

Variation matters too. If people with the same role complete the same task in completely different ways, that difference may be as important as the behaviors they share.

Store the resulting evidence somewhere people can find it again. A shared research repository can keep field observations connected to interviews, surveys, usability studies, and other customer research rather than leaving each project in a separate folder. Our UX research repository guide covers how to structure that evidence so future teams can reuse it.

Great Question's AI research capabilities can help teams analyze qualitative research while keeping findings connected to the underlying evidence.

But much of the value of ethnographic research may never appear in a transcript. The physical layout of a workspace, a participant's hesitation, a handwritten note beside a monitor, or the repeated movement between two devices can be central to the finding.

AI can help researchers process the material they capture. It should not be treated as a substitute for noticing the environment, understanding context, or deciding what the observations mean.