Your product team wants to be more user-centered. You hired your first UX researcher (or you’re looking for one now!), and you’re excited to work with them. Or, you may have a UX research team in your organization, but you’ve never worked with them. Either way, research is new territory. You don’t know what problems UX research can help you solve nor how to work with research.

In this post, I will explain what UX research does for organizations and how to best partner with researchers. I wrote this for people in design, product, engineering, and business development roles who wish to collaborate with research; however, it could equally help a UX researcher explain what they do to their new teams!

What do UX researchers do for an organization?

A UX researcher empowers organizations to deeply understand people who currently and who might use the product so organizations make decisions that benefit both users and the business. UX research investigates people’s experience at 3 levels described by Kim Flaherty: the interaction, the journey, and relationship to the organization. A researcher is a “compass throughout the product development lifecycle” (see Steve Wengrovitz’s post) and a “multiplier” that creates ways for the whole organization to learn about users (see Monty Hammontree’s post).

Research isn’t limited to usability testing an interface; it’s a powerful tool to guide product design and business strategy.

Insights from UX research typically have the biggest impact on short-term and long-term product development, but can have implications for all parts of the business. Research addresses both foundational questions (e.g, How do we position our product for adoption by the early majority?) and tactical questions (e.g., Why do people drop off toward the end of the purchase flow?).

Broadly, research guides product development in the following ways:

• Research before product development helps you build the right product.
• Research during product development helps you build a product in the right direction.
• Research after product development helps your know how successful your product is, and where it needs improvement.

I provide examples below of potential questions, how research might answer these questions, and the impact research can have on product and business.

Your team might ask the following foundational question: What product offerings should we release 3 years from now?

• UX research can address this amorphous question by investigating the lives of people you’re interested in — what does their day-to-day work look like outside of your product? Methods might include in-depth interviews (in the lab or in people’s homes/workplaces), diary studies, surveys, and competitive analysis. Research would also triangulate data from multiple sources (e.g., existing research, analytics, data from customer-facing teams like sales, support, and marketing). Based on this data, research would identify opportunity areas and use cases based on people’s needs, motivations, and behaviors. This knowledge positions your business to build the right offerings 3 years into the future.

Your team might ask the following tactical question: Which design prototype (out of multiple options) best supports people’s workflows?

• UX research can address this question by better understanding the context in which people use your product, whether the prototypes solve their problems and help them achieve their goals, and how well or not well people can perform key tasks with the prototype. Methods might include concept/prototype testing and usability testing. Based on this data, research would help you quickly evaluate designs with prototypes before they’re given to engineers to build.

What methods do UX researchers use?

UX researchers conduct both qualitative and quantitative research, but their methods tend to be more qualitative because the goal of UX research is to understand people’s experiences and behaviors in depth. However, there are quantitative UX researchers who specialize in statistical analysis of survey and behavioral log data (see post by Duyen Mary Nguyen, Saide Bakshi, and Alex Whitworth).

Qualitative research answers “why?” and “how?” questions to understand people’s attitudes, motivations, and processes. Qualitative research often involves interviewing and observing smaller sample sizes of people to answer descriptive questions. Examples of questions that qualitative research could answer are:

• Why are people dropping off in the purchase flow after adding items to their shopping cart?
• Why do people shop for a product online instead of a physical store?
• How do people shop for a product or service online?
• How do people feel when they’re shown ads in one context versus another?

Quantitative UX research answers “what?” and “how much?” questions to investigate behaviors and attitudes across large groups of people. Quantitative research often involves performing statistical analysis on survey data and behavioral log data with large samples of people to answer experience questions of scale. Examples of questions that quantitative research can answer are:

• How many people recall seeing a targeted ad on the website?
• How satisfied or dissatisfied were people with the ad?
• Were people in Condition A more/less frustrated than people in Condition B? Is that difference statistically significant?

For a comprehensive review of qualitative and quantitative research methods and when to use them, check out this article by Christian Rohrer.

Who do UX researchers work with?

A UX researcher typically works with product teams consisting of different skills that push forward short-term and long-term product development: design, product management, engineering, and content strategy. In some organizations, non-researchers conduct user research themselves — and that’s great after receiving training on research methods and best practices! It’s important to remember that while a researcher can train non-research partners in research basics, research is still an expertise that takes years of practice to do well and yield confident results.

A UX researcher will also work with other teams like sales, marketing, customer support, and analytics to consolidate existing internal knowledge. These teams have a wealth of information to share, which means researchers will not need to start from scratch when beginning a new research project. Findings from research are also important outside of product. For example, research insights can have implications for the sales funnel, how marketing positions a new product launch, help articles, and customer support training.

How do I effectively collaborate with UX researchers?

(1) Work with your researcher to identify “people problems” that your product can solve.

For products to be successful, they need to solve a need that people have and have clear use cases. If the product, service, or technology offering does not fit into people’s lives, it will not be successful in the market.

J.T. Trollman explains in his post, “‘People problems’ […] are needs and issues as they might be articulated by people on the street. They identify progress that people are trying to make in their daily lives and define what’s broken or unsatisfying about their current solutions. Note the difference between these and company problems — which are internal goals, priorities, and challenges that map back to your company mission.” To understand people’s needs, we must first identify the people problems (e.g., “My family has outgrown our home, but most bigger homes in our area are now outside our budget.”) and distinguish these from company problems (e.g., “We need to grow product adoption by 5% this quarter.”).

UX research is an excellent tool for identifying people problems; however, product teams sometimes shy away from research because they’re under pressure to quickly develop a minimum viable product (MVP) to meet an organizational objective. Unfortunately, this can lead to the trap of creating the wrong technology first and then puzzling over how to get people to use it, leading to lots of waste.

Research doesn’t have to slow you down, especially if you follow Steve Wengrovitz’s tips to get your researcher involved early, communicate your short-term and long-term research needs, and ask your researchers questions instead of asking for research methods. Your researcher will work with you to determine what research needs to be done, how research will fit into the product development roadmap, and what research methods are appropriate.

(2) Show your researcher what the organization already knows about its users and non-users.

Research doesn’t have to start from scratch! Often organizations have existing knowledge from sales, customer support, customer service/success, analytics, marketing, etc. (see my LinkedIn post and others’ comments on this topic). A researcher will use this knowledge as a starting point for their work and also figure out ways to incorporate this information into product development.

(3) Communicate what decisions research will inform and the priority level and timelines for those decisions.

This will enable your researcher make a more targeted research plan and prioritize the project based on impact and urgency. You want your researcher to spend time tackling the most impactful questions. What research insights would yield the most return on investment for the product or business? If you’ve already made decisions you’re reasonably confident about, and findings from research wouldn’t change plans, then you don’t need user research. When you conduct research as a checklist item in product development, this takes away from research with a higher return on investment. There are also times where it’s not appropriate to do user research, such as when behavioral analytics are better suited to answer the question or when you don’t know what you’ll do with the research (see Michele Ronsen’s Awkward Silences interview and LinkedIn post).

(4) Get involved in the research process, give your researcher feedback on the research process, and be ready to do some research yourself!

Will Myddelton aptly describes user research as a “team sport.” A researcher will not disappear and then give you a big reveal moment when the research is complete. Your researcher will likely want to involve you in some or all of the following steps: research planning, data collection, data analysis, and sharing of research more broadly. Being involved in research enables you to see what your users say and experience first hand, without waiting for your researcher to tell you later in a share-out. It also enables you to give your researcher feedback along the way to learn what is important (e.g., if you want them to spend more time on a specific topic with participants).

Ways to collaborate with your researcher during a research project:

• Work together on defining project goals and focus areas.
• Give your researcher feedback on study materials (e.g, discussion guides, survey drafts).
• If your researcher needs prototypes or builds from you to do the research, align on timelines so that your researcher has sufficient time to pilot those and incorporate them into the discussion guide. (See Michele Ronsen’s post on the importance of piloting research.)
• Attend research sessions, take notes, and comment on what stands out to you (in your notes, over Slack, etc.). If your researcher is okay with it, ask participants interview questions directly!
• If you attend a research session, debrief with your researcher about what stood out to you as the most important moments and why.
• Participate in research synthesis sessions.
• Discuss with your researcher what implications the findings have for your product, service, or wider business.
• Give your researcher direct feedback about the research process. What is working well and what are development areas? What is YOUR user experience of how your researcher brings you into the research and how they communicate findings? This feedback will help your researcher to work more effectively with your team.

You may encounter a situation where you’ll need to take on the research yourself, which is an amazing opportunity! As Monty Hammontree explains, the role of research is “empowering everyone to learn.” Your researcher is an expert on research, not a research gatekeeper. To that end, your researcher may offer consulting on research projects you take on, train non-research partners on research methods and best practices, and develop self-service resources (see Reduct.Video post by myself and Prabhas Pokharel about some ways researchers have democratized research in their organizations).

(5) Involve your researcher in non-research activities.

While researchers specialize in research, our facilitation skills and strategic mindset can impact our organizations in more ways than conducting new research projects. Here are some ways that researchers have partnered with teams in their organizations. These are based on responses to my LinkedIn post, as well as my past observations and conversations.

• Workshops, sprints, and brainstorms for product roadmapping and generating design/product ideas
• Activities to identify trust-breaking / trust-building moments for users, understand users across their lifecycle, and align multiple teams on how to teach users new interactions
• Synthesis of existing research, both internal and external to the organization (sometimes new research is not needed because past research exists!)
• Trainings and workshops on research methods (e.g., interviewing users), sketching, journey mapping, and empathy mapping
• Consulting on research projects that non-research partners conduct themselves (e.g., weekly research office hours) or on client research strategy
• Consulting on design strategy and on quarterly/annual product roadmaps
• Retrospectives on team collaboration
• New employee onboarding and orientation (e.g., vision exercise board game, bringing research insights into orientation activities)
• Document and share product feedback from sales and customer service
• Setting up tracking systems to measure sentiment and behaviors
• Selecting markets for testing products prior to wider release

(6) Work with your researcher to set the foundation to scale research in your organization (e.g., participant incentives, software/tooling, research ops).

I’ve had team members new to research express discomfort with paying research participants due to concerns about introducing bias. Michele Ronsen explains while it’s not possible to entirely eliminate bias, providing participants with an incentive for their time does not introduce bias if a researcher does their job properly: “We might be testing a hypothesis, a prototype or something else entirely, but we’re never testing ‘them’” (post, webinar). Giving research participants an incentive for their time is standard practice across industry and academic research. If budget is constrained and monetary payments or gift cards aren’t an option, then consider providing participants with discounts / credits for your products, swag, or entry into a raffle. Either way, it’s important to show appreciation for their time sharing their experience with your team.

To scale and conduct some forms of research, your researcher will need software and tools. As your team of researchers grows, they’ll need Research Operations to do research more effectively at scale (see Re+Ops community). The research SaaS products your researcher brings in will depend on your organization’s needs, budget, and the type of research being done most frequently. Check out the 2019 UX Research Tools Map by UserInterviews to get a sense of what is out there! If budget is tight, there are always creative workarounds (e.g., see my article about using Google Docs as a tool for different kinds of remote research).

Thank you to Amy Santee, Michele Ronsen, and michael / nagle for reviewing and providing feedback on drafts of this post.

The beliefs and statements included in this article are my own opinions, and do not necessarily reflect those of my current nor prior employers.

How to partner with UX researchers to positively impact product and business was originally published in UX Collective on Medium, where people are continuing the conversation by highlighting and responding to this story.

As a UX researcher, it’s essential to speak with participants who live outside of my geographic area; however, in person research isn’t always possible due to budget, time, and logistical constraints. For this reason, I often conduct remote research, where my participants and I are in different locations. Across different projects, I’ve found handy ways to use the collaborative abilities in Google Docs as a cost effective tool in remote research. In this post, I describe how I’ve used Google Docs to conduct remote research through diary studies, retrospective experience maps, and sacrificial concept tests.

Diary studies

During research beta programs I’ve led, my product stakeholders and I used diary methods to have participants record their experiences as they used a new product across time. We created an individual Google Doc for each participant, which only the participant and our product team had access to. In this document, participants answered a set of questions about their experience and could paste in screenshots to supplement their answers.

My product stakeholders and I regularly read diaries and asked participants follow up questions in the comments of Google Docs, allowing for ongoing dialog between us and participants. Conversing with participants over Google Docs comments enabled us to ask clarification questions, dig deeper into certain situations, and keep participants engaged throughout the longitudinal research.

At the end of research beta programs, we had a diary document from each participant that included the participant’s documentation of their experience across time, as well as a record of our dialogue with them.

Best practice tips:

• To encourage completion of diary entries, send participants automated reminder emails that contain a direct link to their Google Doc diary.
• To set expectations about privacy and research process, inform your participants beforehand that you and (if applicable) the people on your team / in your company will be reading and commenting on their diary document. If participants don’t know this in advance, they might be surprised or think they’re doing something incorrectly.
• Decide with your stakeholders what kind of engagement the team will have with participants inside of participant diary documents, and set ground rules of who can be tagged in these documents and what can be discussed. For example, if a participant mentions something that is interesting to another group in your company, and you tag a team member from the other group who doesn’t have context on the participant diary, you may risk stakeholders having conversations that are not relevant or not appropriate to have in the comments of the diary (e.g., roadmapping conversations).

Retrospective experience mapping

Following guidelines on retrospective experience methods (Carine Lallemand’s UXPA 2018 talk, Kujala et al. 2011, & Kujala et al. 2013), my research collaborators and I conducted a foundational research project where we asked participants to complete a pre-interview assignment, where they plotted and described their most memorable moments in their journey. To do this, we sent participants text and video instructions on how to complete the exercise by using an experience map template and experience questions we sent them.

We created an experience map template as a PDF file where they could plot and label their experience points on a scale, ranging from “very positive” to “very negative.” Participants could print or draw out this template to do the exercise by hand, or they could complete it digitally. After completing their experience map, we asked participants to take a digital photo or screenshot of their map.

To complement experience maps, we created a Google Doc for each participant where we asked them to place the image of their experience map and answer a set of questions about each experience point they plotted. By the end of this exercise, each participant had created a digital artifact in a Google Doc that illustrated their experience across their journey. This enabled us to ask these participants more targeted questions during our subsequent interviews with them.

Best practice tips:

• For remote retrospective experience mapping, provide participants with step-by-step instructions and an example of this exercise. To accomplish this, we sent participants text instructions and a video demo of us doing an experience map on a topic different from the one we were investigating. Participants expressed these instructions were very helpful to complete the exercise.
• Provide participants with an experience map template, but give them the option to complete it by hand or digitally (participants chose whatever method they were comfortable with). Participants can then capture an image of their experience map and place that image in a Google Doc containing a structured set of questions for each experience point.

Sacrificial concept testing

My product stakeholders and I have also used Google Docs to test sacrificial concepts of ideas that emerged from participant interviews. In one study, we asked our participants if they’d be willing to complete a follow up homework assignment after their interview, where would they review a set of concepts and answer questions about them.

After their interview, we sent each participant a Google Doc containing a set of sacrificial concepts (descriptions and images) and questions about each concept (Likert scales and open-ends). After participants completed the assignment, we went into their assignment and asked them follow up questions by using the comments feature in Google Docs. In this manner, we were able to get further clarification from participants about their responses and dig deeper into “why” questions.

By the end of data collection, we had gathered two complementary sets of data: foundational research interviews with participants and their sacrificial concept exercises in Google Docs.

Best practice tips:

• If you ask participants if they’d be willing to complete a follow up homework after their interview, offer them additional compensation for their time.

Conclusion

I described a few cost effective ways I’ve used Google Docs with my product stakeholders and research colleagues to collect participant data remotely, have participants produce digital artifacts for research, and converse with participants asynchronously around their artifacts. However, this method may not be effective nor appropriate in other research situations, such as studies with mobile only users in regions with poor internet connection.

I’d love to hear about any creative remote research techniques you’ve used as well!

The beliefs and statements included in this article are my own opinions, and do not necessarily reflect those of my current nor prior employers.

📝 Read this story later in Journal.

🗞 Wake up every Sunday morning to the week’s most noteworthy Tech stories, opinions, and news waiting in your inbox: Get the noteworthy newsletter >

At the time I wrote this post, I was on the User Experience (UX) Research Team at Udemy (a global online teaching and learning marketplace), and prior to that, I was a UX researcher at Facebook. I love the field of UX research, and I frequently receive questions about how I got into UX research and what one can do to prepare for a UX research career. Here I share a high-level overview of my journey to becoming a UX researcher and things I’ve learned along the way to prepare for this career. I organized this post by frequently asked questions that I’ve gotten and observed.

Question: How did you get into UX research?

I made my way from academic research into industry research. Like many UX researchers I know today, my path into the field wasn’t straightforward.

When I finished my Bachelor’s in Cognitive Science at Vassar College and my Master’s in Cognitive and Evolutionary Anthropology at the University of Oxford, UX research wasn’t a career option that many students knew about (I didn’t even know that UX research existed). All I knew was that I loved conducting research, but I wanted my research to have an applied impact on the world beyond academic publications. After working as a research assistant at the University of Miami Center on Aging (a center that studied the intersection of health and technology use among older adults), I began a PhD program in Human-Computer Interaction at Carnegie Mellon with a focus on online communities.

Almost 2 years into my PhD program, I got my first taste of applied UX research: I received an opportunity to do a summer internship with the Facebook UX Research Team (for more information about UX research at Facebook, see website and Facebook Research Medium posts). This internship was a pivotal moment in my career where I saw I was highly energized by collaborating with other researchers and cross-functional team members to work on product.

In the months after my internship, I made a decision (with the full support of my academic advisors and PhD program) to finish my program at the Master’s level. I subsequently took a full-time position as a UX researcher at Facebook, where I conducted qualitative and quantitative research for over 2 years on the Sharing and Applied Machine Learning teams.

I then transitioned into the EdTech industry and joined the growing UX Research Team at Udemy (for more information about UX research at Udemy, see Medium posts by Udemy’s research lead/manager, Claire Menke). At Udemy, I was the primary researcher on the instructor experience.

Question: Do I need a PhD to be a UX researcher?

No. While a PhD is more relevant if you want to pursue academic research in academia or industry research groups, it’s not at all necessary to get a PhD to go into UX research. Your work experience in applied research (i.e., your strength in research methodologies, analysis, write-ups/presentations, and explaining the implications of your research on product strategy and/or product design) is more important than the level of your academic degree.

Question: What fields do UX researchers come from, and what kind of a degree do I need to go into UX research?

You don’t need a degree in a specific field to be a UX researcher. However, you do need to acquire a deep knowledge of people’s behavior and technology use, whether that’s through work experience and/or school.

UX researchers generally come from backgrounds such as psychology, human-computer interaction, anthropology, sociology, communications, information science, and other behavioral fields.

UX researchers often have specific research methods they’re highly skilled at (e.g., surveying, one-on-one interviewing), but they also have experience in and the ability to learn other methods outside of their strength area(s). Note: UX research sometimes gets confused with usability testing. While usability testing is one thing that UX researchers can do, researchers can use a variety of qualitative and/or quantitative research methods to answer research questions. This article by Christian Rohrer provides an excellent overview of methods used by UX researchers.

In addition, check out this post by Yuling An for stories about how people from different backgrounds made their way into UX research. For students navigating their undergraduate careers, Omar K. El-Etr’s post shares his journey about moving from computer science to UX research (and recovering from imposter syndrome in the process).

Question: How do I prepare for a UX research career?

Regardless of where you are right now, pay attention to products and be curious about them (if you haven’t already!). For an example of product thinking, read Daniela Retelny’s post where she reviews her favorite physical technology products from 2017. When you think of or use a product, reflect on it by asking yourself “why,” “how,” “what,” “where,” and “when” questions (also see the “why” questions section of this post by Konstantin Escher). I provide examples of questions below that you can ask about any product (where product can broadly represent software, hardware, a service, consumer goods, etc.):

• Why does a product a offer a good/bad user experience for one group of people but not another group?
• How does this product meet or not meet needs that people have?
• What are pain points that people have while using this product?
• Where are people when they use this product?
• When or in what situations do people use this product?

Look if you or your contacts know anyone who works in UX research, and chat with them to learn about their experience, see if they know other people they could introduce you to, and/or if they know of work opportunities that might be a good fit for you. You can also check out the User Experience Research Professionals Association, and see if you have a local chapter or upcoming events near you.

The answer to this question also depends on where you are now. For example, are you an academic researcher looking to work in industry UX research? Are you already working in industry but in a different role from UX research?

Sub-question: How do I move from academic research into industry research?

If you’re an academic researcher who would like to try UX research or become a UX researcher, the most important thing is to get applied industry research experience where:

• You learn how to collaborate with and succinctly communicate research findings to cross-functional partners who aren’t researchers (e.g., product managers, designers, engineers, content strategists, marketing, etc.)
• Your work will have an impact on product strategy (e.g., what kind of product to build) and/or product design decisions (e.g., how to build a product)

Some ways to acquire industry research experience are participating in an industry research internship program, contracting for a specific industry research project while you are still in academia (some professors have even done this on their sabbaticals!), or conducting a volunteer research project with a local organization. However, if that’s not possible right now, or you’re in a highly theoretical academic field, seek out professors and labs in your university who do more applied research and find out how you can get involved.

For advice about landing an industry research job after graduate school, take a look at this post by Judd Antin.

Sub-question: I work in a non-research role at my company. How do I get involved in or learn more about UX research?

If you already work in industry and your company has a UX, design, or market research team, consider speaking with your manager and the research team’s manager to see how you can get involved in research projects. Check out Spencer Lanoue’s advice on shadowing and taking notes for experienced researchers in this post. If you don’t have researchers at your organization, then consider conducting your own applied research project. You could do research on something related to your role at your organization, or even a passion project outside of work! Also try searching for groups/labs in local universities that conduct applied research, and see if you can volunteer with them to get hands-on experience.

Have more questions? Do you want to become a UX researcher but aren’t sure how to break into the field?

If you have more questions, feel free to get in touch on tatianavlahovic.com! In addition, I co-organized a virtual panel with Michele Ronsen and Curiosity Tank about the transition from academic research to industry UX research: “What I wish I knew before starting a career in user research.” This panel has a great deal of advice and resources for people making this transition, but the content is relevant to anyone who wants to learn more about UX research. Check out the panel video and panel resources on Curiosity Tank.

The beliefs and statements included in this article are my own opinions, and do not necessarily reflect those of my current nor prior employers.

Becoming a UX researcher: my experience and things I’ve learned along the way was originally published in UX Collective on Medium, where people are continuing the conversation by highlighting and responding to this story.