May 16, 2015
Why do we care about Ethnosemantics?
Ethnosemantics is the study of how people relate concepts to each other. It is thus a scientific discipline that investigates the foundations of knowledge and understanding.
—Dr. Leon James, University of Hawaii
You will be surprised (at least, I was) to know that the majority of modern user research methods was developed by anthropologists in the early 20th century. Ethnosemantics, or ethnolinguistics, offers a comprehensive set of techniques to research users’ understanding of your product’s domain. Ultimately, you want to use the findings when shaping the information architecture.
Information architecture is the structure of all the data you have: navigation, labels and descriptions, search algorithms, metadata—you name it. Ethnosemantic research can make the information architecture of your site or application closely mimic how your users understand that information in the first place.
What problem are we solving?
- You are designing or building an app for a group of people you don’t identify yourself with (be honest, it is most likely true), and
- You want to refine discovery within your application.
How can ethnosemantics help design better interfaces?
The first discovery stage is interviewing your users. Interviewing is a structured technique to collect qualitative feedback. Interviewing is not just talking to your users; it is asking right questions and listening.
Interviewing is not specific to learning taxonomy, but something that could significantly improve your user experience in general. This empathetic step will help you understand people you are building the product for on a deeper level. The purpose of these interviews is to get a large amount of unstructured data. You can extract specific user terminology later on.
One interview might take half-an-hour to an hour. When scheduling interviews, ask to meet in the setting where the product will be used. I cannot emphasize enough, how important it is to conduct research in a right environment.
Most likely, you won’t be writing notes the entire conversation. I highly recommend a tool like Evernote. You can record the audio, but at the same time, you can simply jot down the time on the recorder when something interesting happens, and can come back to it later and listen again.
The first discovery stage is mostly interviewing your users (not talking to). It is not specific to learning the language, but something that could greatly improve your user experience in general. This empathetic step will help you understand people you are building the product for on a different level. Not just numbers and statistics, but who they really are. This is a half-an-hour technique inspired by anthropologic methods. You should give it a try.
- Start with a Grand Tour. It is a good way to find interesting themes. Ask questions like “Could you describe what a day of a single dad looks like?”, “Could you describe the hospital you are working at?”. The goal is to get a general vocabulary set for a place or action.
- When you hear an interesting word or interesting action the user describes try a Mini Tour. It is targeted on a specific term, usually an action and uses questions like “Could you describe [action]?”
- When you are interested in a very specific task your user has (like “find a babysitter”, “file a report”, “connect with grandparents”), try Story Questions. This tactic explores actual and often recent event with a question like “What was the last time you [task]?”
- Use Native Language questions when it is crucial to find that right word for your interface. You need to check how the term is used within a user group, or if the person is just using it for the interview. Try repeating the term you’ve heard in your own sentence. Alternatively, ask if that is how the informant uses it with his or her peers.
When going through your notes and recordings, look for all the terms specific to the domain of your product or terms related to the tasks users would be performing within your app. Then divide the terminology into verbs, nouns, and phrases.
Let’s take Acorns app as an example. It allows users to invest their change from purchases (Disclaimer: I don’t know what research the creators of Acorn conducted or what they’ve based their design decision on. I am just using their app as an example for potential research). The designers used terms like “government bonds”, “large cap”, “small cap”, “diversified portfolio”. The app is targeting people who have little investment experience and wouldn’t mind starting with something small like change. The user research could define what language these people use when it comes to finances use or what domain knowledge they have.
The purpose of identifying the taxonomic structure is to understand how your users relate concepts to each other. Taxonomic structures are especially important when designing navigation, indexes, or search algorithms. Take a look at these examples of taxonomies in practice.
These are three very different apps using taxonomies for their navigation. Well-designed navigation helps users find the right bit of information fast and with fewer steps. The relationship between the terms could be hierarchical (“dresses” and “casual”), associative (music that associates with “work-out”), means-end (“delivery” is a way to “get food”), or other. The appropriate structure depends on the goals of the design.
This is the area where you can improve and innovate discoverability. Working with the data you got from your users can help you find better label terms (“bottoms” vs. “pants”) or relationships (“BB cream” is not only a subset of “makeup”, but also “skincare”). Taxonomic structure largely depends on semantic relationships between terms, and there are many different ways to structure them. Here are two different approaches:
The first method is used in anthropology to study “folk terms”. The second one is used in information science to create controlled vocabularies and indexes. Use these approaches to analyze raw data you got from the interviews.
Your product has a voice, whether or not it is intentionally designed. It speaks to the user through buttons, pop-ups, error messages, and everything that has words in it. Design products that speak the same language with the user.