Ask a room of product people what ethnographic research is and you will hear everything from "interviews, but in someone's house" to "that thing anthropologists do for a year". Neither is quite right. Ethnography means studying people in their own context, on their own terms, and it has earned its place in product work because of one stubborn truth: what people do in their real environment is rarely what they tell you in a lab.
This guide covers what ethnographic research looks like when it is applied to products and services, when it beats an interview study, and how to run a lightweight version without a film crew or a six month timeline.
What ethnographic research means in product work
Classic ethnography comes from anthropology: a researcher immerses themselves in a community for months or years, participates in its daily life, and writes a careful account of how it works from the inside. Product teams borrowed the mindset and shrank the timescale. Design ethnography, as this applied version is often called, keeps the essentials: you go to where the behaviour lives, you observe more than you ask, and you treat the participant as the expert on their own world.
In practice, that might mean spending a day on a hospital ward watching how nurses handle handovers, shadowing a delivery driver through a shift, or sitting in a family kitchen while the weekly shop gets planned. You are not testing a design. You are learning the world your design will have to survive in: the interruptions, the workarounds, the sticky notes on the monitor, the colleague people ask instead of opening the help centre.
That last list is the point. The most valuable findings from observational research are usually things nobody would have thought to mention in an interview, because to the person doing them they are not interesting. They are just how things are.
Context is exactly what the lab removes
A lab session, or a remote moderated call, is a controlled environment: a quiet room, a single task, your full attention on the participant and theirs on you. That control is what makes usability testing powerful, and it is also precisely what makes it blind to context.
In the real setting, the task you care about is squeezed between six others. The user is interrupted twice a minute. The lighting is poor, the gloves make the touchscreen useless, and the "quick" workflow happens on a phone balanced on a shelf. None of this shows up in a lab, and all of it decides whether your product gets used at all.
Neither setting is wrong; they answer different questions. The lab tells you whether someone can complete a flow. The field tells you whether that flow fits a life.
When ethnography beats interviews
Interviews are faster and cheaper, so the practical question is when observation justifies the extra effort. Reach for the ethnographic end of the spectrum when:
- The behaviour is habitual. People cannot describe what they no longer notice. Ask someone how they use their calendar and you get a tidy story; watch them and you see the real system, held together by habit and sticky tape.
- The environment shapes the task. Physical constraints, noise, shared devices, patchy connectivity: if context matters to the outcome, you have to see the context.
- You are new to the domain. Entering healthcare, logistics, or a trading floor, a few days of observation buys you the vocabulary and the credibility that every later interview will depend on.
- The say-do gap is expensive. When a wrong assumption costs you a quarter of roadmap, watching behaviour beats trusting recollection.
If you are weighing observation against other options, our guide to choosing a UX research method places field studies in the wider map.
A lightweight version you can actually run
You do not need a grant and a year in the field. A useful design ethnography can be a handful of half day visits:
- Pick one behaviour in one place. "How pharmacists handle prescription queries at the counter" beats "understand pharmacies".
- Recruit three to five sites or participants. Depth per visit matters more than volume here.
- Observe first, ask later. Spend the first stretch just watching and noting. Save questions for natural pauses, and favour "what just happened there?" over "why do you do it that way?", which invites a rehearsed answer.
- Collect artefacts. Photograph the sticky notes, the printed cheat sheets, the taped-over button. A workaround is an unmet need wearing overalls.
- Debrief the same day. Write up while it is fresh. A day later, half the texture is gone.
Then treat what you gathered like any rich qualitative data set, thematic analysis works well, and share it with photos and stories rather than bullet points alone. A single image of the workaround wall often does more for a roadmap conversation than a deck of charts.
Seeing what people cannot tell you
At its heart, ethnographic work is a kind of humility: accepting that people are experts at living their lives but not at describing them, and that your assumptions about a context are usually wrong in ways you cannot predict from a desk. So go and watch. You will come back with fewer numbers than a survey would give you, and more understanding than a hundred surveys could.
People of Research is a community and newsletter for UX researchers, ethnographers, and everyone who believes the best insight comes from watching real people in real contexts. Join us and get the good stuff in your inbox.