Ethnographic Research Template for User Research

[Contextual inquiry](/templates/contextual-inquiry-template) is a structured interview conducted while the user performs their task. The researcher asks questions throughout. Ethnographic research is more observational. The researcher watches with minimal interruption and asks clarifying questions only at natural pauses. Contextual inquiry gives you deeper explanations of specific behaviors. Ethnographic observation gives you a broader view of the workflow, environment, and social dynamics. Many product teams use both methods together.

Partially. Screen-sharing sessions where users work on their normal tasks while you observe capture the digital workflow. You miss the physical environment, interruptions, paper artifacts, and social interactions. Remote observation is a reasonable compromise when travel is not feasible, but it captures about 60% of what an in-person visit reveals. For remote sessions, ask the user to keep their camera on and describe their physical environment at the start.

Four to eight participants across at least two user segments is the practical range. Pattern saturation (the point where new visits stop revealing novel insights) typically occurs around visit 5-6 for a well-defined segment. If your users work in very different environments (e.g., corporate offices versus field locations), plan for 4 visits per environment type.

This happens. Users sometimes use unauthorized tools, skip compliance steps, or have workarounds their manager does not know about. Treat everything you observe as confidential research data. Do not report individual behaviors to the participant's manager. Focus your findings on systemic patterns ("schedulers maintain informal provider rules outside the system") rather than individual actions ("Sarah uses a personal spreadsheet that violates data policy").

Frame it in terms of risk reduction. "We are about to invest $200K in a scheduling redesign. Two days of field observation will tell us whether our design assumptions match reality. If they do not, we save months of rework." Pair this with a specific example from past projects where untested assumptions led to wasted effort. Decision-makers respond to concrete cost-of-failure calculations. Use the [RICE framework](/frameworks/rice-framework) to quantify the value of the research as an initiative. ---