Ethnography and Real-World Product Discovery: What Observation Reveals

Ethnography brings innovation researchers closer to everyday practice. Instead of asking people only what they would do in an imagined situation, researchers observe how a task unfolds in a natural setting and ask careful questions about the reasons behind it. The resulting observations may reveal workarounds, constraints and social expectations that a survey misses.

Observation is not mind reading

A researcher who sees a participant repeat a step can describe the behavior, but cannot know the motive without asking. Teams need to distinguish notes about actions from interpretations. Good fieldwork also reflects on the observer’s influence, permissions, privacy and the limits of a small sample.

Observation is most useful when connected to a decision: which service interaction confuses people, which administrative step creates delays, or which product requirement is being misunderstood? Clear questions help prevent an attractive anecdote from becoming an unsupported general claim.

Turn observations into testable design options

After fieldwork, organize observations into recurring patterns while preserving exceptions. Create a small number of alternative design concepts and ask whether they address the observed difficulty. A clickable model or paper role-play can show whether the proposed change is understandable. A second observation round can then test the revised workflow.

The IDEO.org Design Kit methods collection describes participatory ways to research and develop ideas. Combining observational methods with visible prototypes allows teams to discuss their reasoning with the people most affected by a change.

Ethics and practical limits

Research participants should understand the activity and its purpose. Teams must respect confidentiality, avoid collecting unnecessary sensitive data and describe the setting accurately. A finding from a particular workplace cannot automatically be treated as a universal rule. Responsible reporting explains what was observed and what remains uncertain.

Ethnography does not replace quantitative measurement, nor does measurement replace observation. Both methods can contribute to an innovation process when the team is explicit about what each one can establish.

Plan fieldwork around a concrete activity

Begin with the work people are already trying to complete. Map the practical setting, including objects, interruptions, handoffs and informal workarounds. Ask permission to observe, clarify how notes will be stored and avoid capturing more personal information than the purpose requires. In some settings, the appropriate method may be a carefully facilitated interview rather than direct observation. The research plan should explain why the selected approach is proportionate.

Capture an observation in plain language: a participant changed tools during a task, paused to ask a colleague, or relied on a handwritten reminder. Then record possible interpretations separately. The behavior could reflect confusing software, a policy requirement, or a locally efficient habit. Follow-up questions and additional observations help distinguish these explanations.

Translate findings into a design brief

Grouping repeated observations into themes is useful, but it can erase the distinctive circumstances that made an observation important. Preserve examples and counterexamples. Describe the practical problem, the people affected, the environmental constraint and the uncertainty that remains. A design brief should specify how a proposed change could be evaluated rather than jumping immediately from an anecdote to a finished solution.

Observation works especially well alongside rapid prototypes. A researcher can show a revised process to participants, ask them to attempt a task and observe whether the earlier difficulty has changed. Repeating the cycle allows the team to improve an idea without claiming that the first set of field notes provided a definitive answer for every user or setting.

What observation can reveal that interviews miss

People often describe their routines in terms of the official process, even when daily work relies on shortcuts and improvised support. Observation helps uncover these gaps. A researcher may discover that someone alternates between a digital form and a paper note, asks a coworker for help, or delays a task until a particular device is available. Such details show how a product operates within a larger system of tools and relationships.

Yet an observation is only a starting point. Its meaning should be checked with participants, and the researcher should distinguish repeated patterns from isolated moments. The presence of a workaround does not always mean the official process is defective; it may reflect a temporary event, a safety practice, or a choice worth preserving.

Build an ethical fieldwork protocol

Explain the research purpose, how notes will be used, and who will see them. Obtain appropriate consent and allow participants to decline sensitive questions. Avoid recording credentials, private customer data or identifying material that is unnecessary for the design decision. When observation occurs in a workplace or public service, consider the power relationship between researchers and participants and the implications of management receiving the findings.

Researchers should prepare a consistent observation form with separate fields for actions, context, direct participant statements, and provisional interpretations. That distinction reduces the risk of turning an observer’s guess into a reported fact. Anonymize notes as early as practical and delete information that does not serve the research purpose.

Turn field notes into a testable product response

After fieldwork, group observations by the specific activity they affect. Look for recurring delays, handoffs, points of uncertainty, and strategies people already use successfully. Discuss alternative explanations before deciding that a new feature is needed. A training update, clearer instruction or revised policy may be a better intervention than another screen.

Design a small experiment that allows participants to try the proposed response under realistic constraints. Compare the new experience with the original observations and document side effects. Product discovery becomes credible when researchers can show the chain from observed behaviour to the decision they made, rather than presenting a confident persona or journey map with no evidentiary trail.

Share findings without flattening people into personas

Researchers often translate field observations into journey maps, themes and representative profiles. These can support communication, but they can also remove details that explain why a workaround exists. A well-documented synthesis should preserve examples, note the limits of each pattern, and avoid assigning a single motivation to everyone who behaves similarly. People may do the same action for very different reasons.

Invite members of the product team to examine anonymized observations and consider alternative explanations. A repeated delay might arise from unclear software, missing authority, equipment availability or a policy that requires additional checking. Different causes lead to different interventions. A new feature should not be the default answer simply because the research is being conducted by designers.

After a change is tested, return to the original activity and observe whether the problem has genuinely improved. The most responsible field research is iterative: it listens, proposes, checks and remains open to correction. Its strength lies in carefully described evidence, not in the novelty of a presentation artifact.

When sharing findings with stakeholders, include a small set of anonymized moments that illustrate the activity rather than presenting people as stereotypes. Explain what the researcher observed directly and what participants later clarified. A short account of a single interrupted task can reveal more about a workflow than a polished demographic profile. Explain how often a behaviour was observed and why its consequences matter even when it is unusual.

Finally, include a plan for checking the proposed change with the same population or setting. Product discovery is not complete when a team has named a need; its value is demonstrated through an intervention that people can actually use, with results reported faithfully and limitations kept visible.

Further reading: IDEO.org Design Kit – Methods; OECD / Eurostat – Oslo Manual 2018.