IMMERSION DEPTH OVER TIME · trust → behavioural normalisation → access DAY 1 obvious outsider WEEK 1 familiarity begins WEEK 2-3 trust established MONTH 1+ full participation DEPTH brief site visit (1 day): a shallow slice vs full immersion ethnographic-research · trust takes time · context reveals what interviews cannot

Ethnographic Research

Immerse yourself in users' world before you design for it — the method that reveals what observation alone cannot.

User Research Contextual Research Discovery Research Qualitative Research Behavioural Research Cultural Research

Two sentences.

Ethnographic Research is a qualitative methodology originating in cultural anthropology — developed by researchers including Bronisław Malinowski in the early twentieth century and adapted for product and design research through IDEO's human-centred design practice and the broader field of design ethnography. A researcher embeds themselves in users' natural environments for an extended period, observing behaviour, participating in activities, conducting informal conversations, and building the kind of trust and familiarity that reveals the social norms, cultural values, and contextual factors that shape how people actually behave — rather than how they report behaving in an interview or how they behave in a laboratory. For product designers, ethnographic research addresses the most significant limitation of all other research methods: the gap between what people say they do and what they actually do.

The method's core principle is that human behaviour is inseparable from its context — the physical environment, the social relationships, the cultural norms, the historical background, and the material conditions are not incidental details but constitutive factors without which the behaviour cannot be understood or designed for accurately. A healthcare application designed without ethnographic understanding of how nurses actually move through a ward, communicate with colleagues, and manage cognitive load across a shift will solve the wrong problems regardless of how carefully it was designed from interviews alone; an agricultural product designed without fieldwork in the communities it is designed for will embed assumptions about literacy, connectivity, device access, and social decision-making that do not reflect the reality it is trying to serve.

Apply this when…

Designing for users in healthcare, agriculture, education, humanitarian, or community contexts where the design team's background is significantly different from the target users' lived experience
A product is intended for users in low-resource or low-connectivity environments where standard assumptions about device access, literacy, and digital fluency do not apply
The design problem involves complex social dynamics — how decisions are made within families, teams, or communities — that cannot be captured through individual interviews
Previous research has consistently produced findings that feel accurate at the surface level but do not explain user behaviour when the product is in the field
An organisation is entering a new geographic market or designing for a cultural context where local norms significantly affect product use
The design challenge involves physical environments — clinical settings, factory floors, agricultural contexts, informal settlements — where environmental factors shape behaviour in ways that desk research and remote interviews cannot reveal

When NOT to apply it

Skip it when the research timeline is shorter than 2-3 weeks — ethnographic research produces its most valuable insights from extended immersion, not brief visits. Skip it when the design team needs to evaluate a specific interface or prototype — Usability Testing is the appropriate method for that question. Skip it when the research question is about quantitative behaviour patterns at scale (analytics and surveys are more efficient), or when the design challenge is well-understood and the team needs to validate a specific direction (Concept Testing or Prototype Testing are faster).

The mechanism

Ethnographic Research works through three interdependent mechanisms. Extended presence builds the trust and familiarity that cause people to behave naturally rather than performing for an observer — the Hawthorne effect (people behaving differently when observed) diminishes significantly over time as the researcher becomes a familiar presence rather than a novel one. Participation rather than pure observation generates tacit knowledge — understanding that cannot be communicated in words but that emerges from doing rather than watching. Systematic documentation across multiple contexts and interactions reveals patterns that single-session observation cannot — the researcher sees the same behaviour in different situations, talks to the same people in different moods, and observes the exceptions as well as the norms.

01
Design ethnography and IDEO's field research tradition
Design ethnography adapted the methods of academic cultural anthropology — participant observation, field notes, cultural artefact analysis, insider perspective development — to the faster-paced and more action-oriented context of product design research. IDEO's human-centred design methodology, developed in the 1980s and 1990s, made field immersion a standard component of design research for complex social challenges. The practice was further developed by researchers at Intel (whose People and Practices Research group conducted foundational ethnographic work on technology use in the home), Microsoft Research, and Xerox PARC, where ethnographic studies of photocopier use in real offices produced insights that transformed how the company understood its own products.
02
The four phases of ethnographic fieldwork
Access and entry: identifying the field site, building relationships with gatekeepers, and establishing the researcher's presence in a way that is accepted and trusted. Observation and participation: spending extended time in the field — observing behaviour, participating in relevant activities, conducting informal conversations, documenting through field notes, photographs, and audio recordings. Analysis: identifying patterns across the field notes — recurring behaviours, cultural norms, contradictions between stated values and actual behaviour, and the contextual factors that shape specific actions. Synthesis: converting the field analysis into design implications — specific insights about user needs, environmental constraints, and cultural factors that should shape the design direction.
03
The most valuable findings are the ones that contradict the brief
The most counterintuitive aspect of ethnographic research is the handling of findings that contradict the project brief or the client's assumptions. Ethnographic research consistently produces findings that the team did not expect and that stakeholders did not want to hear — that the user population uses the product very differently from how it was intended, that the assumed primary user is actually a secondary user, that the problem the product was designed to solve is less important than a different problem the field research revealed, or that a social norm in the community makes the proposed design approach culturally inappropriate. These contradictory findings are the most valuable outputs — they prevent significant misaligned investment — and they require the most careful management because they arrive late in the process and require stakeholders to reconsider commitments they have already made.
04
Theoretical saturation and finding depth
Ethnographic research quality has two primary evaluation criteria. Theoretical saturation measures whether continued fieldwork is producing new insights or whether the researcher is encountering the same patterns repeatedly — saturation indicates sufficient depth of understanding has been reached. Finding depth measures whether the insights produced address the underlying cultural and contextual mechanisms that drive behaviour, not just the surface behaviours themselves — a deep finding explains why users behave as they do, not just that they behave that way.

Ethnographic Research vs. Contextual Inquiry — different scales of immersion

Both are observational methods conducted in users' natural environments, but they differ significantly in depth and duration. Contextual Inquiry is a structured 1-2 hour interview-and-observation session with one user — fast, focused, and produces specific behavioural observations. Ethnographic Research involves weeks or months of immersion in a community or environment — slow, expansive, and produces understanding of the cultural and social systems within which behaviour occurs. Contextual Inquiry answers "how does this specific user perform this specific task in this environment?" Ethnographic Research answers "what is the cultural and social context within which any member of this community would encounter this type of task?" Choose Contextual Inquiry for time-constrained discovery with specific behavioural questions; choose Ethnographic Research when the cultural and social context is itself the unknown.

IDEO's Embrace infant warmer — the fieldwork that replaced the design brief

IDEO's work with the Stanford d.school on the Embrace infant warmer for premature babies in India provides one of the most widely cited examples of ethnographic research changing a product direction entirely. The original brief assumed the product would be used in hospitals — a low-cost incubator for under-resourced rural facilities. The design team spent several weeks conducting ethnographic fieldwork in rural Indian communities, observing maternal and infant care practices, talking with mothers and traditional birth attendants, and documenting the physical environments and social dynamics around childbirth.

The fieldwork produced a finding that contradicted the entire premise of the brief: most premature births in the target communities did not occur in hospitals, and the mothers who most needed the product would not travel to hospitals to use it. The real context of use was the home — and the real users were not hospital staff but mothers and family members with no medical training, in environments without reliable electricity. The ethnographic findings did not just modify the design — they replaced the brief entirely. The product that emerged was not a hospital incubator but a portable, electricity-free infant warmer that a mother could use at home, operated without medical training. The Embrace warmer has since been used by over 300,000 infants in 22 countries. Without the fieldwork that contradicted the original brief, the team would have designed a hospital product for a population that never reaches hospitals.

IDEO + Stanford d.school · Embrace Infant Warmer
Ethnographic fieldwork contradicted the original brief — revealing the product needed to work in homes, not hospitals
ORIGINAL BRIEF · ASSUMED CONTEXT Hospital incubator concept hospital medical staff plug-in equipment clinical environment · grid power FIELDWORK FINDING · ACTUAL CONTEXT Home context · rural community home, not hospital mother, not nurse no electricity FIELD NOTES · weeks of observation "Most premature births do not occur in hospitals — mothers in rural communities cannot travel." PRODUCT EVOLUTION: hospital incubator concept portable, electricity-free home warmer Embrace warmer · used by 300,000+ infants in 22 countries Embrace · ethnographic fieldwork contradicted the original brief · home not hospital · mother not nurse · no electricity required
Field findings replaced the design brief — and the product reached the population it was designed for

Test yourself & see real examples

No examples yet — be the first.

Spotted a product that clearly emerged from deep immersion in users' real-world context — where the design addresses social, cultural, or environmental factors that no amount of desk research would have revealed — or one that was clearly designed from assumptions about users rather than direct experience of their world? Submit what you observed. Every approved example gets attributed to you.

✓ Reviewed before publishing ✓ Your name on every example you submit ✓ Violation or fix — both welcome

Seen a product that shows real cultural and contextual understanding — or one that was clearly designed for a user who doesn't exist? Help grow the evidence base.

Where teams go wrong

Treating a one-day site visit as ethnographic research. Brief site visits produce contextual observations, not ethnographic understanding. The critical mechanisms — trust building, behavioural normalisation, pattern recognition across multiple contexts and time periods — require extended presence. A researcher who visits a field site for one day sees performed behaviour, not natural behaviour; they see the obvious, not the subtle; they see what community members want an outsider to see. Brief site visits should be described as contextual observation or field visits — using the word ethnographic implies a depth of understanding that a short visit cannot produce.
Observing without participating. Ethnographic research is participant observation — the researcher is not a passive observer but an active participant. Teams that watch without doing miss the tacit knowledge that emerges from participation. A researcher who observes farmers using a mobile agricultural app from a distance will understand less about the experience than one who spends time farming alongside them. Participation is how researchers discover the aspects of an experience that cannot be articulated or demonstrated for an observer — physical demands, divided attention across competing tasks, social pressures, moments of improvisation that never appear in formal accounts of how things work.
Focusing on product use rather than the broader context. Design teams frequently narrow their observation to moments of direct product interaction — watching how users open the app, navigate the interface, and complete tasks. This narrow focus misses the most valuable ethnographic insights, which come from understanding the broader context: what is happening immediately before and after the product interaction, what social dynamics are present, what environmental pressures are competing for attention. The most actionable findings typically come from observations that had nothing to do with the product — about how decisions are made in a household, or how information is shared within a community.
Not returning to the field after preliminary analysis. Ethnographic research is iterative — preliminary analysis in the field should generate new questions explored in subsequent sessions, not taken back to the office for synthesis. Teams that conduct a single round of fieldwork, return to the office, and synthesise without returning to the field miss the chance to test and deepen their emerging understanding. Preliminary findings that cannot be confirmed or contradicted by subsequent observations are hypotheses, not findings. The cycle of observation, preliminary analysis, and return to the field is what distinguishes ethnographic research from impressionistic observation.

Connected ideas

Ethnographic Research is the deepest contextual research method in the design toolkit. Its closest relationships are with the methods that address related questions at different time and depth scales.

The most important pairing is Ethnographic Research with genuine openness to having the design brief changed. The method's most valuable outputs are the findings that contradict the team's assumptions — observations that reveal the design problem is different from what was originally understood. Teams that conduct ethnographic research with a fixed commitment to a predetermined direction will unconsciously filter their observations to confirm what they already believe. The method produces its full value only when the team is genuinely prepared to change direction based on what the field reveals.

Run it right now

⏱ 10 minutes · Solo · No prep

The Context Audit

1. Think of the last significant design decision your team made about a product feature or user flow. Write down the assumption about user context that underpins that decision — not what users do with the interface, but where they are, who else is present, what else they are doing simultaneously, and what the social and physical environment looks like when they use the product.

2. Now write down how you know that assumption is accurate. Is it based on user interviews where users described their context? Analytics that show when they use the product? Persona documents? Or is it based on your team's intuition about what "typical" use looks like?

3. If your answer is anything other than direct observational evidence — if you have not actually seen users using the product in their natural environment — your design is built on an assumption about context that may or may not be accurate. Write down: what would you need to observe to confirm or contradict this assumption?

4. Identify one person who represents your target user who you could spend two hours with in their actual environment — not in a usability lab, not on a video call, but in the physical or social context where they would actually use the product. What would you want to observe during those two hours? This is your minimum viable ethnographic research question — the specific contextual observation that would most reduce your uncertainty about the design decision you identified in step one.

10 minutes