Field Visits / Participant Observation

What Is It

Go where your users are and watch them work. Field visits involve observing or shadowing people in their real environments where the relevant activity happens. The goal is to see what people actually do, not just what they say they do.

When to Use It

You need to better understand the physical, social, or technological context surrounding a behavior
Your team has assumptions about use that haven’t been tested against reality
You’re early in a project and need to ground the problem space in observed behavior

What You'll Learn

Field visits are best for understanding use-in-context. They tend to reveal concrete details about actual use (especially workarounds and pain points), tacit knowledge people can't easily articulate or wouldn't think to mention, and assumptions your team didn't know it had.

How to Run It

Plan

Recruit participants in the target segment. Schedule sessions when the relevant activity will actually be happening. Do enough domain homework to follow along without slowing things down.

Field

Open with a brief intro and consent. Spend the majority of time watching, not talking. Ask participants to narrate what they're doing as they do it—this surfaces reasoning that observation alone misses. Record audio or screen if possible. In your fieldnotes, log observations and flag questions for the debrief. Pay attention to sequences, tools, workarounds, interruptions, and the broader environment.

Debrief

Reserve time at the end to ask follow-up questions. Use your fieldnote observations as a guide. This is the moment to clarify surprising moments you observed but didn't want to interrupt.

Analyze

If you have access to an AI tool, input your transcript and fieldnotes for a first pass identifying key sequences, tools, and problems that arose. This is a draft to iterate from—use your direct experience from the session to refine. A productive entry point is any moment of failure, workaround, or surprise. Then look for patterns across sessions: repeated workarounds, shared pain points, and places where observed behavior diverged from what participants said or what your team assumed.

Artifacts

Fieldnotes template (research question, observations, debrief questions)
Consent form

Watch Out For

Observer effect

Participants may perform rather than work naturally; focus on building rapport early and give them time to settle.

Breaking frame

This is not an interview—avoid shifting frames into one by sticking to the idea of shadowing or the roles of expert and novice.