9 UX Research Methods for Product Teams

Product teams build things for people. But how do you know if the thing you built is what people need? The answer is user experience (UX) research.

This is the process of learning about your users, their needs, and their problems. With this data, you can build products that people find easy to use and truly love.

Good UX research helps you avoid making big mistakes. It stops you from building a product no one wants.

It helps you find and fix issues before they cost you time and money. By putting users first, you can make smarter choices and build better products. This post will show you nine key UX research methods.

These methods will give you the tools you need to learn what your users think and feel. You will learn how to ask the right questions and how to find the right answers to build products that work.

1. User Interviews

Understand your users’ needs and pain points. User interviews are one-on-one talks with people who use or might use your product. The goal is to get deep insights into their thoughts, feelings, and actions. This method is great for the start of a project when you want to explore a topic or an idea.

When to Use User Interviews

Discovery Phase: At the start of a project to learn about user problems and needs.
Concept Validation: To get feedback on new ideas before you build them.
Persona Building: To gather rich details to create accurate user personas.

How to Conduct User Interviews

Define Your Goals: Know what you want to learn from the interview. Are you trying to see if there is a market for a new app? Or do you want to find out why users are not using a certain feature?
Find Participants: Look for people who fit your target user profile. You can find them through your current user base, social media, or a research firm. Aim for 5 to 8 people for one round of interviews.
Prepare Your Questions: Write open-ended questions that ask people to tell stories. Avoid questions that can be answered with a “yes” or “no.” For instance, instead of asking “Do you like our app?”, ask “Can you tell me about the last time you used our app?”
Conduct the Interview: Make the user feel at ease. Start with some easy questions. Record the session if you get their okay. Listen more than you talk. Ask follow-up questions to dig deeper into their answers.
Analyze the Data: After the interviews, look for themes and patterns in the notes and records. Group similar comments and look for key insights that can guide your design choices.

User interviews give you rich, qualitative data that can shape the way you think about your product and your users.

2. Surveys

Gather quantitative and qualitative data from a large group. Surveys are a set of questions sent to many people to collect data on their views, actions, and traits. They are a good way to get a lot of data fast and at a low cost. You can use surveys at any stage of the design process.

When to Use Surveys

Market Research: To learn about the size of your market and who your users are.
Customer Satisfaction: To measure how happy users are with your product.
Prioritizing Features: To find out which features users want most.

How to Create Effective Surveys

Set Clear Goals: Know what you want to find out. This will help you write the right questions.
Keep it Short and Simple: People are busy. A long survey will have fewer people who finish it. Only ask what you need to know.
Use a Mix of Question Types: Use multiple-choice, rating scales, and open-ended questions. This mix gives you both hard numbers and rich context.
Write Neutral Questions: Do not write questions that lead people to a certain answer. For example, instead of “Don’t you think our new feature is great?”, ask “How would you rate our new feature on a scale of 1 to 5?”
Test Your Survey: Before you send it out, have a few people take the survey to check for any unclear questions or issues.
Distribute and Analyze: Send your survey out through email, social media, or on your website. Use tools like SurveyMonkey or Google Forms to collect and review the data. Look for trends and key stats.

Surveys are a powerful tool for getting data from many users at once, helping you make data-driven choices.

3. Usability Testing

Observe users as they interact with your product. Usability testing involves watching real users try to do tasks with your product. The goal is to find any problems they face, so you can fix them. This method is key to making a product that is easy and pleasant to use.

When to Use Usability Testing

Throughout the Design Process: From early wireframes to the final product.
To Validate Design Changes: To see if a new design is better than the old one.
To Find Usability Issues: To spot where users get stuck or confused.

How to Run a Usability Test

Define Objectives and Tasks: Decide what you want to test. Create real tasks for users to do. For example, “Find a red shirt in your size and add it to your cart.”
Recruit Participants: Find 5 to 7 users who match your target audience. You do not need a lot of people to find the most common issues.
Prepare a Test Plan: Write down the steps for the test, from the intro to the tasks and the final questions. This keeps each session the same.
Moderate the Session: Sit with the user as they do the tasks. Ask them to think out loud. Do not help them, even if they get stuck. The goal is to see where they have problems. You can also run tests where no one is there to watch.
Analyze the Findings: Watch the records and review your notes. Look for common pain points and areas where users struggled. Please make a list of issues and sort them by severity.

Usability testing shows you exactly where your design is not working for your users, giving you clear next steps to make it better.

4. Card Sorting

Organize your content in a way that makes sense to users. Card sorting is a method where you ask users to group topics into groups that feel right to them. This helps you design the information architecture (IA) of your site or app.

When to Use Card Sorting

Designing a New Website: To create a clear and user-friendly site map.
Redesigning an Existing Site: To see if your current structure is good or needs to be changed.
Labeling Navigation: To come up with names for your menus that users will understand.

How to Conduct a Card Sort

Prepare the Cards: Write down your content topics on individual cards. You can use real cards or a digital tool like OptimalSort.
Recruit Participants: Get 15-20 users from your target audience.
Run the Session: Ask users to sort the cards into groups that make sense to them. In an “open” card sort, they can name the groups. In a “closed” card sort, you give them the group names.
Analyze the Results: Look for common groups and patterns. See which cards are often grouped. This data will help you build a navigation system that aligns with how your users think.

Card sorting helps you build a structure for your content that feels natural to your users, making it easier for them to find what they need.

5. Tree Testing

Evaluate the findability of topics on your website. Tree testing is a way to test your site structure, or “tree.” You give users a task and see if they can find the right information in your menu tree. It’s like usability testing, but just for your navigation.

When to Use Tree Testing

After Card Sorting: To check the structure you created from a card sort.
Before Visual Design: To test the site map before you spend time on its look it.
To Improve an Existing IA: To find out why users can’t find things on your current site.

How to Conduct a Tree Test

Build Your Tree: Create a text-only version of your site structure. Use a tool like Treejack.
Write Tasks: Create tasks that ask users to find a specific piece of information. For example, “Where would you go to find out about shipping fees?”
Recruit Participants: Find users who represent your target audience.
Analyze the Data: The tool will show you where users clicked, how long it took them, and if they were right. This tells you which parts of your structure work and which need to be changed.

Tree testing gives you hard data on how easy it is for users to find content, so you can build a more effective site structure.

6. Diary Studies

Collect long-term data about user behavior and experiences. In a diary study, you ask users to keep a log of their actions and thoughts over a period of time, from a few days to a few weeks. This method gives you deep insights into user habits in their real context.

When to Use Diary Studies

Understanding User Habits: To learn about user routines and how your product fits in.
Tracking Behavior Over Time: To see how user actions change with time.
Capturing Context: To understand the world in which your product is used.

How to Run a Diary Study

Define Your Goals and Timeline: Decide what you want to learn and for how long the study will run.
Recruit Participants: Find users who are willing to take part for the whole study period.
Provide a Diary Tool: Give users a way to log their data. This can be a paper book, a digital form, or a mobile app.
Give Clear Instructions: Tell users what to record and when. You might ask them to log every time they use your app, or at the end of each day.
Analyze the Entries: At the end of the study, go through all the diary entries. Look for patterns in behavior, common problems, and quotes that show the user’s point of view.

Diary studies offer a rich view into the daily lives of your users, helping you design products that meet their real-world needs.

7. Focus Groups

Facilitate a group discussion to gather opinions and attitudes. A focus group brings a small group of people (6-9) to talk about a topic, product, or service. A host leads the talk, asking questions and making sure all voices are heard.

When to Use Focus Groups

Exploring Broad Concepts: To get a range of views on a new idea.
Understanding Brand Perception: To find out what people think of your brand.
Generating New Ideas: To brainstorm new features or products with users.

How to Conduct a Focus Group

Define Your Objectives: Be clear about the goal of the discussion.
Recruit Participants: Find a diverse group of people from your target audience.
Create a Discussion Guide: Plan the questions you will ask to guide the talk.
Moderate the Session: The host should guide the chat but not lead it. They should get everyone to share their views.
Analyze the Discussion: Review the record and notes. Look for common themes, areas of agreement, and points of debate.

Focus groups can give you a quick sense of user views and can spark ideas that you may not have found in one-on-one interviews.

8. Contextual Inquiry

Observe users in their natural environment. Contextual inquiry, or a field study, is when a researcher watches users as they do tasks in their own home or work space. This helps you see the real-world context in which your product is used.

When to Use Contextual Inquiry

To Understand Complex Workflows: To see how people really work.
To Discover Unmet Needs: To find problems that users don’t even know they have.
To Get Rich Contextual Data: To learn about the physical and social world of your users.

How to Conduct a Contextual Inquiry

Plan the Visit: Set a goal for the study and find users to visit.
Observe and Interview: Watch the user as they do their normal tasks. Ask questions as you go to learn why they do what they do.
Record Your Observations: Take detailed notes, photos, and videos (with their okay).
Analyze the Findings: Look for patterns in behavior and the impact of the world on the user’s actions. Use this to guide your design.

Contextual inquiry gives you deep empathy for your users by showing you their world firsthand.

9. A/B Testing

Compare two versions of a design to see which one performs better. A/B testing, or split testing, shows two versions of a page (Version A and Version B) to users at random. You then measure which version is more effective at reaching a certain goal, like getting more clicks or sales.

When to Use A/B Testing

Optimizing Key Metrics: To improve conversion rates, click-through rates, or other key metrics.
Testing Small Changes: To see the impact of changing a headline, button color, or image.
Making Data-Driven Decisions: To use real data to choose between two design options.

How to Run an A/B Test

Identify a Goal: Choose one metric you want to improve.
Create a Variation: Change one thing on your page to create Version B.
Run the Test: Use a tool like Optimizely or Google Optimize to show the two versions to your users.
Analyze the Results: Wait until you have enough data. The tool will tell you if there is a big enough difference between the two versions to declare a winner.

A/B testing is a great way to make small, steady improvements to your product based on real user behavior.

Build Products Users Love

These nine UX research methods give you a full toolkit to learn from your users. By using these methods, you can move from what you think you know to what you know for sure. Start with user interviews to find user needs. Use surveys to get data from many people. Run usability tests to find and fix issues.

When you make UX research a core part of your process, you build a culture that values the user. This leads to better products, happier users, and a stronger business. Start small, pick one or two methods, and begin learning. Your users will thank you for it.