← Blog

Field research methods: observing users in the wild

20 November 2026 · 5 min read

Illustration of field research observation

Ask someone how often they descale their coffee machine and you will get a guess dressed up as a fact. Watch them make coffee for a week and you will learn the truth, plus a dozen things you would never have thought to ask about. That gap, between what people say and what people do, is exactly what field research methods exist to close.

Field research means leaving the lab, the video call, and the survey behind, and observing people in the places where the behaviour actually happens: their kitchen, their clinic, their warehouse, their commute. The methods vary, but they share one conviction: context is data. This guide walks through the main field research methods, the two design choices you will face on every study, and the note-taking discipline that turns a day of watching into evidence you can stand behind.

Why field research methods earn their cost

Field work is slower and more logistically annoying than remote sessions, so it has to justify itself. It does, three ways.

First, the environment does work an interview cannot. The password on a sticky note, the printed spreadsheet taped above the till, the queue that forms at the same machine every morning: none of this surfaces when you ask people to describe their day, because to them it is invisible. It is furniture.

Second, behaviour in context is honest. Self-report smooths a week of improvisation into a tidy routine, and naturalistic observation, watching behaviour unfold where it lives rather than staging it, catches the workarounds, interruptions, and shortcuts that never make it into the telling.

Third, the field generates better questions. Half the value of a site visit is the list of things you now know to ask about in every session that follows.

The core methods on the menu: observation (watching in place), shadowing (following one person through their day), intercepts (short, in-the-moment conversations with people mid-task), and contextual inquiry (observation with questions woven in). When the behaviour you care about unfolds over weeks rather than hours, diary studies extend the same in-context logic across time.

Structured or unstructured observation

Your first design choice is how much structure to impose.

  • Unstructured observation · you arrive with a broad question and open eyes, and record whatever seems meaningful. This is the right mode early, when you do not yet know which behaviours matter. The risk is drift: with no focus you can fill a notebook and learn nothing.
  • Structured observation · you arrive with a defined framework: specific behaviours to look for, sometimes a checklist or a coding sheet, sometimes counts and timings. This is the right mode once you know what you are looking for, and it makes observations comparable across people, sites, and observers.

Most good field studies blend the two: an unstructured first visit to learn what the meaningful behaviours even are, then structured visits to see how those behaviours vary and how often they occur.

Fly on the wall or participant observation

The second choice is your own role.

Fly-on-the-wall observation minimises your influence. You watch, you do not interrupt, you do not steer. It is the closest you get to seeing the world as it runs without you in it. Be honest about the observer effect, people do behave differently when they are watched, but the effect fades faster than you might expect once you stop being novel.

Participant observation comes from anthropology: you join the activity you are studying and learn it from the inside. It trades some detachment for empathy and access, because some things you only understand by doing them. It is the beating heart of ethnographic research, and it is how researchers earn the right to interpret a way of working rather than just describe it.

Between the two sits contextual inquiry, where you watch someone work in their real environment and interrupt, respectfully, to ask why. For most product questions it is the workhorse: more efficient than pure observation, more truthful than an interview.

Note-taking discipline, the part that makes it research

Field data lives or dies in your notes. A rich day captured as "visited the depot, loads of interesting stuff" is a day wasted. The habits that hold up:

  • Separate observation from interpretation. "She typed the code three times" is data. "The code system frustrates her" is inference. Record both, but mark which is which; a two-column page does the job.
  • Timestamp as you go. Sequence and duration are often the finding, and you will not reconstruct them from memory.
  • Capture verbatims and artefacts. Exact words in quote marks, photos of the environment where permitted, copies of the forms and printouts people actually use.
  • Write up the same day. Raw jottings decay overnight. Expand them into full field notes while your memory can still fill the gaps between the lines.
  • Debrief in pairs. If two of you were there, compare notes within hours. You will catch each other's blind spots and inherit each other's questions.

Watching well

None of this is complicated, but all of it is craft. The instinct to ask has to give way to the patience to watch, and the urge to conclude has to wait for the write-up. Choose your structure deliberately, know which role you are playing, and take notes as though a sceptical colleague will read them, because one should. Do that, and a single day in the field will change how your team talks about its users for months.


People of Research is a community and newsletter for UX researchers, ethnographers, and anyone who learns more from watching people than from asking them. Join us and get the good stuff in your inbox.

Join 7,500+ researchers, free

One email a week, a global community, and events near you. No noise, just the people and ideas that matter.