A warehouse application may assign each worker a task, yet the work gets done through conversations, favours and local knowledge that never enter the system. An ethnographic study asks how that setting operates, including the meanings and relationships that make its practices understandable to the people involved.

Ethnographic research develops a contextual account of a group, practice or social world through engagement with it. Observation and participation are often central, alongside conversations, documents and artefacts. The purpose reaches beyond identifying isolated usability problems to understanding how an activity fits into everyday life.

Study the practice in its setting

In the fictional warehouse example, a delayed update might make sense once the researcher understands that staff wait for a colleague to confirm a physical handover. Looking only at the screen could turn a coordination practice into an apparent failure to use the software correctly.

The National Centre for Research Methods’ discussion of ethnography describes the value of engagement with social settings. For product research, this means allowing the investigation to include the surrounding work rather than assuming the product defines the boundaries of the problem.

Fieldwork may be focused or extended, depending on the question and access. Duration alone does not determine quality, but a brief visit supports a narrower account than sustained engagement across changing circumstances. Describe what was actually done rather than using “ethnography” as a more impressive name for any contextual interview.

Attend to relationships and interpretation

Access affects what the researcher can see. Being introduced by management may shape what staff feel able to discuss; working alongside one role may offer limited insight into another. Keep track of those relationships and how they influence the developing account.

Participant observation can help the researcher learn through taking part, while interviews and artefacts provide other perspectives. Compare them carefully. An official procedure, a participant’s explanation and an observed shortcut may each express a different part of how the organisation works.

Record enough context to support interpretation, including your own role and assumptions. Seek examples that complicate a simple story, and avoid describing a group as if all its members share one view or practice.

Carry understanding into design carefully

Ethnographic findings can challenge the problem a team thought it was solving. The warehouse may need better coordination between roles rather than more reminders to update the system. That insight can guide task analysis, service design or a focused prototype study.

The findings do not require a population percentage to be meaningful, but claims beyond the studied setting need a reasoned account of where they may transfer. Distinguish observations of this context from assumptions about all workplaces or users.

Report in a way that protects relationships as well as personal details. The practical value of access depends on trust, and a rich account should help readers understand the setting without exposing people who contributed their time and experience.