← Blog

Business anthropology: what anthropologists actually do in tech

13 November 2026 · 5 min read

Illustration of an anthropologist working in tech

There is a small but persistent tribe inside tech companies whose job title says researcher and whose training says anthropologist. Business anthropology, sometimes called applied or design anthropology, is what happens when the discipline's methods and mindset leave academia for industry: studying users, customers, and the organisations themselves as cultures rather than as data points.

It is also one of the most misunderstood corners of the research world. Hiring managers tend to picture either an academic who needs a year in the field or an interviewer with a fancier degree. Anthropologists in industry are usually neither, and the teams that have one tend to fight to keep them. Here is what business anthropology actually involves, and what it adds.

What business anthropology looks like day to day

The daily work is closer to product research than the fieldwork memoirs suggest. Industry anthropologists run studies in homes, workplaces, hospitals, and shops; they observe people using products in context; they interview, but with an ethnographer's attention to what people do, not just what they say. If you have read our guide to ethnographic research, that is the methodological core, compressed to industry timelines: weeks, not years.

The lineage runs deeper than most people expect. Anthropologists were studying how office workers actually used technology at Xerox PARC decades ago, Intel famously employed them to understand how households adopt computing, and the field has its own annual gathering in EPIC, the Ethnographic Praxis in Industry Conference. This is an established profession, not an experiment.

A distinctive slice of the job also happens inside the building: treating the company itself as a field site. Why does this organisation keep shipping features nobody asked for? The answer is often cultural, and anthropologists are trained to see it.

Thick description, and why products need it

The discipline's signature idea is what the anthropologist Clifford Geertz called thick description: capturing not just behaviour but the meaning behind it. The illustration he made famous, borrowed from the philosopher Gilbert Ryle, is the difference between a twitch and a wink. The muscle movement is identical; the significance is completely different, and you can only tell them apart if you understand the context.

Product data is full of twitches that are actually winks. Thin data says a user abandoned checkout. Thick description notices that the purchase was happening on a shared family device, that the buyer needed a partner's agreement before spending, and that the abandonment was a negotiation, not a failure. Same event, entirely different product implication.

Making the strange familiar, and the familiar strange

Anthropology's classic move runs in two directions.

Making the strange familiar is the obvious one: helping a team understand people whose lives look nothing like their own, a smallholder farmer in a new market, a nurse on a night shift, a teenager's group-chat economy. Fieldwork renders unfamiliar worlds legible enough to design for.

Making the familiar strange is the rarer gift. Anthropologists question the categories everyone else has stopped seeing. Is "the user" really an individual, when the account is shared across a household? Is "adoption" the right frame, when people are visibly adapting the product into something else entirely? Workarounds, rituals, and improvised uses get treated as signal rather than noise, because they show what people actually need.

From fieldwork to product decisions

The make-or-break skill in industry is translation. A rich field study that ends as a beautifully written report changes nothing; the job is to carry meaning across the gap into roadmaps and design calls.

In practice that means framing findings as implications and opportunities rather than observations, pairing with product managers and designers during analysis instead of presenting at them afterwards, and holding every finding to the question it must survive: what would we do differently because of this? Methods like contextual inquiry fit comfortably into sprint-sized boxes, which helps the work land inside product rhythms rather than alongside them.

What hiring managers get wrong

  • "Ethnography is too slow for us." Trained observers extract signal fast. Industry ethnography runs in days and weeks, and a skilled fieldworker will often see more in three site visits than a dashboard reveals in a quarter.
  • "They are academics who cannot ship." Applied anthropologists are judged on decisions influenced, and the good ones know it. The writing gets leaner, the timelines are real, and the theory stays mostly under the surface, doing its work quietly.
  • "Ethnography just means interviews in someone's home." It is a stance, not a location: attention to context, meaning, and systems, wherever the work happens to be.
  • "It is a luxury for huge companies." The approach pays off most precisely when the map is least reliable: new markets, new categories, products that keep being used in ways nobody planned.

If your team is repeatedly surprised by how people actually live with your product, that is not bad luck, it is a missing lens. Anthropologists in tech exist to supply it: the patience to watch, the training to read meaning in behaviour, and the nerve to ask whether the team's basic categories are the right ones. You do not need to hire a department. One person who can make the familiar strange will change what everyone else sees.


People of Research is a community and newsletter for UX researchers, ethnographers, anthropologists, and social scientists making sense of people in industry. Join us and get the good stuff in your inbox.

Join 7,500+ researchers, free

One email a week, a global community, and events near you. No noise, just the people and ideas that matter.