• Diary study
• User interview
• Stakeholder interview
• Requirements & constraints gathering
When deciding where to start or what to focus on first, use some of these top UX methods. Some methods may be more appropriate than others, depending on time constraints, system maturity, type of product or service, and the current top concerns. It’s a good idea to use different or alternating methods each product cycle because they are aimed at different goals and types of insight. The chart below shows how often UX practitioners reported engaging in these methods in our survey on UX careers.
If you can do only one activity and aim to improve an existing system, do qualitative (think-aloud) usability testing , which is the most effective method to improve usability . If you are unable to test with users, analyze as much user data as you can. Data (obtained, for instance, from call logs, searches, or analytics) is not a great substitute for people, however, because data usually tells you what , but you often need to know why . So use the questions your data brings up to continue to push for usability testing.
The discovery stage is when you try to illuminate what you don’t know and better understand what people need. It’s especially important to do discovery activities before making a new product or feature, so you can find out whether it makes sense to do the project at all .
An important goal at this stage is to validate and discard assumptions, and then bring the data and insights to the team. Ideally this research should be done before effort is wasted on building the wrong things or on building things for the wrong people, but it can also be used to get back on track when you’re working with an existing product or service.
Good things to do during discovery:
Exploration methods are for understanding the problem space and design scope and addressing user needs appropriately.
Testing and validation methods are for checking designs during development and beyond, to make sure systems work well for the people who use them.
Listen throughout the research and design cycle to help understand existing problems and to look for new issues. Analyze gathered data and monitor incoming information for patterns and trends.
Ongoing and strategic activities can help you get ahead of problems and make systemic improvements.
Use this cheat-sheet to choose appropriate UX methods and activities for your projects and to get the most out of those efforts. It’s not necessary to do everything on every project, but it’s often helpful to use a mix of methods and tend to some ongoing needs during each iteration.
Related courses, discovery: building the right thing.
Conduct successful discovery phases to ensure you build the best solution
Pick the best UX research method for each stage in the design process
Create, maintain, and utilize personas throughout the UX design process
Please accept marketing cookies to view the embedded video. https://www.youtube.com/watch?v=7_sFVYfatXY
Competitive Reviews vs. Competitive Research
Therese Fessenden · 4 min
15 User Research Methods to Know Beyond Usability Testing
Samhita Tankala · 3 min
Always Pilot Test User Research Studies
Kim Salazar · 3 min
Project Management for User Research: The Plan
Susan Farrell · 7 min
Open-Ended vs. Closed Questions in User Research
Maria Rosala · 5 min
Formative vs. Summative Evaluations
Alita Joyce · 5 min
UX Research Methods: Glossary
Raluca Budiu · 12 min
What a UX Career Looks Like Today
Rachel Krause and Maria Rosala · 5 min
Pilot Testing: Getting It Right (Before) the First Time
Amy Schade · 5 min
Cori Widen currently leads the UX Research team at Lightricks. She worked in the tech industry for 10 years in various product marketing roles before honing in on her passion for understanding the user and transitioning to research.
Get the most value out of your research project from day 1.
If you’re a Product Manager without a user research team, are you out of luck? Absolutely not. Though dedicated researchers are truly the dream (I’m biased, as I lead a team of them myself), a user-centric PM can create and execute a UX research plan that answers some of the most crucial questions about users during the product development and product design process.
I’ll walk you through exactly what to do and how to do it—let’s dive in.
Before we get into user research tools and the specifics of how to create a user research plan, it’s important to reflect a little bit about when it’s most helpful to conduct user research. Particularly if you’re not a full-time researcher, you’ll want to make sure that you’re investing time in research where it’s most worthwhile.
Here’s a handy chart to guide your thought process about whether or not it’s time to roll up your sleeves and do some research.
You’re lacking new ideas for features or other initiatives that answer user needs | You don’t have time to make iterations on whatever section of the product you’d like to research |
You had a highly successful or unsuccessful product initiative and you aren’t sure what you can learn from the experience for future iterations | Your current questions about your users are more because you’re curious and less because you need answers in order to make product decisions |
There is a disagreement or lack of knowledge on your team about which user pain points or needs are most crucial to solve | You won’t have time to finish up your research before you have to make the relevant product decisions |
You are working on a new flow or feature and are questioning what the ideal UX is |
Overall, doing user research makes sense when you have a practical reason for doing so and when you have sufficient time to do research and define actionable insights. It also bears noting that skipping user research means running the risk of developing a poorly-designed product .
Now, let’s assume that you’ve put some thought into this and you’re feeling ready to get started. Next is your step-by-step guide for creating a solid user research plan.
If you do a quick search, you’ll see that the world is full of many different UX research podcasts , resources, and approaches when it comes to creating a research plan. In my role as a User Research Lead, I’ve found that a short, to-the-point one-pager is the best way to both plan your research in a way that all stakeholders can understand and to leave enough time to, you know, actually do the research. Here are the steps to follow when you go about creating your one-page plan.
It’s often tempting to start the conversation about user research with methodology—“we’ll do some interviews” or “we’ll conduct a survey.” The truth is, though, that you can’t know what methodology to use, or even whether you want to use a quantitative or qualitative methodology, until you work with your team to define your goals.
Once you’ve defined your goals—in other words, what you want to learn and why—and your whole team is aligned, you’ll be able to start drafting your research plan.
Stay in-the-know on all things product management including trends, how-tos, and insights - delivered right to your inbox.
Get together the smallest, most relevant group of colleagues whose work will be directly impacted by your research. Often, this group includes other product managers, the UX or product design team, product marketing managers, and a representative from senior management on the product team.
Think about what makes sense given your product development workflow and organizational culture and get everyone together.
Consider this meeting a brainstorming meeting where you’ll have the ability to get outside of your own head and hear from other colleagues about what they’d like to learn. Ultimately, since you’re creating the research plan and owning the UX design research process , you’ll decide what makes it in and what doesn’t.
Not only does this brainstorming session with your colleagues give you practical information to include in your research plan, but you’ll find that it’s easier to get buy-in for the research process when your colleagues feel that they’re genuinely involved.
When brainstorming with your team, challenge everyone who puts forward a question about users to explain how answering that question will help them make important product decisions. This is a helpful way to whittle down your research goals to the things that will actually have practical, tangible value in the foreseeable future.
Now that you’ve brainstormed with your colleagues, and you have all of the information that motivated you to start planning research in the first place, you’re ready to start drafting your plan.
The first section of your research plan should be what is called The Story.
The Story is anywhere from 3 to 6 sentences explaining briefly, in words, what you’re doing and why. The goal of this section is to craft a short narrative such that anyone who reads it knows why you’re doing research and what the expected impact of your knowledge will be.
Let’s look at an example to help you get started. Imagine that your company has a mindfulness app and is planning to build a community feature where people who are interested in mindfulness can interact with each other in a meaningful way. A sample Story may look something like this:
This quarter, the product team is beginning an ambitious project to create a mindfulness community within the app. Our goal is to provide genuine value to our users, and we’ll be using metrics in the realm of conversion rate and community engagement to measure our success.
Before we begin creating the product roadmap for the community, the team is going to conduct user research in order to learn more about our target audience and the ways in which our future community can best serve them. This research will allow us to kick off the project by understanding user needs related to the community more in-depth so that we can begin brainstorming product solutions.
Notice that in the Story section, you’re being fairly general in order to give context and background—in the next section, you’ll write out your concrete research goals.
After the story, you’ll create your Scope section, which is the section of the research plan where you’ll define your specific research questions. Simply put, this is where you write out, usually in a bulleted list, what exactly you want to learn from your research.
Continuing with our mindfulness community example, a Scope may look something like this:
The scope can be longer or shorter than this example, and you can use the syntax that makes the most sense for your team—but the overall idea is that anyone who reads the Scope section of your UX research plan will know exactly what your research questions are and what type of information you’re looking to learn.
Next up, you’ll use your Story and your Scope to decide which research methodology you’ll be using…
Once you’ve defined your Scope, you can decide which research methods will best help you to answer the research objectives that you’ve defined. There are a lot of decisions to make here, and you’ll likely be asking yourself questions like:
These are all great and relevant questions—and it’s certainly true that a hugely important part of the research process is choosing the appropriate methodology. Even the most commonly used methods—interviews, surveys , usability testing, and so on—give very different types of information.
The good news is that—even if you’re not yet knowledgeable about which UX research methods to use and when—there are a ton of good user experience research resources out there that can give you some guidance. This guide is a great place to start when it comes to understanding which research techniques will help you with your specific research project.
To understand more about the number of participants to recruit, or how many research sessions to do, for each stage of your UX research project, this article does a great job at defining what to take into account.
Once you’ve defined your methodology, write it out in your research plan. Title the section Methodology and include one bullet point for each method – and yes, it’s definitely possible that you’ll use more than one research method in your research project.
Make sure to define the target research participants for each method.
Here is an example of what bullet points under the Methodology section may look like:
You can include other relevant details in this section if you think they’re important to state. For example, will each method be conducted in-person or virtual? Do you want to link to your list of interview questions for transparency about what you’ll ask users if you are doing interviews? As long as the core information is here, you can add details that you think your team needs to align on and/or be aware of.
Ask any user researcher and they’ll tell you that anyone who gets wind of a user research project will immediately want to know how long it’s going to take. At the end of your one-page research plan, give a target date for when your research deliverables will be ready. Simply, this means: when will you have your research insights and product recommendations ready to present to other stakeholders?
You may want to specifically define your timeline as approximate in your research plan since actually executing research can be somewhat unpredictable. For example, your project timeline may need to be altered depending on how long it takes you to recruit participants, which you can’t always anticipate precisely in advance.
In addition to your Timeline, think about whether it makes sense within your organizational culture to make explicit your Budget for the project in your research plan. If your manager will need to approve your plan and expenses such as paying research participants for their time, it’s a good idea to include it in your plan.
The okr roadmap: what it is & how to use it, product strategy: what it is, and how to nail it, the top 10 ux design trends of 2024, step 6: share your research plan for feedback and final alignment.
Congratulations! You’re finished with the first draft of your UX research plan. It’s one page, it gives all of the necessary context, and it lays out exactly what you’re going to do and when. Just to recap, your very basic UX research plan template is something like this:
Story : Give the general context for this research
Scope : Give a bulleted list of what you’d like to learn from this study
Methodology : List which research methods you’ll use and with whom
Timeline : Give an approximate timeline for your research and tell everyone when you plan to deliver your results
Budget : If needed, define your budget here for approval
The next and final step is to share the main stakeholders with the draft of your plan. Allow comments, and use your judgment as to which user feedback to incorporate (or not). Once you feel that you and your colleagues are reasonably aligned, you’re done! You have your research plan and you’re ready to start doing your user research project.
Whether this is your first time implementing a user research plan or you have some experience, it’s worth taking a little bit of time to reflect on some best practices right before you get started.
Here are some tips and tricks to keep in mind as you move forward:
It can feel overwhelming to initiate and execute user research projects among all of your other tasks, but hopefully, now that you’ve drafted your one-page plan, you feel that it’s more manageable. Most product and UXR professionals who have leaned into user research and integrated it into the product development process describe it as transformative for themselves, the product, and their team members. It’s invigorating to learn from your users and to use your research findings as a starting point for key product initiatives.
As your user research journey continues, be sure to subscribe to The Product Manager newsletter , which is one of my favorite sources for new and timely advice when it comes to user experience research.
Happy researching!
by Rick Dzekman
An often neglected step in UX research
UX research should always be done for a clear purpose – otherwise you’re wasting the both your time and the time of your participants. But many people who do UX research fail to properly articulate the purpose in their research objectives. A major issue is that the research objectives include assumptions that have not been properly defined.
When planning UX research you have some goal in mind:
As part of this goal you write down research objectives that help you achieve that goal. But for many researchers (especially more junior ones) they are missing some key steps:
One approach people use is to write their objectives in the form of research hypothesis. There are a lot of problems when trying to validate a hypothesis with qualitative research and sometimes even with quantitative.
This article focuses largely on qualitative research: interviews, user tests, diary studies, ethnographic research, etc. With qualitative research in mind let’s start by taking a look at a few examples of UX research hypothesis and how they may be problematic.
Example hypothesis: users want to be able to filter products by colour.
At first it may seem that there are a number of ways to test this hypothesis with qualitative research. For example we might:
These approaches are all effective but they do not and cannot prove or disprove our hypothesis. It’s not that the research methods are ineffective it’s that the hypothesis itself is poorly expressed.
The first problem is that there are hidden assumptions made by this hypothesis. Presumably we would be doing this research to decide between a choice of possible filters we could implement. But there’s no obvious link between users wanting to filter by colour and a benefit from us implementing a colour filter. Users may say they want it but how will that actually benefit their experience?
The second problem with this hypothesis is that we’re asking a question about “users” in general. How many users would have to want colour filters before we could say that this hypothesis is true?
This is an obvious improvement to the first example but it still has problems. We could of course identify further assumptions but that will be true of pretty much any hypothesis. The problem again comes from speaking about users in general.
Perhaps if we add the ability to filter by colour it might make the possible filters crowded and make it more difficult for users who don’t need colour to find the filter that they do need. Perhaps there is a sample bias in our research participants that does not apply broadly to our user base.
It is difficult (though not impossible) to design research that could prove or disprove this hypothesis. Any such research would have to be quantitative in nature. And we would have to spend time mapping out what it means for something to be “easier” or what “the right products” are.
The problem with this hypothesis should now be obvious: what would it actually mean for this hypothesis to be proved or disproved? What portion of travelers would need to book their flights first for us to consider this true?
This hypothesis is better because it talks about “most users” rather than users in general. “Most” would need to be better defined but at least this hypothesis is possible to prove or disprove.
We could address this hypothesis with quantitative research. If we found out that it was true we could focus our design around the primary use case or do further research about how to attract users at different stages of their journey.
However there is no clear way to prove or disprove this hypothesis with qualitative research. If the app has a million users and 15/20 research participants tell you that this is true would your findings generalise to the entire user base? The margin of error on that finding is 20-25%, meaning that the true results could be closer to 50% or even 100% depending on how unlucky you are with your sample.
There are many things wrong with this hypothesis but we will focus on the hidden assumptions and the links to design decisions. Two big assumptions are that (1) it’s possible to find out what research participants want and (2) people’s wants should dictate what features or services to provide.
One of the biggest problem with using hypotheses is that they set the wrong expectations about what your research results are telling you. In Thinking, Fast and Slow, Daniel Kahneman points out that:
Using a research hypothesis primes us to think that we have found some fundamental truth about user behaviour from our qualitative research. This leads to overconfidence about what the research is saying and to poor quality research that could simply have been skipped in exchange for simply making assumption. To once again quote Kahneman: “you do not believe that these results apply to you because they correspond to nothing in your subjective experience”.
We can fix these problems by instead putting our focus on research objectives. We pay attention to the reason that we are doing the research and work to understand if the results we get could help us with our objectives.
This does not get us off the hook however because we can still create poor research objectives.
Let’s look back at one of our prior hypothesis examples and try to find effective research objectives instead.
In thinking about the colour filter we might imagine that this fits into a larger project where we are trying to decide what filters we should implement. This is decidedly different research to trying to decide what order to implement filters in or understand how they should work. In this case perhaps we have limited resources and just want to decide what to implement first.
A good approach would be quantitative research designed to produce some sort of ranking. But we should not dismiss qualitative research for this particular project – provided our assumptions are well defined.
Let’s consider this research objective: Understand how users might map their needs against the products that we offer . There are three key aspects to this objective:
The next step is to look at the assumptions that we are making. One assumption is that mental models are roughly the same between most people. So even though different users may have different problems that for the most part people tend to think about solving problems with the same mental machinery. As we do more research we might discover that this assumption is not true and there are distinctly different kinds of behaviours. Perhaps we know what those are in advance and we can recruit our research participants in a way that covers those distinct behaviours.
Another assumption is that if we understand our users’ mental models that we will be able to design a solution that will work for most people. There are of course more assumptions we could map but this is a good start.
Now let’s look at another research objective: Understand why users choose particular filters . Again we are looking to understand something that we did not know before.
Perhaps we have some prior research that tells us what the biggest pain points are that our products solve. If we have an understanding of why certain filters are used we can think about how those motivations fit in with our existing knowledge.
Our actual research will involve some form of asking questions and/or making observations. It’s important that we don’t simply forget about our research objectives and start writing questions. This leads to completing research and realising that you haven’t captured anything about some specific objective.
An important step is to explicitly write down all the assumptions that we are making in our research and to update those assumptions as we write our questions or instructions. These assumptions will help us frame our research plan and make sure that we are actually learning the things that we think we are learning. Consider even high level assumptions such as: a solution we design with these insights will lead to a better experience, or that a better experience is necessarily better for the user.
Once we have our main assumptions defined the next step is to break our research objective down further.
The best way to consider this breakdown is to think about what things we could learn that would contribute to meeting our research objective. Let’s consider one of the previous examples: Understand how users might map their needs against the products that we offer
We may have an assumption that users do in fact have some mental representation of their needs that align with the products they might purchase. An aspect of this research objective is to understand whether or not this true. So two sub-objectives may be to (1) understand why users actually buy these sorts of products (if at all), and (2) understand how users go about choosing which product to buy.
Next we might want to understand what our users needs actually are or if we already have research about this understand which particular needs apply to our research participants and why.
And finally we would want to understand what factors go into addressing a particular need. We may leave this open ended or even show participants attributes of the products and ask which ones address those needs and why.
Once we have a list of sub-objectives we could continue to drill down until we feel we’ve exhausted all the nuances. If we’re happy with our objectives the next step is to think about what responses (or observations) we would need in order to answer those objectives.
It’s still important that we ask open ended questions and see what our participants say unprompted. But we also don’t want our research to be so open that we never actually make any progress on our research objectives.
At the end it’s important to review every task, question, scenario, etc. and seeing which research objectives are being addressed. This is vital to make sure that your planning is worthwhile and that you haven’t missed anything.
If there’s time it’s also useful to run a pilot study and analyse the responses to see if they help to address your objectives.
It should be easy to see why research hypothesis are not suitable for most qualitative research. While it is possible to create suitable hypothesis it is more often than not going to lead to poor quality research. This is because hypothesis create the impression that qualitative research can find things that generalise to the entire user base. In general this is not true for the sample sizes typically used for qualitative research and also generally not the reason that we do qualitative research in the first place.
Instead we should focus on producing effective research objectives and making sure every part of our research plan maps to a suitable objective.
The concept of research planning can be met with mixed emotions. Some may say that planning delays action. However, a good plan should really do the opposite by providing a clear guide for action and deliverables. In this post, we’ll detail how a well-conceived UX research plan will help streamline your research and foster understanding and engagement from all stakeholders involved.
A UX research plan can take many forms. It can be a document, spreadsheet, set of slides, or anything else you can imagine as long as it acts as an overview for kicking off the project.
While a UX research plan doesn’t have to be a formal document, it shouldn’t only live in the mind of a single person. Consolidating ideas, milestones, and deliverables together in one, accessible place allows for a guided conversation that has major benefits on the outcomes of a set of research.
When it comes to user research, it may seem daunting to be too prescriptive when building your UX research plan. After all, how can you account for everything a user might need, say, or want? Nonetheless, it’s important to try, because making progress on your goals is rarely made through random activity. And, there’s nothing wrong with making adjustments as you go.
Even when faced with uncertainty—often compounded by the everchanging world we live in—effective planning facilitates progress.
The benefits of a UX research plan are numerous, but some include:
Every organization is different, so the teams within them may be responsible for different business goals. This means that there isn’t a one-size-fits-all approach to creating a UX research plan.
In this section, we’ll provide an overview of steps to consider when creating your plan.
A well-oiled UX research plan should include:
Let’s get started.
As with most plans, you should start by clearly identifying and stating the problem that you’re trying to solve. A UX research plan is no different. Your problem statement should be clear, specific, and give enough detail that stakeholders understand what the research is trying to solve.
Problem statements don’t just stem from nowhere. Some great sources for inspiration might be your support team which deals with customer issues on a daily basis, customer reviews on your website, or feedback from social media. Understanding what data already exists—and what you still need to know—is a fantastic starting point for building a strong UX research plan. Let's take a closer look at some of the steps involved in creating a great problem statement:
Begin by articulating the issue in a manner that is concise yet comprehensive. A well-crafted problem statement should communicate the essence of the issue succinctly, making it immediately apparent to all stakeholders what the research will address. It’s important that this statement avoids generalities and is rooted in specific user experiences or observed difficulties. For example, instead of saying "improve website navigation," specify "users are struggling to locate the search function on the homepage, which is impacting conversion rates."
Before formalizing your problem statement, gather preliminary data to understand the context better. Chat to your customer support team to identify common complaints or challenges users face. Review customer feedback collected through surveys, feedback forms on your website, or direct interactions. Social media platforms can also be a goldmine of user opinions and issues, often providing raw, unfiltered feedback on what users like or struggle with regarding your product or service.
Analyze the data you’ve gathered to detect patterns or recurring themes. This analysis might reveal that users feel a particular feature is too complicated or that there are barriers to completing a purchase. Such insights help refine your problem statement by focusing on specific user challenges that your research needs to address.
With a clear understanding of user challenges, refine your problem statement to reflect these specifics. Ensure it encapsulates the user's perspective, focusing on their experiences and the difficulties they encounter. For instance, if users find an application form daunting due to its length and complexity, your problem statement could be, "Users are abandoning the application form because its length and complex questions create a perception that the process is tedious and time-consuming."
Ensure your problem statement communicates why addressing this issue is crucial for the business or product. Link the problem directly to business outcomes, such as improved user satisfaction, increased sales, or reduced customer churn. This not only highlights the importance of the research but also aligns it with broader business goals, facilitating stakeholder buy-in.
Once you have a draft, share it with key stakeholders—include team members from design, development, marketing, customer service etc. This will help provide new insights, validate the problem’s relevance, and make sure it resonates across all areas of the business. This feedback might prompt revisions that make the statement more inclusives and more robust.
Once you've used that feedback to refine your problem statement, you'll have a well-defined statement that will lead to powerful and useful reseaarch insights.
Once you’ve put together your problem statement, it’s time to define your objectives.
Think about defining your objectives as telling the story of what you’re doing, why you’re doing it, and what you expect to learn from your UX research . The objectives you set should be the driving force behind every task you assign and every question that you ask research participants.
This means it’s important to be specific. Setting clear objectives will help you define the project scope and the questions you have to ask participants to get the information you need. If the scope is too broad, anything and everything becomes a research question—which becomes overwhelming to manage.
If you like to think visually, consider this chart.
A well-defined objective keeps you from falling into the rabbit hole of scope creep. Without specific targets, your project can easily grow unwieldy, trying to cover too much ground and diluting the impact of your findings. To avoid this, break down large goals into smaller, focused tasks that you can tackle effectively. For instance, if improving website navigation is your goal, you could focus specifically on enhancing the visibility of the main menu, reducing clicks to reach key content, or improving search functionality.
To make your objectives really work for you, frame them using the SMART criteria—Specific, Measurable, Achievable, Relevant, and Time-bound. Here’s how you might apply these to a UX project:
Objectives aren’t set in stone. As you dive into your research and start gathering data, be ready to tweak and refine your objectives based on what you learn. UX research is inherently iterative, and being flexible allows you to pivot as you uncover new insights or face unexpected challenges. Regularly revisiting your objectives ensures your research stays relevant and aligned with both user needs and business priorities.
By keeping your objectives clear and focused, you make sure that your UX research is effective, impactful, and tightly connected to enhancing user experience. This isn't just about sticking to a plan—it's about making the plan work hard for you, every step of the way.
Start with a problem statement, define the objectives you need to address the problem, then build out tasks and questions that will uncover the necessary information from your participants.
Once you have a clear understanding of what your problem is and how you’re going to aim to solve it, you’ll need to choose the right research method for your plan.
Next, you'll have to choose the research method that will achieve your stated goals—based on the objectives you've already identified. Before we jump into individual research methods, or the tactics used for conducting UX research, there are big-picture questions that need to be addressed first. And that’s: What types of UX research are there?
We won’t dive too deep into this here, but here’s some additional reading that might help you understand the type of research you’ll need to conduct:
Now that you’ve got a lay of the land, it’s time to match your research method to your project goals. Here’s how you can ensure the method you pick will deliver the goods:
Often, no single method will tell the whole story. Consider using a mix of approaches to get both the depth and breadth of insights you need. For instance, you might start with a survey to get a general sense of user satisfaction and follow up with interviews to dive deeper into specific issues highlighted by the survey results.Once you understand the types of results you're trying to achieve, make sure that the research method you choose delivers the evidence you need to make informed decisions.
Related reading: The UX research methodology guidebook
One of the most important factors that contribute to a successful UX research plan lies in choosing the right participants (and the right number of them). There’s some debate out there over how many participants you should include in UX research, and the right answer depends on what you’re trying to learn.
Figuring out the right number of participants Let’s unpack this a bit:
Selecting the right participants is more than just filling seats—it’s about ensuring that every voice you hear from can directly contribute to richer, more actionable insights. So take your time, think it through, and choose wisely to make your UX research as impactful as possible.
Finally, make sure they’re a good fit for what you’re trying to learn:
Finding these people and convincing them to take part in your study is next on the agenda. Here are a few strategies:
But it’s not just about numbers. Who these people are matters a ton. Here’s how to get the right mix:
Defining who your participants should be will require you to go back to the goals you’ve set and the questions that need answering.
There's a certain art to crafting a great test plan. Admittedly, it can take a bit of practice. From moderated user interviews to unmoderated usability tests to prototyping—test plans can take many different shapes and sizes. Lucky for you, our education and research teams have come together to build out this outstanding resource for building test plans.
Check out all of our articles on the UserTesting Knowledgebase for building a test plan .
Establishing your research project’s timeline is an essential step in creating a UX research plan. Estimating how long the research project will take place and when the findings could be expected are necessary considerations in any project.
Even if not exact, determining an approximate timeline (e.g., 2-3 weeks) will enable you to manage stakeholders’ expectations of the process and the results.
Let’s dive into how to effectively map out the time your research will take and when you can expect to roll out the findings.
Here’s how you can approach it:
While it’s great to have a timeline, it’s also important to stay flexible:
An accurate timeline helps in setting and managing expectations:
Locking in a timeline isn’t just about sticking to dates. It’s about creating a structured approach to your research that allows for informed planning, anticipates adjustments, and aligns with the broader goals of your project. By taking the time to map out each phase and communicate this effectively, you ensure that your UX research delivers valuable insights in a timely and efficient manner.
Finally, determining how you’ll present the findings of your project from the start ensures they will be impactful and implemented across the organization. Setting this understanding from the beginning will also determine if all of your stakeholders have been properly identified. It can be frustrating to find out that you need to present to an executive halfway through a project.
Ultimately, for the purpose of your UX research plan, it’s important to choose a presentation medium that’s appropriate for your key stakeholders. Perhaps it’s a UX research report , a set of slides, or even a Jira ticket for your product team; the point is, you want to deliver the information to stakeholders in a way they’re comfortable with—and will be most receptive to.
So now you’ve built a UX research plan from scratch. While it may seem like an arduous process, we can assure you that it’s well worth your time. Being able to confidently embark on a project with clear deliverables, milestones, stakeholder buy-in, and a plan for presenting results is a major feat—one that will be recognized and appreciated by all of those involved.
Nevertheless, time is money. So once you’ve gone through an entire UX research project, we encourage you to hold a retrospective meeting to identify all the ways you could improve the process. Once you uncover what went well and what can be improved, turn your UX research plan into a template for you and your peers to leverage within your organization.
Need some inspiration for your next UX research project? Check out our list of curated test templates to get you started.
Get started now
About the author(s).
Steven is a Marketing Content Strategist. When he’s not inserting oxford commas where they belong, you can find him shooting pool at a local dive or building killer playlists on Spotify.
Human understanding. Human experiences.
Oh no! We're unable to display this form.
Please check that you’re not running an adblocker and if you are please whitelist usertesting.com.
If you’re still having problems please drop us an email .
By submitting the form, I agree to the Privacy Policy and Terms of Use .
Integrations
What's new?
In-Product Prompts
Participant Management
Interview Studies
Prototype Testing
Card Sorting
Tree Testing
Live Website Testing
Automated Reports
Templates Gallery
Choose from our library of pre-built mazes to copy, customize, and share with your own users
Browse all templates
Financial Services
Tech & Software
Product Designers
Product Managers
User Researchers
By use case
Concept & Idea Validation
Wireframe & Usability Test
Content & Copy Testing
Feedback & Satisfaction
Content Hub
Educational resources for product, research and design teams
Explore all resources
Question Bank
Research Maturity Model
Guides & Reports
Help Center
Future of User Research Report
The Optimal Path Podcast
Maze Guides | Resources Hub
0% complete
Conducting UX research without a plan is like moving to another country without knowing the language—confusing and exhausting.
To avoid wasting time and resources, it’s crucial to set achievable research goals and work on developing a research plan that’s clear, comprehensive, and aligned with your overarching business goals and research strategy.
A good UX research plan sets out the parameters for your research, and guides how you’ll gather insights to inform product development. In this chapter, we share a step-by-step guide to creating a research plan, including templates and tactics for you to try. You’ll also find expert tips from Paige Bennett, Senior User Research Manager at Affirm, and Sinéad Davis Cochrane, Research Manager at Workday.
A UX research plan—not to be confused with a UX research strategy or research design—is a plan to guide individual user experience (UX) research projects.
It's a living document that includes a detailed explanation of tactics, methods, timeline, scope, and task owners. It should be co-created and shared with key stakeholders, so everyone is familiar with the project plan, and product teams can meet strategic goals.
A UX research plan is different to a research strategy and research design in both its purpose and contents. Let’s take a look.
While your UX research plan should be based on strategy, it’s not the same thing. Your UX strategy is a high-level document that contains goals, budget, vision, and expectations. Meanwhile, a plan is a detailed document explaining how the team will achieve those strategic goals. Research design is the form your research itself takes.
In short, a strategy is a guide, a plan is what drives action, and design is the action itself.
Research design | to be employed and specifics on how they’ll be used in the study (e.g., qualitative interviews, quantitative surveys, experimental trials) that will assist in data collection (sampling size) and how they will be selected | |
---|---|---|
Research plan | or goals of the research that will be used to gather and analyze data of the project (like budget and personnel) required | |
Research strategy |
Conducting research without goals and parameters is aimless. A UX research plan is beneficial for your product, user, and business—by building a plan for conducting UX research, you can:
Work toward specific, measurable goals, align and engage stakeholders, save time by avoiding rework.
The structure of a research plan allows you to set timelines, expectations, and task owners, so everyone on your team is aligned and empowered to make decisions. Since there’s no second guessing what to do next or which methods to use, you’ll find your process becomes simpler and more efficient. It’s also worth standardizing your process to turn your plan into a template that you can reuse for future projects.
When you set research goals based on strategy, you’ll find it easier to track your team’s progress and keep the project in scope, on time, and on budget. With a solid, strategy-based UX research plan you can also track metrics at different stages of the project and adjust future tactics to get better research findings.
“It’s important to make sure your stakeholders are on the same page with regards to scope, timeline, and goals before you start," explains Paige Bennett, Senior User Research Manager at Affirm. That's because, when stakeholders are aligned, they're much more likely to sign off on product changes that result from UX research.
A written plan is a collaborative way to involve stakeholders in your research and turn them into active participants rather than passive observers. As they get involved, they'll make useful contributions and get a better understanding of your goals.
A UX research plan helps you save time and money quite simply because it’s easier and less expensive to make design or prototype changes than it is to fix usability issues once the product is coded or fully launched. Additionally, having a plan gives your team direction, which means they won’t be conducting research and talking to users without motive, and you’ll be making better use of your resources. What’s more, when everyone is aligned on goals, they’re empowered to make informed decisions instead of waiting for their managers’ approval.
In French cuisine, the concept of mise en place—putting in place—allows chefs to plan and set up their workspace with all the required ingredients before cooking. Think of your research plan like this—laying out the key steps you need to go through during research, to help you run a successful and more efficient study.
Here’s what you should include in a UX research plan:
Use Maze to run quantitative and qualitative research, influence product design, and shape user-centered products.
Now we’ve talked through why you need a research plan, let’s get into the how. Here’s a short step-by-step guide on how to write a research plan that will drive results.
One of the most important purposes of a research plan is to identify what you’re trying to achieve with the research, and clarify the problem statement. For Paige Bennett , Senior User Research Manager at Affirm, this process begins by sitting together with stakeholders and looking at the problem space.
“We do an exercise called FOG, which stands for ‘Fact, Observation, Guess’, to identify large gaps in knowledge,” says Paige. “Evaluating what you know illuminates questions you still have, which then serves as the foundation of the UX research project.”
You can use different techniques to identify the problem statement, such as stakeholder interviews, team sessions, or analysis of customer feedback. The problem statement should explain what the project is about—helping to define the research scope with clear deliverables and objectives.
Research objectives need to align with the UX strategy and broader business goals, but you also need to define specific targets to achieve within the research itself—whether that’s understanding a specific problem, or measuring usability metrics . So, before you get into a room with your users and customers, “Think about the research objectives: what you’re doing, why you’re doing it, and what you expect from the UX research process ,” explains Sinéad Davis Cochrane , Research Manager at Workday.
Examples of research objectives might be:
A valuable purpose of setting objectives is ensuring your project doesn't suffer from scope creep. This can happen when stakeholders see your research as an opportunity to ask any question. As a researcher , Sinéad believes your objectives can guide the type of research questions you ask and give your research more focus. Otherwise, anything and everything becomes a research question—which will confuse your findings and be overwhelming to manage.
Sinéad shares a list of questions you should ask yourself and the research team to help set objectives:
Another useful exercise to help identify research objectives is by asking questions that help you get to the core of a problem. Ask these types of questions before starting the planning process:
It’s good practice to involve stakeholders at early stages of plan creation to get everyone on board. Sharing your UX research plan with relevant stakeholders means you can gather context, adjust based on comments, and gauge what’s truly important to them. When you present the research plan to key stakeholders, remember to align on the scope of research, and how and when you’ll get back to them with results.
Stakeholders usually have a unique vision of the product, and it’s crucial that you’re able to capture it early on—this doesn’t mean saying yes to everything, but listening to their ideas and having a conversation. Seeing the UX research plan as a living document makes it much easier to edit based on team comments. Plus, the more you listen to other ideas, the easier it will be to evangelize research and get stakeholder buy-in by helping them see the value behind it.
I expect my stakeholders to be participants, and I outline how I expect that to happen. That includes observing interviews, participating in synthesis exercises, or co-presenting research recommendations.
Paige Bennett , Senior User Research Manager at Affirm
Choose between the different UX research methods to capture different insights from users.
To define the research methods you’ll use, circle back to your research objectives, what stage of the product development process you’re in, and the constraints, resources, and timeline of the project. It’s good research practice to use a mix of different methods to get a more complete perspective of users’ struggles.
For example, if you’re at the start of the design process, a generative research method such as user interviews or field studies will help you generate new insights about the target audience. Or, if you need to evaluate how a new design performs with users, you can run usability tests to get actionable feedback.
It’s also good practice to mix methods that drive quantitative and qualitative results so you can understand context, and catch the user sentiment behind a metric. For instance, if during a remote usability test, you hear a user go ‘Ugh! Where’s the sign up button?’ you’ll get a broader perspective than if you were just reviewing the number of clicks on the same test task.
Examples of UX research methods to consider include:
Check out our top UX research templates . Use them as a shortcut to get started on your research.
Every research plan should include information about the participants you need for your study, and how you’ll recruit them. To identify your perfect candidate, revisit your goals and the questions that need answering, then build a target user persona including key demographics and use cases. Consider the resources you have available already, by asking yourself:
When selecting participants, make sure they represent all your target personas. If different types of people will be using a certain product, you need to make sure that the people you research represent these personas. This means not just being inclusive in your recruitment, but considering secondary personas—the people who may not be your target user base, but interact with your product incidentally.
You should also consider recruiting research participants to test the product on different devices. Paige explains: “If prior research has shown that behavior differs greatly between those who use a product on their phone versus their tablet, I need to better understand those differences—so I’m going to make sure my participants include people who have used a product on both devices.”
During this step, make sure to include information about the required number of participants, how you’ll get them to participate, and how much time you need per user. The main ways to recruit testers are:
You should always reward your test participants for their time and insights. Not only because it’s the right thing to do, but also because if they have an incentive they’re more likely to give you complete and insightful answers. If you’re hosting the studies in person, you’ll also need to cover your participants' travel expenses and secure a research space. Running remote moderated or unmoderated research is often considered to be less expensive and faster to complete.
If you’re testing an international audience, remember to check your proposed payment system works worldwide—this might be an Amazon gift card or prepaid Visa cards.
The next component of a research plan is to create a brief or guide for your research sessions. The kind of brief you need will vary depending on your research method, but for moderated methods like user interviews, field studies, or focus groups, you’ll need a detailed guide and script. The brief is there to remind you which questions to ask and keep the sessions on track.
Your script should cover:
It’s crucial you remember to ask participants for their consent. You should do this at the beginning of the test by asking if they’re okay with you recording the session. Use this space to lay out any compensation agreements as well. Then, ask again at the end of the session if they agree with you keeping the results and using the data for research purposes. If possible, explain exactly what you’ll do with their data. Double check and get your legal team’s sign-off on these forms.
Next in your plan, estimate how long the research project will take and when you should expect to review the findings. Even if not exact, determining an approximate timeline (e.g., two-three weeks) will enable you to manage stakeholders’ expectations of the process and results.
Many people believe UX research is a lengthy process, so they skip it. When you set up a timeline and get stakeholders aligned with it, you can debunk assumptions and put stakeholders’ minds at ease. Plus, if you’re using a product discovery tool like Maze, you can get answers to your tests within days.
When it comes to sharing your findings with your team, presentation matters. You need to make a clear presentation and demonstrate how user insights will influence design and development. If you’ve conducted UX research in the past, share data that proves how implementing user insights has improved product adoption.
Examples of ways you can present your results include:
In your plan, mention how you’ll share insights with the product team. For example, if you’re using Maze, you can start by emailing everyone the ready-to-share report and setting up a meeting with the team to identify how to bring those insights to life. This is key, because your research should be the guiding light for new products or updates, if you want to keep development user-centric. Taking care over how you present your findings will impact whether they’re taken seriously and implemented by other stakeholders.
Whether you’re creating the plan yourself or delegating to your team, a clear UX research plan template cuts your prep time in half.
Find our customizable free UX research plan template here , and keep reading for a filled-in example.
Now, let’s go through how to fill out this template and create a UX research plan with an example.
Flows aims to increase user adoption and tool engagement by 30% within the next 12 months. Our B2B project management software has been on the market for 3 years and has 25,000 active users across various industries.
By researching the current product experience with existing users, we’ll learn what works and what doesn’t in order to make adjustments to the product and experience.
Objective | Description |
---|---|
Objective 1 | Identify pain points and areas of friction in the current user experience that stop adoption and engagement |
Objective 2 | Understand how team members currently use the tool to manage projects and collaborate |
Objective 3 | Explore desired features, integrations, and capabilities to enhance productivity and team effectiveness |
The purpose is to gather actionable insights into user needs, behaviors, and challenges to inform updates that will drive increased adoption and engagement of 30% for the B2B project management tool within 12 months.
Characteristic | Details |
---|---|
Target audience | Current customers (teams) using the project management tool |
Sample size | 20 teams across different client accounts |
Scope | Full user experience from onboarding to daily use across all tool features |
Demographics | Teams of 5-15 members from industries like software, marketing, construction, and consulting |
Deliverable | Description | Deadline |
---|---|---|
Deliverable 1 | User journey maps highlighting friction points | 3 weeks after research study completion |
Deliverable 2 | Competitive analysis report | 4 weeks |
Deliverable 3 | Prioritized feature roadmap | 5 weeks |
Deliverable 4 | Final report with key findings and recommendations | 6 weeks |
Method | Reason |
---|---|
Behavioural analytics | Review product stats to uncover friction points that can inform following research |
Contextual inquiries (8 teams*): | Observe teams using the tool in their workspace |
User interviews (12 teams*) | 60-min semi-structured interviews |
Usability testing (5 teams*) | Unmoderated remote usability tests |
*Some teams will take part in more than one research session.
We are doing a mixed methods study.
User interviews are our primary method for gathering qualitative data, and will be analyzed using thematic analysis .
User interview questions:
Total estimated budget: $8,000
Item | Estimated costs | Notes |
---|---|---|
Participant incentives | $4,000 | |
Remote usability testing platform | $1,000 | |
Research tools & software | $3,000 |
Whether you’re creating the plan yourself or are delegating this responsibility to your team, here are six research templates to get started:
We all know that a robust plan is essential for conducting successful UX research. But, in case you want a quick refresher on what we’ve covered:
UX research can happen at any stage of the development lifecycle. When you build products with and for users, you need to include them continuously at various stages of the process.
It’s helpful to explore the need for continuous discovery in your UX research plan and look for a tool like Maze that simplifies the process for you. We’ll cover more about the different research methods and UX research tools in the upcoming chapters—ready to go?
Discover how Maze can streamline and operationalize your research plans to drive real product innovation while saving on costs.
What’s the difference between a UX research plan and a UX research strategy?
The difference between a UX research plan and a UX research strategy is that they cover different levels of scope and detail. A UX research plan is a document that guides individual user experience (UX) research projects. UX research plans are shared documents that everyone on the product team can and should be familiar with. A UX research strategy, on the other hand, outlines the high-level goals, expectations, and demographics of the organization’s approach to research.
What should you include in a user research plan?
Here’s what to include in a user research plan:
How do you write a research plan for UX design?
Creating a research plan for user experience (UX) requires a clear problem statement and objectives, choosing the right research method, recruiting participants and briefing them, and establishing a timeline for your project. You'll also need to plan how you'll analyze and present your findings.
How do you plan a UX research roadmap?
To plan a UX research roadmap, start by identifying key business goals and user needs. Align research activities with product milestones to ensure timely insights. Prioritize research methods—like surveys, interviews, and usability tests—based on the project phase and objectives. Set clear timelines and allocate resources accordingly. Regularly update stakeholders on progress and integrate feedback to refine the roadmap continuously.
Generative Research: Definition, Methods, and Examples
Create a strong business case for UX research and streamline your process with the UX research plan template.
Trusted by 65M+ users and leading companies
A UX research plan, also known as a user research plan, is a brief reference document that outlines your research project’s goals, key contributors, important dates, and timelines.
Think of your research plan as a UX-focused kick-off document for your project. The plan offers an overview of the research initiative, encourages well-defined and agreed-upon goals, and acts as a written guarantee that the research will meet these goals.
When conducting usability testing or user research with a goal in mind, researchers need to plan. UX researchers often present their findings to stakeholders, like product managers, developers, marketers, and executives, to act on those results.
You should present your UX research plan in plain language with a single document. Keep your findings clear, collaborative, easily accessed, and digestible to get buy-in for your research and your team’s next steps.
A user research plan typically has up to seven segments:
Project background: Reasons for the study and internal stakeholders involved.
Research goals and objectives: What your teams want to learn, or their ideal research outcome.
Research participants: Who they are and how they’ll be recruited.
Method: How you conducted research, and any other information about how the research will be conducted.
Guides: An interview guide or cheat sheet of instructions and questions to follow during the session.
Duration: A rough timeline of how long the research will take and when the team can review the report.
Other helpful information: Additional resources for your team, such as previous studies, scripts, or results, can inform this new round of research.
Research plans keep your team focused on outcomes rather than getting lost in the details or changing the research goal midway through the project. By the end of the project, UX researchers should feel confident that their questions were answered and presented in both the plan and actual research.
UX research plans are useful for teams who need to decide on questions such as:
What do our customers need? Who is our target persona?
Does the proposed or current design work well for our customers? How can we make it better?
Planning UX research also gives researchers an opportunity to:
Decide what works for your stakeholders, especially the questions they’re trying to answer.
Engage stakeholders and keep them invested in your research results.
Clarify your ideas, problems to be solved, and research approaches.
Treat your research plan as a blueprint for aligning expectations, asking for feedback, or generating enthusiasm and support for increasing the value of user research in your organization.
Making your own UX research plans is easy, and Miro is the perfect tool to create and share them. Get started by selecting the UX research plan template, then take the following steps to make one of your own.
Give your team or stakeholders a quick project introduction. You can hop on a video chat with up to 25 team members and remind everyone what you’re trying to achieve. Remember that research proves its value when it satisfies a single objective rather than many. If you seem to have lots of different goals or objectives, avoid overreaching and start fresh: what’s the one customer problem and business problem you’re trying to solve?
Define the user and business problems your research needs to solve. The default sticky notes are simply for inspiration — feel free to edit each of these to fix your own context. If you want your team to focus on this area instead of skipping ahead, you can select the “problem” frame and click the “hide frame” (closed eye) icon that appears in the frame’s menu.
Define your research goals. Ask your team to brainstorm their top three research goals or priorities. Remember that the best research sessions are chasing a single objective, so out of the two to three you note down, ask your team to vote for their preferences. Try Miro’s Voting Plugin to help your team reach a decision.
Draft your research questions. Pick three to five questions with your team or stakeholders that are most important to your research. Aim for no more than 10. The more focused your questions, the more focused your research will be.
Link to useful supporting information as needed. Keep this plan to the point in order to get buy-in. For stakeholders who need more detail, there may be other useful data to link to. If you have previous UX research results or relevant studies, link to them on your Miro Board. You can also import survey data, embed tables and charts , or link sticky notes to external sources .
Dive even deeper into how to conduct UX research – and see examples – in our expert guide to user research .
Centralized planning: Centralize your UX research plans in one shared space. This ensures that all relevant information, including research objectives, methodologies, and timelines, is easily accessible in one place, reducing the risk of scattered or lost documentation.
Collaborative research: Multiple stakeholders, including designers, researchers, and product managers, can collaborate on your UX research plan template simultaneously, fostering a more inclusive and collaborative approach to research planning.
Visual representation of research steps: Create diagrams, flowcharts, and visual representations of the research process. This visual mapping helps teams better understand the sequence of research activities, identify dependencies, and effectively communicate the overall research strategy.
Iterative refinement: Provide feedback, comments, and suggestions directly on the UX research plan template. Promote continuous improvement, allowing the team to refine the research plan based on insights and changing project requirements.
Integration with user flows and personas: Integrate with other templates, such as user flows and persona maps. By connecting these elements, teams can create a holistic view of the user experience journey. This integration helps align research activities with the overall UX strategy and ensures a more cohesive and user-centric product design.
Regularly review and update the research plan as project requirements evolve. It's crucial to stay flexible and adapt the plan based on the findings and changing project needs.
Get started with this template right now.
Works best for:.
Business Management, Ideation, Brainstorming
Know who knew a little something about coming up with ideas that set imaginations alight? Walt Disney. And he inspired the Disney Creative Strategy, an approach that establishes three types of thinkers—dreamers, realists, and critics—and gives each the space to do clear thinking. Your team will go through an engaging exercise of adopting the three mindsets, where they’ll focus on a specific aspect of the idea. The Disney Creative Strategy has a way of yielding brilliant ideas and great products. That’s why it’s used successfully by organizations of all kinds and sizes.
Education, Team Meetings, Workshops
Breakout groups provide an excellent opportunity for teammates to have candid conversations and connect on a more intimate level than is possible during a broader meeting. When you’re in a large group setting, it can be difficult for people to feel safe or comfortable speaking up. In a smaller group, participants can feel safer sharing their ideas. Since the group is more intimate, teams are empowered to participate rather than observe.
Desk Research, Product Management, Prioritization
When it comes down to it, a product’s success is determined by the features it offers and the satisfaction it gives to customers. So which features matter most? The Kano model will help you decide. It’s a simple, powerful method for helping you prioritize all your features — by comparing how much satisfaction a feature will deliver to what it will cost to implement. This template lets you easily create a standard Kano model, with two axes (satisfaction and functionality) creating a quadrant with four values: attractive, performance, indifferent, and must-be.
Prioritization, Strategic Planning, Project Management
Setting goals can be encouraging, but can also be overwhelming. It can be hard to conceptualize every step you need to take to achieve a goal, which makes it easy to set goals that are too broad or too much of a stretch. SMART is a framework that allows you to establish goals in a way that sets you up for success. SMART stands for Specific, Measurable, Attainable, Relevant, and Timely. If you keep these attributes in mind whenever you set goals, then you’ll ensure your objectives are clear and reachable. Your team can use the SMART model anytime you want to set goals. You can also use SMART whenever you want to reevaluate and refine those goals.
Education, Desk Research, Product Management
Teams often need to document findings from usability testing sessions and customer interviews into a systematic, flexible user research template. Collecting everyone’s observations into a centralized location makes it easier to share insights company-wide and suggest new features based on user needs. Research templates can be used to record quantitative or qualitative data.. When it’s your job to ask questions, take notes, learn more about your user, and test iteratively, a Research Template can help you validate your assumptions, find similarities across different users, and articulate their mental models, needs, and goals.
Market Research, Research & Design
The Empathy Map Canvas is a versatile tool for visualizing user behavior and emotions. It helps teams capture insights about what users see, hear, think, and feel. Use this template to build empathy and ensure your product meets real user needs.
Are you an agency specialized in UX, digital marketing, or growth? Join our Partner Program
Learn / Guides / UX research guide
Back to guides
After a lengthy planning and designing process, you’ve turned your website or app vision into a reality. But maybe you've noticed that despite its visual appeal, conversions are low while bounce rates keep soaring. Often, a poor user experience (UX) is to blame, affecting your brand perceptions and customer conversions.
Reading time.
So, how can you create a frictionless, user-centric experience? Strong UX research and smart use of UX research tools are key.
While the research process can be a challenge, analyzing how other brands have successfully conducted UX research can inspire your own approach. This article dives into seven detailed case studies and shows you how to use UX research tools to identify and solve UX challenges and delight your customers.
Use Hotjar for effective end-to-end UX research campaigns that help you deeply understand user needs
UX research is the strategic process of analyzing target users to understand their needs, behavior, and experience. Teams use UX research, feedback tools, and experimentation techniques to collect contextual insights.
Then, they translate these insights into a user-centric design that generates strong conversions and higher user retention rates.
UX research offers several other benefits, including:
Helping create customer delight: by understanding how users behave, you can design your product more accessibly and empathetically. UX research equips teams to create tailored experiences, maximizing customer satisfaction and improving product experience (PX).
Replacing guesswork with data-driven insights : UX research involves collecting and assessing qualitative and quantitative data to make decisions based on comprehensive insights, rather than gut feelings.
Providing insight into the user’s needs : the better you know your audience's pain points, the better you can design a product that truly addresses their needs. UX research tells you exactly where your users struggle—so you can come up with solutions.
Helping you achieve critical KPIs : research methods like concept validation and user feedback ensure every iteration moves you toward better user engagement, conversions, increased retention, and reduced churn, positively impacting your revenue.
The benefits of UX research are clear. So when should you start the process?
Since you are creating a product for someone else and not for yourself, any time is good to start UX research. The beginning doesn't have to be sophisticated. It can start simple and evolve, adapting to the amount/complexity of the questions about the users and the resources of your business.
You only need curiosity, some time, and a willingness to base your product on facts and not assumptions.
Let’s take a look at how seven companies aced UX research and produced incredible results.
UX research offers you opportunities for conversion rate optimization and personalization that can significantly increase business growth and enhance customer satisfaction.
Contrary to popular belief, you don’t always need a dedicated UX research team: a cost-effective tech stack can do most of the heavy lifting. Product experience insights tools like Hotjar help you assess your users’ experience, measure their behavior, and garner constructive feedback for UX analysis .
Here are seven examples of great UX research with the help of product experience insights tools to get you inspired.
Zenprint provides order and wholesale digital printing services in the Australian market.
Zenprint’s biggest challenge was identifying factors leading to drop-offs on their website. The brand’s marketing team struggled to figure out:
Where people spent their time
What users were interested in
What caused them to drop off
They wanted actionable insights into how users interacted with their site .
Zenprint’s marketing team leveraged Hotjar (👋) to analyze web performance and understand user behavior at a granular level. They used:
Funnels to locate the exact drop-off points in the customer journey
Session Recordings to understand how each user behaved on the site, tracing mouse and scroll movements to see which elements users click on
Heatmaps to view color-coded representations of popular and unpopular site elements to help discover areas where users spend the most time and determine those that need improvement
This action plan helped the team zero in on their pricing table as a major blocker.
Once Zenprint identified the problem, the next step was split testing multiple layouts to optimize the pricing table. With a simple change in their pricing plan, the Zenprint team reduced drop-off rates by 7% and boosted its conversion rate by 2%.
For stellar UX research, collect real-time insights from users across different stages of the conversion funnel to identify bottlenecks. Supplement quantitative analytics with qualitative feedback by analyzing Hotjar Recordings and Heatmaps to understand user behavior.
Matalan is a British fashion and homeware retail and ecommerce brand.
Without qualitative UX research to interpret data points, Matalan's UX team was forced to make decisions based on gut feelings, relying on quantitative data alone, which gave them limited visibility. The checkout process was showing high drop-offs and they weren’t sure why.
When Matalan migrated to a responsive website, its UX team used Hotjar to record and assess user responses to this change, and compare performance through A/B testing. They also viewed Session Recordings that flagged bugs and glitches early in the migration process.
They used Hotjar's Feedback tools to collect user feedback in real-time to capture the customer’s voice and make product changes to improve the user experience. Combined with user recordings, these provided a complete overview of the user journey, which helped eliminate areas of friction.
Using recordings to closely monitor user behavior, Matalan optimized its checkout process and increased conversions by 1.23%.
They created a bespoke experience dashboard by combining qualitative insights gathered by Hotjar with Google Data Studio analytics for a comprehensive UX research process.
Instead of relying solely on numbers, collect user perspectives to add depth to your UX research . This concrete feedback can make your team aware of flaws in the user experience so you can proactively offer fixes.
Materials Market is a UK-based marketplace for construction material manufacturers and customers.
Materials Market’s co-founder wanted to optimize their website experience by improving three problem areas:
Poorly placed calls to action (CTAs), where mobile users couldn’t see the CTA clearly enough to click on it
Customer drop-offs at the checkout step because users only wanted to check the delivery time
A complicated cookie policy that caused visitors to bounce as soon as they landed on the website
Materials Market used Hotjar Recordings and Heatmaps to dig deeper into these UX research issues . The result was a gradual upgrade of the website to meet—and exceed—customer expectations. Here’s what happened:
They improved the visibility of CTAs with changes to font, color, and design. The team also included a rating widget next to the CTAs to display social proof.
They removed the need to set up an account to place an order and added an estimated delivery date for every product
They implemented design changes in the cookie policy pop-up to make it 30% bigger with better color and copy. They also placed the banner on the top of the page.
Redesigning the checkout flow decreased drop-offs by 86%. On the flip side, the conversion rate more than tripled to 1.6% —massively boosting yearly revenue by more than £10,000.
UX research tools like recordings are a great way to understand user behavior on your website—you can sort and filter recordings with Hotjar by relevance. This can boost your UX research efforts without relying heavily on technical expertise and development knowledge.
Totally Promotional is a US-based manufacturer and retailer that produces customized promotional products for brands.
Totally Promotional wanted to evaluate on-site user behavior and improve the brand's UX quality but was struggling to collect meaningful user data that offered a complete insight into the user experience.
Relying on Google Analytics alone, the team lacked qualitative feedback to interpret customer needs and design empathetically.
The team added Hotjar to its tech stack to get a better view of user interaction and web experience. They used Hotjar Heatmaps to assess where users spent their time and dropped off—identifying underperforming pages and bugs.
Hotjar’s Feedback and Survey tools were useful in capturing Voice of the Customer (VoC) insights, allowing Totally Promotional to examine why users behaved the way they did. They also watched Session Recordings to pinpoint where buyers felt stuck in the order process.
This mix of UX research tools removed the guesswork from Totally Promotional’s website optimization process. The team took an evidence-based approach and incorporated both minor tweaks and significant updates in the ecommerce storefront design.
However, the most crucial action they took was changing the order process for their branded pens page, which tripled sales for this product.
Behavioral data and user perspectives are both necessary for excellent UX research. Intuitive tools like Hotjar’s Feedback widget can help you collate meaningful information to supercharge your UX research campaign and implement strategic website changes.
Hussle is a subscription-based network of gyms, spas, and digital fitness solutions.
Hussle’s biggest challenge was high customer churn: the brand’s product team wanted to better understand why this was happening and deploy UX research to reduce churn with an unparalleled product experience.
Hussle’s team leveraged Surveys and Recordings to find answers as to why users were leaving.
It turned out there were three core reasons behind churn:
High subscription cost
Changes in the user’s location
Purchase of direct gym membership
Deploying UX research tools to understand churn led to an improved UX and user interface and boosted Hussle’s growth. The team saw great results, including:
A preemptive bug fix that would’ve hindered the buying process
Streamlined the bug-fixing process by detecting and deleting at least one bug weekly
Gathered meaningful insights from users through 1000+ survey responses and over 73,000 seconds of Hotjar Session Recordings
The team has continued to use Session Recordings and Heatmaps to stay one step ahead—whether detecting bugs or finding where users get stuck.
User feedback is a great way to understand the reasons behind churn so you can address them and improve retention . Additionally, you can also gather data to proactively fix bugs and improve UX.
Turum-burum is a digital UX design agency that provides conversion rate optimization strategies for clients like Intertop, one of Ukraine's biggest shoe retailers.
Intertop saw a rapid increase in traffic on their website and used Turum-burum’s services to maximize conversions from this influx of visitors. They used UX research to address three crucial challenges:
Simplifying and enhancing the customer journey once a visitor lands on Intertop’s homepage
Testing and implementing UX changes as quickly as possible
Anticipating and mitigating any potential risks resulting from UX changes
Using Hotjar’s exit-intent Surveys , the Turum-burum team identified a major problem in the conversion funnel: their complicated checkout process.
Hotjar helped the team in two main ways:
They used the user feedback coming in through Surveys to prioritize improvements
They used Heatmaps and Session Recordings to understand customer blockers and pain points
Drawing on these UX research insights, the team decided to add a few small but crucial details to Intertop’s storefront, such as filters, intuitive product lists, and an improved checkout flow.
Product experience insights helped the team pinpoint exact bottlenecks and run feedback-driven experiments.
These changes skyrocketed Intertop's conversion rate by 54.68% and reduced bounce rates by 13.35%. They also enhanced the product page and lists to increase conversion from the cart to the checkout page by 36.6%.
Mapping the customer journey through your sales funnel is a critical part of successful ecommerce UX research. Monitor user needs at every stage through heatmaps, recordings, and feedback tools.
eShopWorld delivers global ecommerce solutions to help brands scale their business at the international level.
One of eShopWorld’s key services is conversion rate optimization. They monitor conversions for every client to identify drops and discrepancies.
However, the team didn't have a reliable tool for evaluating user behavior and countering occasional dips in the conversion rate.
eShopWorld used Hotjar Feedback tools on its checkout page to collect real-time user opinions: customers were able to flag issues right before ordering, and the eShopWorld team could dig deeper into understanding the context behind their comments via Session Recordings .
Heatmaps also provided actionable insights into customer behavior so the team could holistically review user issues and prioritize them according to their impact on the UX.
eShopWorld studied all the user feedback to get to the root of key problems. They used research data to plan and communicate UX design and user flow changes to tackle each blocker.
The team also analyzed Hotjar Heatmaps and watched Session Recordings to assess whether UX redesigns and changes produced the intended effect for users.
UX research is a continuous process of striving to understand your customers and their preferences at every stage of design and development. By using research tools to identify key issues and dig deeper into their context, teams can produce user-centric interfaces and make data-informed decisions.
For your site to attract quality traffic, deliver seamless buying experiences, and move the needle on conversion rates, you need to understand how your users behave and what they expect.
UX research tools can help you stay on top of your customer needs. Feature-packed PX insights tools allow you to easily observe user behavior, synthesize user feedback, and perform experiments to drive product growth.
What does ux research involve.
UX research is the process of studying the target audience to examine user behavior and identify opportunities for improving designs and workflows. UX research typically involves:
Monitoring user behavior
Assessing what users like and dislike based on their activity
Collecting feedback and suggestions for potential bugs or friction areas
Experimenting to see user reactions and validate any design improvements
Asking users for feedback to bring the users’ voice into the design and development process.
UX research varies in terms of methodology. You can use qualitative, quantitative, behavioral, and attitudinal methods for conducting your research. Each method uncovers unique insights about the user experience, such as:
Qualitative : why and how users behave on a page
Quantitative : numerical assessment of their activity
Behavioral : what users do on a website/product
Attitudinal : how users perceive a website/product
UX research lays the groundwork for successful UX design strategies. It helps you understand your customers and their needs to create more empathetic designs tailored to your audience.
It’s an essential factor for achieving goals such as lowering churn, bounce rate, cart abandonment, and improving UX. By helping you iterate your site or product informed by user feedback, UX research allows you to create a bulletproof website that meets user expectations.
Previous chapter
Next chapter
IMAGES
COMMENTS
Step 3: Draft your research objectives! Once you've written your aim, writing your research objectives is generally a pretty simple task. Look over your notes from your conversations with colleagues and check in with yourself about what you'd like to learn. Now, it's time to write!
The 7 Steps. Determine the most important user tasks. Discover which system aspects are of most concern. Group items from 1 & 2, then sort issues by importance to users and organization. For each top issue, condense the information into a problem statement. For each problem statement, list research goals.
1: Build research into your organization's decision-making. The best UX research strategy is built in collaboration with business strategy. Today, while many company leaders see the value of UX research, this isn't enough—to truly excel, we need to democratize research and use it to inform everything we do.
goals for UX research are: Advocating for the user. . Understanding user perspective, motiva. ions, and goals. Gathering user feedback and input. Using insights drawn f. om data to guide project direct. on and decision-making.What are some dimensions of UX?For every product and process that a person uses, their.
User experience research, or UX research, is the process of gathering insights about users' behaviors, needs, ... The goal of UX research is to understand your users and gain context and perspectives to help make informed decisions and build user-centered products. It's an essential part of designing, developing, and launching a product that ...
Step 3: Identify Your Target Audience & Plan a Recruiting Strategy. Knowing your audience is essential for creating a UX research plan that delivers relevant and actionable insights. In this step, we'll talk about how to define your target audience and plan a recruiting strategy for this set of users. The target audience you're considering ...
From Research Goals to Usability-Testing Scenarios: A 7-Step Method. Developing goals for a usability study, deciding what to test, and crafting user scenarios can be challenging. This method makes the process straightforward. Video Author. Tanner Kohler is a User Experience Specialist with Nielsen Norman Group.
A research objective, also known as a goal or an objective, is a sentence or question that summarizes the purpose of your study or test. In other words, it's an idea you want to understand deeper by performing research. ... the easier it is to write tasks and UX research questions, and the easier it will be to find the answers to those ...
Here's how to approach this phase in the UX research process: 1. Analyze UX research data. To analyze your data effectively, first, organize it systematically. Then, identify patterns and trends, understand user behavior, and cross-reference your findings with your research goals to create user-centered designs.
Depending on the research goal, it would be wise to have a good understanding which types of research you would like to be part of the ux design and would make the most impact. The BTNG Research Team loves to start with Qualitative Research to first get a better understanding of the WHY and gain new insights.
How to plan a UX research study. This is a step-by-step guide to planning user research. It explains the process by which a research plan comes together into a shareable document (like the one above) that enables team alignment, accountability, and efficiency throughout your study. 1. Identify your research goals.
A UX research goal is the purpose of your research, the main outcome you want to achieve, and the value you want to deliver to your stakeholders and users. It helps you focus your research scope ...
The UX researcher's toolkit: 11 UX research methods and when to use them. After defining your objectives and planning your research framework, it's time to choose the research technique that will best serve your project's goals and yield the right insights. While user research is often treated as an afterthought, it should inform every ...
Now that we the S.M.A.R.T goals method as it pertains to defining a research objectives, let's apply it! Say you are the Lead UX Researcher for a dating app that markets to retired singles (ages ...
UX Research Cheat Sheet. Susan Farrell. February 12, 2017. Summary: User research can be done at any point in the design cycle. This list of methods and activities can help you decide which to use when. User-experience research methods are great at producing data and insights, while ongoing activities help get the right things done.
Next is your step-by-step guide for creating a solid user research plan. Creating a UX Research plan, step-by-step. If you do a quick search, you'll see that the world is full of many different UX research podcasts, resources, and approaches when it comes to creating a research plan. In my role as a User Research Lead, I've found that a ...
UX research should always be done for a clear purpose - otherwise you're wasting the both your time and the time of your participants. But many people who do UX research fail to properly articulate the purpose in their research objectives. A major issue is that the research objectives include assumptions that have not been properly defined.
The benefits of a UX research plan are numerous, but some include: Fosters alignment: Rarely does UX research involve a single stakeholder. With a written UX research plan, you can ensure that all team members involved are on the same page, marching toward agreed-upon goals.
A UX research plan is a document that guides individual user experience (UX) research projects. UX research plans are shared documents that everyone on the product team can and should be familiar with. A UX research strategy, on the other hand, outlines the high-level goals, expectations, and demographics of the organization's approach to ...
A UX research objective is a statement of what you want to learn about your customers (or users) from carrying out the research. ... Delineate and align with the goal of the project;
A UX research plan, also known as a user research plan, is a brief reference document that outlines your research project's goals, key contributors, important dates, and timelines. Think of your research plan as a UX-focused kick-off document for your project. The plan offers an overview of the research initiative, encourages well-defined and ...
Here are seven examples of great UX research with the help of product experience insights tools to get you inspired. 1. Zenprint: 7% reduction in bounce rate. ... It's an essential factor for achieving goals such as lowering churn, bounce rate, cart abandonment, and improving UX. By helping you iterate your site or product informed by user ...
1 Introduction: set up the context. Start the conversation by introducing ourselves to the research participants. Go over the purpose and goal of the interview, give them a preview of key points you will cover, and address any concerns or questions the participants may have.
Discover how UX research can help mediate design disputes and lead to a user-centered design that aligns with project goals.
As a UX designer, it is important to focus on some key areas such as transparency, permission management, clear settings and privacy by design; all of which help in achieving a balance between data privacy and good user experience.