how to write ux research objectives

UX Research: Objectives, Assumptions, and Hypothesis

by Rick Dzekman

An often neglected step in UX research

Introduction

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:

• For generative research it’s usually to find out something about users or customers that you previously did not know
• For evaluative research it’s usually to identify any potential issues in a solution

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:

• How will those research objectives help to reach that goal?
• What assumptions have you made that are necessary for those objectives to reach that goal?
• How does your research (questions, tasks, observations, etc.) help meet those objectives?
• What kind of responses or observations do you need from your participants to meet those objectives?

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.

Research hypothesis

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:

• Observe users shopping on sites with and without colour filters and see whether or not they use them
• Ask users who are interested in our products about how narrow down their choices
• Run a diary study where participants document the ways they narrowed down their searches on various stores
• Make a prototype with colour filters and see if participants use them unprompted

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?

Example Hypothesis: Adding a colour filter would make it easier for users to find the right products

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.

Example Hypothesis: Travelers book flights before they book their hotels

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?

Example Hypothesis: Most users who come to our app know where and when they want to fly

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.

Example Hypothesis: Customers want their bank to help them build better savings habits

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.

Research objectives

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:

• “extreme outcomes (both high and low) are more likely to be found in small than in large samples”
• “the prominence of causal intuitions is a recurrent theme in this book because people are prone to apply causal thinking inappropriately, to situations that require statistical reasoning”
• “when people believe a conclusion is true, they are also very likely to believe arguments that appear to support it, even when these arguments are unsound”

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.

Example objectives: deciding on filters

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:

• “Understand” is a common form of research objective and is a way that qualitative research can discover things that we cannot find with quant. If we don’t yet understand some user attitude or behaviour we cannot quantify it. By focusing our objective on understanding we are looking at uncovering unknowns.
• By using the word “might” we are not definitively stating that our research will reveal all of the ways that users think about their needs.
• Our focus is on understanding the users’ mental models. Then we are not designing for what users say that they want and we aren’t even designing for existing behaviour. Instead we are designing for some underlying need.

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.

Mapping objectives to our research plan

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.

Breaking down our objectives

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.

Reviewing our objectives and pilot studies

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.

Plan accordingly

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.

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

Resources Hub

Educational resources for product, research and design teams

Explore all resources

Question Bank

Maze Research Success Hub

Guides & Reports

Help Center

The Evolving Role of Research Playbook

The Optimal Path Podcast

Maze Guides | Resources Hub

What is UX Research: The Ultimate Guide for UX Researchers

0% complete

Essential elements of an effective UX research plan (examples + templates)

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.

What is a UX research plan?

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.

Research plan vs. research design vs. research strategy: What’s the difference?

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.

What are the benefits of using a UX research plan?

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:

Streamline processes and add structure

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.

What should a UX research plan include?

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:

• A brief reminder of the strategy and goals
• An outline of the research objectives
• The purpose of the plan and studies
• A short description of the target audience, sample size, scope, and demographics
• A detailed list of expectations including deliverables, timings, and type of results
• An overview of the test methods and a short explanation of why you chose them
• The test set up or guidelines to outline everything that needs to happen before the study: scenarios, screening questions, and duration of pilot tests
• Your test scripts, questions to ask, or samples to follow
• When and how you’ll present the results
• Cost estimations or requests to go over budget

Collect all UX research findings in one place

Use Maze to run quantitative and qualitative research, influence product design, and shape user-centered products.

How to create a UX research plan

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.

• Define the problem statement
• Get stakeholders’ buy-in
• Identify your objectives
• Choose the right research method
• Recruit participants
• Prepare the brief
• Establish the timeline
• Decide how you’ll present your findings

1. Define the problem statement

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.

2. Identify your 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:

• Learn at what times users interact with your product
• Understand why users return (or not) to your website/app
• Discover what competitor products your users are using
• Uncover any pain points or challenges users find when navigating with your product
• Gauge user interest in and prioritize potential new features

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:

• What are you going to do with this information?
• What decisions is it going to inform?
• How are you going to leverage these insights?

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:

• Who are the users you’re designing this for?
• What problems and needs do they have?
• What are the pain points of using the product?
• Why are they not using a product like yours?

3. Get stakeholders buy-in

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

4. Choose the right research method

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:

• Five-second testing
• User interviews
• Field studies
• Card sorting
• Tree testing
• Focus groups
• Usability testing
• Diary studies
• Live website testing

Check out our top UX research templates . Use them as a shortcut to get started on your research.

5. Determine how to recruit participants

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:

• Do you have a user base you can tap into to collect customer insights ?
• Do you need to hire external participants?
• What’s your budget to recruit users?
• How many users do you need to interact with?

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:

• Using an online participant recruitment tool like Maze Panel
• Putting out physical or digital adverts in spaces that are relevant to your product and user
• Reaching out to existing users
• Using participants from previous research
• Recruiting directly from your website or app with a tool like In-Product Prompts

5.1. Determine how you’ll pay them

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.

6. Prepare the brief

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:

• Introduction: A short message you’ll say to participants before the session begins. This works as a starting point for conversations and helps set the tone for the meeting. If you’re testing without a moderator, you should also include an introductory message to explain what the research is about and the type of answers they should give (in terms of length and specificity).
• Interview questions: Include your list of questions you’ll ask participants during the sessions. These could be examples to help guide the interviews, specific pre-planned questions, or test tasks you’ll ask participants to perform during unmoderated sessions.
• Outro message: Outline what you'll say at the end of the session, including the next steps, asking participants if they are open to future research, and thanking them for their time. This can be a form you share at the end of asynchronous sessions.

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.

7. Establish the timeline

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.

8. Decide how you’ll present your findings

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:

• A physical or digital PDF report with key statistics and takeaways
• An interactive online report of the individual research questions and their results
• A presentation explaining the results and your findings
• A digital whiteboard, like Miro, to display the results

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.

Your UX research plan template: Free template + example

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.

Example: Improving user adoption of a project management tool called Flows

Now, let’s go through how to fill out this template and create a UX research plan with an example.

Executive summary:

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.

Research objectives:

Purpose of the plan and studies:.

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.

Target audience, sample size, scope, and demographics:

Expectations, deliverables, timings, and type of results:, research methodologies:.

*Some teams will take part in more than one research session.

Research analysis methods:

We are doing a mixed methods study.

User interviews are our primary method for gathering qualitative data, and will be analyzed using thematic analysis .

• Quantitative data will be pulled from usability tests to evaluate the effectiveness of our current design.
• Research set up and guidelines:
• Create baselines surveys to gauge current usage and pain points
• Develop interview/discussion guides and usability testing scenarios
• Pilot test materials with two teams
• User interviews: 60 mins, semi-structured; usability tests: 90 mins
• Findings will be presented in a research report for all stakeholders

Research scripts, questions, and samples:

User interview questions:

• What’s your experience with Flows?
• How does Flows fit into your workflow?
• What is your understanding of Flows’ features?
• What do you wish Flows could do that it currently doesn’t?

Usability test sample with Maze:

Cost estimations or budget requests/pricing:

Total estimated budget: $8,000

More free customizable templates for UX research

Whether you’re creating the plan yourself or are delegating this responsibility to your team, here are six research templates to get started:

• UX research plan template : This editable Miro research project plan example helps you brainstorm user and business-facing problems, objectives, and questions
• UX research brief : You need a clear brief before you conduct UX research—Milanote shares a template that will help you simplify the writing process
• User testing synthesis : Trello put together a sample board to organize user testing notes—you can use this as a guide, but change the titles to fit your UX research purposes
• Usability testing templates : At Maze, we’ve created multiple templates for conducting specific UX research methods—this list will help you create different remote usability tests
• Information architecture (IA) tests template : The way you organize the information in your website or app can improve or damage the user experience—use this template to run IA tests easily
• Feedback survey templates : Ask users anything through a survey, and use these templates to get creative and simplify creation

Everything you need to know about UX research plans

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:

• Using a UX research strategy as a starting point will make your plan more likely to succeed
• Determine your research objectives before anything else
• Use a mix of qualitative and quantitative research methods
• Come up with clear personas so you can recruit and test a group of individuals that’s representative of your real end users
• Involve stakeholders from the beginning to get buy-in
• Be vocal about timelines, budget, and expected research findings
• Use the insights to power your product decisions and wow your users; building the solution they genuinely want and need

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?

Elevate your UX research workflow

Discover how Maze can streamline and operationalize your research plans to drive real product innovation while saving on costs.

Frequently asked questions

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:

• Problem statement
• Research objectives
• Research methods
• Participants' demographics
• Recruitment plan
• User research brief
• Expected timeline
• How to present findings

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

New NPM integration: design with fully interactive components from top libraries!

Creating A User Research Plan (with Examples)

UX research helps to test hypothesis you have about users prior to design. Sadly, not every UX design project starts with user research, and that’s because it takes a lot of time to recruit participants, run UX research projects, and sumamrize findings.

Good research, nevertheless, ensures that your product team doesn’t build the wrong functionality that would cost you valuable resources and make you vulnerable to losing customers.

In this article, you’ll see how you can use UX research plan to get stakeholder’s buy-in and create research reports that’s full of valuable advice for product design. Let’s go.

At the end, when you have your research complete, launch the right tool for your design process. For that, try UXPin, an end-to-end design tool for interactive prototyping that brings design and product development together.

Designers can create a powerful prototypes, show them to product managers who can interact with the design instead of just looking at it. Then, they give the design to engineers who can get all the specs and some code to kickstart front-end design with.

Since with UXPin you work faster, you have ample time for UX research before UX design. Try it for free .

Build advanced prototypes

Design better products with States, Variables, Auto Layout and more.

What is a UX Research Plan?

A UX research plan helps to set expectations and document the essentials you need to communicate to stakeholders and clients. Your company needs a strong business case for every user research session, complete with research objectives, goals, methods, and logistical needs for the study.

UX Research Plan Elements

Every UX research plan should start with a solid outline. That’s where templates come in handy. They help you structure your UX research project in a way that team members and stakeholders see value in completing research process.

Master templates are the best way to create a successful and effective UX research plan. Using a template as a starting point makes planning and writing easier and helps you and your team stay focused on the who, what, why, and when of research. Read on for tips and examples for how you can build a user research plan that works.

UX Research Plan Background

The background section should offer your clients and stakeholders a few sentences on why you are creating a user research plan and what it will accomplish. It should orient readers to the needs and expectations behind the purpose of the study. It should also include a problem statement, which is the primary question you’re setting out to answer with your research findings. 

Example Background

The purpose of this study is to understand the major pain points users experience in using our website/app and how these contribute to issues such as cart abandonment, returned items, and low customer loyalty. 

We will be using usability testing to follow the user’s experience of our website/app and the obstacles they encounter leading up to the point of purchase. We will also be using generative research techniques to better understand the customer’s experience of our brand and the challenges and needs they face in making a purchase. 

UX Research Plan Objectives

Before getting into the nitty-gritty of your user research plan, you first want to focus on your research objectives. This step outlines the reasons you are conducting a UX research plan in the first place. Why are you carrying out this research? What are the end goals you have after completing all the work?

Seeking out answers to these questions should be a collaborative effort between you and your stakeholders. It’s also helpful to consider discussions and learnings from past clients and projects to create metrics for your UX research plan. 

Objectives and Success Metrics

Research objectives will be different for every project, but they should always be actionable and specific. 

Example Objectives

• Understand how users currently go about tracking orders on our website
• Understand what actions customers take when they consider buying a new [product we offer]
• Learn about competitor websites/apps customers are using to buy [product we offer]
• Evaluate pain points customers are experiencing in using our website/app

And here are some examples to help you determine the success of your UX research plan.

Example Success Metrics

• What information are we trying to collect about users?
• What scales/documents/statistics do we intend to create?
• What decisions will these materials help to make? 

UX Research Plan Methodology

This step should be a short and sweet description of the research methods you will use to answer the research objectives. It should include both secondary and primary methods. Generative methods, such as user interviews and open-ended questions, help uncover motivations or more general insights, while UX testing helps to evaluate the usability and experience of your product. 

Research Scope & Focus Areas

Clearly outlining the research scope and focus areas helps to facilitate efficient user research planning. The more you’re able to hone in on the specifics of what information you are wanting to collect, the less overwhelmed you will be in the process. It also helps avoid inundating your clients with unnecessary information. 

To keep research-focused, this section should include:

• 3-6 question topics (e.g. How do users spend their time on a website?)
• Design Focus Components, including interface qualities (e.g. Usability, Training, Efficiency, Satisfaction)
• Primary User Scenarios (e.g. Scenarios in which pain points are most problematic; scenarios you have the least information about, etc.)

Example Methodology

For this study, we’re conducting a 30-minute usability test to evaluate our user’s experience of our app/website. A secondary method will be to conduct one-on-one generative research interviews to better understand our customers and empathize with their needs. 

UX Research Plan Participant Profiles

Once you’ve defined objectives methodology and focus areas, it’s time to outline the participants you’ll need to get the required insights. Participant profiles help you determine who you want to recruit, or an approximation of your users, to optimize recruiting efforts. Here are a few examples of how to ensure you’ll get the best participants for your study. 

Define your target user by collaborating with internal stakeholders, marketing, sales, and customer support. With their help, you can create approximations about who your users are. This is a great starting point for finding the right participants for your study. 

Compare yourself to your competitors and create participant profiles based on their audiences. Recruiting people who use a competitor’s product can be an excellent way to glean insights into how to further improve your product. 

Outline a screening process. Participant profiles should include any relevant information concerning your target audience, including behaviors, needs, demographics, geography, etc. Including the right criteria will help you evaluate whether or not to include certain individuals in your user research plan. 

This Nielsen Norman article offers some great information about defining and recruiting the right participants for your study. 

UX Research Plan Timeline

This is optional, but many UX research plans include a timeline that offers clients and stakeholders a general overview of how long the research will take. It helps to set expectations for the final results as well as allowing you to create a schedule for research sessions, debriefing, follow-up, and deliverables. 

Timeline Example: 

Approximately 6-8 weeks for identifying objectives, creating participant profiles, recruitment, in-person meetings, qualitative research, and analysis. 

Try an End-to-End Design Solution

UX research plan templates are essential tools for executing a successful project. Having a master template helps you to remember what the process entails, communicate essential information to the right people, and stay on track throughout the user research plan.

UXPin, besides being a great prototyping tool, makes creating such research templates fast and easy. Especially since each project will be a little different and plans will need tweaking in terms of structure and content. Try UXPin for free .

Build prototypes that are as interactive as the end product. Try UXPin

by UXPin on 8th October, 2020

UXPin is a product design platform used by the best designers on the planet. Let your team easily design, collaborate, and present from low-fidelity wireframes to fully-interactive prototypes.

No credit card required.

These e-Books might interest you

Interaction Design Patterns

Design and reuse the most important interaction patterns in UI design.

Design Systems & DesignOps in the Enterprise

Spot opportunities and challenges for increasing the impact of design systems and DesignOps in enterprises.

We use cookies to improve performance and enhance your experience. By using our website you agree to our use of cookies in accordance with our cookie policy.