Ethnography in UX: Observing Users in Their Real Environment

What is ethnography, and where does it come from?

In the social sciences, ethnography implies immersion in a culture or community. In UX, the term is used more loosely. Nielsen Norman Group’s glossary notes that in UX “ethnographic study” is used as a synonym for “field study”: a qualitative method for observing users in their natural habitat.

NN/g describes ethnography as complete immersion in a person’s or group’s natural setting for a sustained period, sometimes living as a member of the group. It gives insight into mental models and social situations, and it is especially helpful when your audience lives in a culture or environment different from yours.

Why does this matter for a junior designer?

Because it is one of the slowest and most expensive methods, which makes it easy to promise without delivering. Saying “we did ethnography” after visiting two customers for an afternoon confuses a visit with an immersion. Understanding the difference protects you from promising what cannot be delivered, and lets you propose the level of observation the project really needs.

Ethnography also teaches you to look. A designer who has watched someone work in their real environment sees details a lab screen never shows: how they improvise, what they ignore, what they do with the papers around them.

Where does it sit among field methods?

NN/g distinguishes four types of field study, each with a different goal:

Watching and asking are not opposites: NN/g places each type at a different point between the two extremes.

How does it differ from contextual inquiry and interviews?

For NN/g, contextual inquiry is a more bounded type of ethnographic field study: the researcher watches the user perform their task in their normal environment and asks why when something is unclear. It uses a small sample, with sessions ranging from an hour or two to several days, and is mostly applied in the early discovery of a feature or product.

Ethnography goes further: total, sustained immersion, focused on the relationships and norms of the group, not just on one task.

Compared with an interview, the difference is memory. In an interview, the person recounts what they remember of their process. NN/g explains that by observing work live, the researcher captures details the person no longer notices because they have become habitual and invisible. The article on contextual inquiry goes deeper into that technique, and the one on user interviews covers the conversational alternative.

When is it worth doing?

IxDF recommends ethnography for early discovery, when depth matters more than breadth, and for uncovering why behaviors happen. It makes sense when:

• The project is new and the team does not yet understand the user’s context.
• The audience’s culture is different from the team’s, through language, trade, region, or circumstance.
• Behavior depends on the environment, such as fieldwork, a hospital, or a physical store.
• Informal norms need to be understood, the ones nobody writes down but that shape how the product gets used.

When should you NOT do it?

According to IxDF, ethnography prioritizes depth over volume and is slow and expensive. Its limits follow from that:

• When large numbers are needed. It gives depth with a few cases, not statistics.
• When the budget or timeline is tight. NN/g notes that field methods have not become cheaper at the same rate as other methods and can be challenging to facilitate.
• When the population or setting is hard to access. IxDF points to the difficulty of gaining access to the culture you want to study.
• When you cannot protect the privacy of the people observed. IxDF asks researchers to take steps to protect their identity and personal data.

For research with little logistics, the article on remote research shows what can be observed without going on site.

Example

Illustrative example: a team designs an app for nurses in a public hospital.

• Session: over two shifts, a researcher accompanies two nurses, with the hospital’s permission, without intervening in patient care.
• Finding: the nurses use their phones only at the start and end of the shift. During the shift they write on paper, because the system is slow to load in the wards. The paper notes are entered into the system at the end.
• Consequence: the app cannot ask for more steps during care. It must accept the initial load and let the information be completed at the end of the shift.

An interview might not have surfaced that detail, because the nurses did not consider it a problem: it was part of their work. Observing habits that have become invisible is exactly what fieldwork adds.

To gather and summarize field notes, the article on AI interview synthesis can help, as long as you review the original observations.

Common mistakes

• Calling a one-afternoon visit ethnography and promising immersion-level conclusions.
• Interrupting with so many questions that the participant’s workflow changes.
• Allowing side chatter among observers during the session.
• Steering questions or interpretation toward what the team wants to find.
• Bringing observers who make the participant feel self-conscious.
• Observing without protecting the privacy of the people in the setting.

Sources

• Nielsen Norman Group, Research Methods Glossary
• Nielsen Norman Group, Field Studies
• Nielsen Norman Group, Contextual Inquiry
• IxDF, Ethnography