{"id":12132,"date":"2020-05-26T16:04:24","date_gmt":"2020-05-26T15:04:24","guid":{"rendered":"https:\/\/uxstudioteam.com\/?p=12132"},"modified":"2022-05-19T14:34:00","modified_gmt":"2022-05-19T13:34:00","slug":"ethnographic-research","status":"publish","type":"post","link":"https:\/\/timemachine.uxstudioteam.com\/ux-blog\/ethnographic-research\/","title":{"rendered":"A Less Known But Powerful Helping Hand In Product Design: Ethnographic Research"},"content":{"rendered":"

Don\u2019t listen to your users is one of the ground rules of usability. <\/span>\u201cWhat people <\/span><\/i>say<\/i><\/b>, what people <\/span><\/i>do<\/i><\/b>, and what people <\/span><\/i>say they do<\/i><\/b> are entirely different things.\u201d<\/span><\/i> says Margaret Mead, cultural anthropologist. We keep this statement in mind while carrying out user research during product development. We don\u2019t listen to them – but what do we do instead?\u00a0\"UXstudio-ethnographic-research\"<\/span>If I tell you that one amazing solution to this is to include <\/span>ethnographic research<\/b> in your product design process, you will be a bit surprised and it might bring up a few questions for you. For instance: what is ethnographic research? What is the use of ethnography in product development? To be honest, at first, ethnography sounds quite academic… But trust me, it\u2019s a lot of fun! To prove this to you, I talked to <\/span>David Travis<\/b>, director of <\/span>Userfocus<\/span><\/a> about the importance of ethnographic research in product development.\u00a0<\/span><\/p>\n

\"what-is-ethnographic-research\"
Anika Huizinga on Unsplash<\/figcaption><\/figure>\n

In this article, I share David\u2019s tips and thoughts with you in my words: we are giving you a great summary of a method that can help you see through the eyes of your users!<\/p>\n

What is ethnographic research?\u00a0<\/span><\/h2>\n

Ethnographic research is a method that originates from anthropology. It studies and represents a culture. As user-centered design has gained ground over the years, ethnographic research methods have started to be used more and more in product development. One of the great benefits of ethnographic research is that it\u2019s conducted in a<\/span> real-life environment<\/b>. Because of that, it lets us peek behind the curtain. Studying our users in real-life scenarios uncovers issues that even the best-designed laboratory experiments can not present, which gives us a huge advantage.<\/span>\u00a0<\/span><\/p>\n

Ethnographic research is diverse, just as its major focus: <\/span>culture<\/b>. It has lots of names: <\/span>field research<\/span><\/a>, site visits, contextual inquiry, to mention a few. In a broader sense, it’s more like a mindset that helps the researcher understand the user group and its motivations and pain points better through <\/span>observation<\/b>.\u00a0<\/span><\/p>\n

\u201cIt\u2019s more ethnography-lite than true ethnography.\u201d – David Travis<\/span><\/i><\/p>\n

\"ethnographic
Poras Chaudhary: Smithsonian.com Photo Contest Archives<\/figcaption><\/figure>\n

Let\u2019s get practical\u00a0<\/span><\/h2>\n

Now, all that above sounds very interesting, but how do we apply it in product design? In the following, let me tell you about the tips and tricks I heard from David Travis.\u00a0<\/span><\/p>\n

\u201cThe whole field of ethnographic research in user-centered design is misknown in some ways.\u201d – David Travis<\/span><\/i><\/p>\n

Open your mind (to): The paradigm shift<\/span><\/h3>\n

Ethnography in the field of anthropology means that the researcher spends weeks, months, even years with the studied group. While in product design we don\u2019t have time for that. Things are going much faster in our processes: researchers spend a maximum of an hour with the users. Additionally, depending on the deadlines of the projects, oftentimes researchers don\u2019t have the possibility to include a significant number of participants in their studies.\u00a0<\/span><\/p>\n

The question of representativeness: quantitative & qualitative methods\u00a0<\/span><\/h3>\n

\u201cYou can gather as much quantitative data as you like, but that\u2019s not going to help you work out <\/span><\/i>how<\/i><\/b> you need to change your product. In order to work out how you should change your product in terms of design, you need the kind of insights that you get from qualitative research.\u201d – <\/span><\/i>David Travis<\/span><\/i><\/p>\n

We at <\/span>UX studio<\/span><\/a> believe that the best way of doing user research is to use a mixed-methods approach (qualitative and quantitative methods at the same time). We don\u2019t value qualitative or quantitative more than the other, instead, we decide on choosing – and mixing – the best methods depending on the needs of our individual partners.<\/span>\"\"<\/a>However, we all know about the power of numbers. When it comes to user research, we often tend to trust reports with more numbers: bigger sample, more user tests; something we can easily <\/span>measure<\/span><\/i>. Usually, greater numbers comfort us. We tend to think that the study which involves 1.000 participants is way more valuable than a study with 50 participants. But let me tell you why this assumption is wrong.\u00a0<\/span><\/p>\n

When it comes to research, data gathered from quantitative methods is very good at telling us <\/span>what <\/b>is happening in an interaction of our product and our users. But they don\u2019t tell us <\/span>why<\/b> it is happening. If you see that a certain issue is occurring, but you don\u2019t know the whys, it\u2019s more difficult to decide what kind of design changes you should make so that your product will perform better. To avoid this situation and to test both the <\/span>whats <\/b>and <\/span>whys<\/b>, we use a mixed-method approach.\u00a0<\/span><\/p>\n

\"field-research\"
Our researcher Bence doing field research<\/figcaption><\/figure>\n

The two most misunderstood facts about qualitative research methods<\/span><\/h3>\n

To be able to make a shift in our thinking about qualitative methods and confidently include them in our product research to get those <\/span>whys <\/i><\/b>answered, it\u2019s necessary to clear up some misconceptions.\u00a0<\/span><\/p>\n

1.) \u201cTo be able to deliver useful results, we need a representative sample.\u201d<\/i><\/b><\/p>\n

\u201cRepresentative samples don\u2019t play nicely with agile.\u201d – says David Travis in his eye-opening <\/span>article<\/span><\/a>. Setting a fixed amount of participants for research requires that we have our research problem and our solution to it defined upfront. Yet, in software development we rely on <\/span>iterations<\/b> so we need to be flexible and be able to change directions quickly based on research insights. The same flexibility should be given to researchers too in terms of setting and developing hypotheses and the research sample \u2014 which gives no room to work with a representative sample.<\/span><\/p>\n

2.) \u201cQualitative research lacks generalizability.\u201d<\/i><\/b><\/p>\n

The data we get from this type of research are more like <\/span>stories<\/b> \u2014 stories that can even conflict with each other. Seeing the world from different perspectives, through different people\u2019s eyes from different contexts, and listening to all their stories makes the insights of the research even more specific – and more complicated to analyze. However this doesn\u2019t mean qualitative methods lack generalizability. Generalizations can be derived from qualitative research in various ways (eg.: naturalistic generalization, transferability, analytical generalizability, and intersectional generalizability). It\u2019s just not the same as quantitative results. (Read more about these methods <\/span>here<\/span><\/a>.)<\/span>\"ethnography\"<\/p>\n

Ethnographic research design how-to: 6 steps to analyze the insights we get from an ethnographic study<\/span><\/h2>\n

Now that we understood the importance of qualitative research in product design, let\u2019s plan how to conduct an ethnographic study!<\/span><\/p>\n

0.)<\/strong> As preparation for carrying out your research, you have to set up your team. If you have a chance, work with a <\/span>cross-functional team<\/span><\/a>. The professional diversity helps to get even more fruitful results out of our observations – more eyes see more and different eyes see things differently. After setting up your team, get yourself ready to be exposed to users, and go out to the field!<\/span><\/p>\n

1.)<\/strong> Only <\/span>talk to<\/b> a handful of <\/span>people<\/b> first. You want to make sure to thoroughly analyze the insights and you also want to give space for changes and new directions as the research hypothesis emerge through the analysis.<\/span><\/p>\n

2.)<\/strong> Have<\/span> ethnographic notes and transcripts<\/b> of sessions about what people said about their experiences.\u00a0<\/span><\/p>\n

Then follow the steps of the <\/span>affinity diagram <\/b>technique:<\/span><\/p>\n

3.)<\/strong> Stick the nuggets of information on <\/span>post-its<\/b>.\u00a0<\/span><\/p>\n

4.)<\/strong> Have the<\/span> post-its with the insights on a<\/span> whiteboard<\/b> and develop them with the team. Look for patterns and insights related to each other, <\/span>group<\/b> those together.<\/span><\/p>\n

5.)<\/strong> Prioritize<\/strong> which insight is more important or less important for the product at that current stage. Prioritization is crucial to keep up with the fast-changing pace of product development teams. Focus on the top three or four, and make sure that they\u2019re addressed.<\/span><\/p>\n

6.)<\/strong> Iterate<\/strong> the product. Then do more research. Then come back and iterate again.<\/span><\/p>\n

\"kick-off-meeting\"<\/p>\n

The added value of ethnographic research<\/span><\/h2>\n

There are two aspects of what added value ethnographic methods bring to your product team.<\/span><\/p>\n

1.) It helps the product team develop empathy towards the user group they\u2019re designing for.<\/i><\/b>
\n<\/span>This is a specific kind of empathy. Not the one that helps you to understand the pain of others, but which gives you <\/span>the ability to see things from their perspective<\/b>. Additionally, you will be able to understand why users do the things they do, but for this to happen you have to make a shift in your mindset. Always start with the following sentence:\u00a0 <\/span>\u201cIf I was that user, in that context, I\u2019d probably do it like this way or that way…\u201d<\/span><\/i>\u00a0 This mindset will help you to really stick to the users\u2019 needs. If you were looking at it from a developer\u2019s point of view, you\u2019d probably do things differently. So, if you can understand <\/span>why<\/b> users behave the way they do, you can gain a level of empathy that is very useful in delivering the needed insights into product development.<\/span><\/p>\n

2.) <\/b>Product teams will stop seeing users as a homogeneous group. <\/b>
\n<\/span><\/i>Many teams get zero exposure to users they\u2019re designing for. You can avoid this and get a deeper and more profound understanding of user needs by spending time with them in their context. This way members of the team will see them as individuals and will be able to appreciate the diversity of the perspectives of the members of the user group. It is also possible that the team will enjoy realizing the fact that there are different users with different goals and different environments – which gives ground to develop new, creative solutions.<\/span><\/p>\n

\"types
Marc Kleen on Unsplash<\/figcaption><\/figure>\n

The challenges of ethnographic research<\/span><\/h2>\n

Hopefully by this time you feel the urge to include ethnographic research in your product design processes, however, remember that there are a few things you should keep in mind:<\/span><\/p>\n