On ethnography, lived practice, and why product research gets better when it studies worlds instead of only users
Most product research is optimized for explanation at the level of the individual user. What do they want? What do they struggle with? What do they think of the concept? Those are good questions. They are not the whole job.
A lot of important product behavior is not fully visible in an interview, because it lives in routine, habit, environment, relationships, workarounds, timing, tacit norms, and things people no longer notice enough to say out loud. The product does not enter a blank space. It enters an already-structured way of life.
This is exactly why design anthropology matters. It is less interested in extracting opinions than in understanding practice. It asks what people are doing, how their world is organized, what meanings hold that world together, and where technology might fit, disrupt, or misread the pattern.
Anthropology helps teams pay attention to the social texture around the task. Not only the interface moment, but the rituals before it, the workarounds around it, the identities bound up in it, and the institutional or domestic setting that makes the behavior possible.
Christina Wasson makes a strong case that design anthropology is not simply anthropology imported into design as a decorative method. It is a way of working that treats ethnographic understanding as central to how interventions get framed. The design question gets better because the world model gets better.
That distinction matters in product because teams often rush to solution while still misunderstanding the setting. They map a user flow without understanding the social flow the product is joining.
It changes decisions any time the product depends on routine, coordination, or context rather than one-off preference. Healthcare, education, financial tools, workplace software, caregiving products, and community systems all benefit from this lens because the product is never the only actor in the story.
Take a collaboration product. A standard research process might ask whether the interface is clear. An anthropological process might also notice how work actually gets delegated, which conversations happen in public versus private, who is expected to clean up ambiguity, and how hierarchy shapes what gets documented. Those observations often reveal the real problem faster than another usability round.
Or take a consumer app used in the home. The relevant unit may not be one user at all. It may be a household, a family routine, or a negotiation between roles. Product teams often say "user" where the real social unit is relational.
This does not mean every product team needs a year-long ethnography. It does mean teams can borrow better habits. Spend more time in context. Watch real work. Study adjacent artifacts. Ask what people have to coordinate around the product, not only within it. Treat workaround behavior as signal, not noise. Ask what social unit the product is actually entering.
It also means being slower to declare the problem understood. Anthropology is useful partly because it resists premature neatness. Product teams love clean problem statements. Lived life is rarely that clean.
That makes this essay a natural companion to Why Personas Flatten People and Jobs to Be Done Has a Sociology Problem. Both critique compressed models of users. Design anthropology offers one practical way to replace them with better understanding.
Better product work starts with better social observation. The team that understands the practice around the product will usually beat the team that understands only the interface inside it.