Summary: A detailed UX research plan helps you keep your overarching research goals in mind as you work through the logistics of a research project.

‍

There’s nothing quite like the feeling of sitting down to interview one of your users, steering the conversation in interesting directions and taking note of valuable comments and insights. But, as every researcher knows, it’s also easy to get carried away. Sometimes, the very process of user research can be so engrossing that you forget the reason you’re there in the first place, or unexpected things that come up that can force you to change course or focus.

‍

This is where a UX research plan comes into play. Taking the time to set up a detailed overview of your high-level research goals, team, budget and timeframe will give your research the best chance of succeeding. It's also a good tool for fostering alignment - it can make sure everyone working on the project is clear on the objectives and timeframes. Over the course of your project, you can refer back to your plan – a single source of truth. After all, as Benjamin Franklin famously said: “By failing to prepare, you are preparing to fail”.

‍

In this article, we’re going to take a look at the best way to put together a research plan.

‍

‍

‍

Your research recipe for success

‍

Any project needs a plan to be successful, and user research is no different. As we pointed out above, a solid plan will help to keep you focused and on track during your research – something that can understandably become quite tricky as you dive further down the research rabbit hole, pursuing interesting conversations during user interviews and running usability tests. Thought of another way, it’s really about accountability. Even if your initial goal is something quite broad like “find out what’s wrong with our website”, it’s important to have a plan that will help you to identify when you’ve actually discovered what’s wrong.

‍

So what does a UX research plan look like? It’s basically a document that outlines the where, why, who, how and what of your research project.

‍

It’s time to create your research plan! Here’s everything you need to consider when putting this plan together.

‍

‍

‍

Make a list of your stakeholders

‍

The first thing you need to do is work out who the stakeholders are on your project. These are the people who have a stake in your research and stand to benefit from the results. In those instances where you’ve been directed to carry out a piece of research you’ll likely know who these people are, but sometimes it can be a little tricky. Stakeholders could be C-level executives, your customer support team, sales people or product teams. If you’re working in an agency or you’re freelancing, these could be your clients.

‍

Make a list of everyone you think needs to be consulted and then start setting up catch-up sessions to get their input. Having a list of stakeholders also makes it easy to deliver insights back to these people at the end of your research project, as well as identify any possible avenues for further research. This also helps you identify who to involve in your research (not just report findings back to).

‍

Action: Make a list of all of your stakeholders.

‍

‍

‍

Write your research questions

‍

Before we get into timeframes and budgets you first need to determine your research questions, also known as your research objectives. These are the ‘why’ of your research. Why are you carrying out this research? What do you hope to achieve by doing all of this work? Your objectives should be informed by discussions with your stakeholders, as well as any other previous learnings you can uncover. Think of past customer support discussions and sales conversations with potential customers.

‍

Here are a few examples of basic research questions to get you thinking. These questions should be actionable and specific, like the examples we’ve listed here:

• “How do people currently use the wishlist feature on our website?”
• “How do our current customers go about tracking their orders?”
• “How do people make a decision on which power company to use?”
• “What actions do our customers take when they’re thinking about buying a new TV?”

‍

A good research question should be actionable in the sense that you can identify a clear way to attempt to answer it, and specific in that you’ll know when you’ve found the answer you’re looking for. It's also important to keep in mind that your research questions are not the questions you ask during your research sessions - they should be broad enough that they allow you to formulate a list of tasks or questions to help understand the problem space.

‍

Action: Create a list of possible research questions, then prioritize them after speaking with stakeholders.

‍

‍

‍

What is your budget?

‍

Your budget will play a role in how you conduct your research, and possibly the amount of data you're able to gather.

‍

Having a large budget will give you flexibility. You’ll be able to attract large numbers of participants, either by running paid recruitment campaigns on social media or using a dedicated participant recruitment service. A larger budget helps you target more people, but also target more specific people through dedicated participant services as well as recruitment agencies.

‍

Note that more money doesn't always equal better access to tools - e.g. if I work for a company that is super strict on security, I might not be able to use any tools at all. But it does make it easier to choose appropriate methods and that allow you to deliver quality insights. E.g. a big budget might allow you to travel, or do more in-person research which is otherwise quite expensive.

‍

With a small budget, you’ll have to think carefully about how you’ll reward participants, as well as the number of participants you can test. You may also find that your budget limits the tools you can use for your testing. That said, you shouldn’t let your budget dictate your research. You just have to get creative!

‍

Action: Work out what the budget is for your research project. It’s also good to map out several cheaper alternatives that you can pursue if required.

‍

‍

‍

How long will your project take?

‍

How long do you think your user research project will take? This is a necessary consideration, especially if you’ve got people who are expecting to see the results of your research. For example, your organization’s marketing team may be waiting for some of your exploratory research in order to build customer personas. Or, a product team may be waiting to see the results of your first-click test before developing a new signup page on your website.

‍

It’s true that qualitative research often doesn’t have a clear end in the way that quantitative research does, for example as you identify new things to test and research. In this case, you may want to break up your research into different sub-projects and attach deadlines to each of them.

‍

Action: Figure out how long your research project is likely to take. If you’re mixing qualitative and quantitative research, split your project timeframe into sub-projects to make assigning deadlines easier.

‍

‍

‍

Understanding participant recruitment

‍

Who you recruit for your research comes from your research questions. Who can best give you the answers you need? While you can often find participants by working with your customer support, sales and marketing teams, certain research questions may require you to look further afield.

‍

The methods you use to carry out your research will also have a part to play in your participants, specifically in terms of the numbers required. For qualitative research methods like interviews and usability tests, you may find you’re able to gather enough useful data after speaking with 5 people. For quantitative methods like card sorts and tree tests, it’s best to have at least 30 participants. You can read more about participant numbers in this Nielsen Norman article.

‍

At this stage of the research plan process, you’ll also want to write some screening questions. These are what you’ll use to identify potential participants by asking about their characteristics and experience.

‍

Action: Define the participants you’ll need to include in your research project, and where you plan to source them. This may require going outside of your existing user base.

‍

‍

‍

Which research methods will you use?

‍

The research methods you use should be informed by your research questions. Some questions are best answered by quantitative research methods like surveys or A/B tests, with others by qualitative methods like contextual inquiries, user interviews and usability tests. You’ll also find that some questions are best answered by multiple methods, in what’s known as mixed methods research.

‍

If you’re not sure which method to use, carefully consider your question. If we go back to one of our earlier research question examples: “How do our current customers go about tracking their orders?”, we’d want to test the navigation pathways.

‍

If you’re not sure which method to use, it helps to carefully consider your research question. Let’s use one of our earlier examples: “Is it easy for users to check their order history in our iPhone app?” as en example. In this case, because we want to see how users move through our app, we need a method that’s suited to testing navigation pathways – like tree testing.

‍

For the question: “What actions do our customers take when they’re thinking about buying a new TV?”, we’d want to take a different approach. Because this is more of an exploratory question, we’re probably best to carry out a round of user interviews and ask questions about their process for buying a TV.

‍

Action: Before diving in and setting up a card sort, consider which method is best suited to answer your research question.

‍

‍

‍

Develop your research protocol

‍

A protocol is essentially a script for your user research. For the most part, it’s a list of the tasks and questions you want to cover in your in-person sessions. But, it doesn’t apply to all research types. For example, for a tree test, you might write your tasks, but this isn't really a script or protocol.

‍

Writing your protocol should start with actually thinking about what these questions will be and getting feedback on them, as well as:

• The tasks you want your participants to do (usability testing)
• How much time you’ve set aside for the session
• A script or description that you can use for every session
• Your process for recording the interviews, including how you’ll look after participant data.

‍

Action: This is essentially a research plan within a research plan – it’s what you’d take to every session.

‍

Happy researching!

‍

‍

Related UX plan reading

‍

• What is mixed methods research? – Learn how a mixture of qualitative and quantitative research methods can set your research project up for success.
• How to encourage people to participate in your study – Attracting participants to your study can be a tough undertaking. We’ve got a few different approaches to help.
• Which comes first: card sorting or tree testing? – Card sorting, tree testing, which one should you use first? And why does it matter?
• How to write great questions for your research – Learn how you can craft effective questions for your next research project.
• 5 ways to increase user research in your organization – One of the best ways to get other teams and stakeholders on board with your own research projects is by helping to spread awareness of the benefits of user research.
• How to lead a UX team – With user-centered design continuing to grow in organizations across the globe, we’re going to need skilled UX leaders.
• How to benchmark your information architecture – Before embarking on any major information architecture projects, learn how you can benchmark your existing one.

Back in early 2018, user researchers from around the globe got together to try and define an emerging practice – ResearchOps. The project eventually grew into a significant research effort called #WhatisResearchOps, involving 34 workshops, a survey that garnered over 300 responses and reams of analysis.

The goal was quite simple. Generate conversation around the work that researchers do in order to support them as research grows, with an eye toward standardizing common research practices. It’s an important undertaking: a report back carried out in 2017 found that 81 percent of executives agreed that user research made their organization more efficient. Further, 86 percent believed user research improved the quality of their products.

It’s clear that many organizations are starting to understand the value that user researchers bring to the table, it’s now up to the researchers to operationalize their practice. 

But for the uninitiated, what exactly is ResearchOps? And why should you care?

What is ResearchOps?

To start off, there’s not a lot of literature about ResearchOps as of early 2020. Right now, it’s a practice that can certainly be classed as ‘emerging’. This is partly why we’re writing about it. We want to add our own kindling to the ResearchOps conversation fire.

ResearchOps as a practice has 2 main goals:

• Socialize research: Make it easier for the people in an organization to access the insights generated by user research, and allow them to actively take part in research activities.
• Operationalize research: Standardize templates, processes and plans to reduce research costs and the time required to get research projects off the ground.

Or, as Vidhya Sriram explains in the post we linked above, ResearchOps “democratizes customer insights, takes down barriers to understand customers, and makes everyone take responsibility for creating remarkable customer experiences.”

ResearchOps certainly hasn’t achieved anything close to ‘mainstream’ understanding yet, so in order to give ResearchOps the best chance of succeeding, it’s quite helpful to look at another ‘Ops’ practice – DesignOps.

As 2 ‘operations’ focused initiatives, DesignOps and ResearchOps share a lot of the same DNA. According to Nielsen Norman’s DesignOps 101 article, DesignOps “refers to the orchestration and optimization of people, processes, and craft in order to amplify design’s value and impact at scale”. Author Kate Kaplan goes on to flesh out this description, noting that it’s a term for addressing such issues as growing or evolving design teams, onboarding people with the right design skills, creating efficient workflows and improving design outputs. Sound familiar?

The world of DesignOps is a veritable smorgasbord of useful learnings for researchers looking to grow the practice of ResearchOps. One particularly useful element is the idea of selecting only the components of DesignOps that are relevant for the organization at that point in time. This is quite important. DesignOps is a broad topic, and there’s little sense in every organization trying to take on every aspect of it. The takeaway, DesignOps (and ResearchOps) should look very different depending on the organization.

Kate Kaplan also touches on another useful point in her Nielsen Norman Group article; the idea of the DesignOps menu:

This menu essentially outlines all of the elements that organizations could focus on when adopting practices to support designers. The DesignOps Menu is a useful framework for those trying to create a similar list of elements for ResearchOps.

Why does ResearchOps matter now?

It’s always been difficult to definitively say “this is the state of user research”. While some organizations intimately understand the value that a focus on customer centricity brings (and have teams devoted to the cause), others are years behind. In these lagging organizations, the researchers (or the people doing research), have to fight to prove the value of their work. This is one of the main reasons why ResearchOps as an initiative matters so much right now.

The other driver for ResearchOps is that the way researchers work together and with other disciplines is changing fast. In general, a growing awareness of the importance of the research is pushing the field together with data science, sales, customer support and marketing. All this to say, researchers are having to spend more and more time both proving the value of their work and operating at a more strategic level. This isn’t likely to slow, either. The coming years will see researchers spending less time doing actual research. With this in mind, ResearchOps becomes all the more valuable. By standardizing common research practices and working out ownership, the research itself doesn’t have to suffer.

What are the different components of ResearchOps?

As we touched on earlier, ResearchOps – like DesignOps – is quite a broad topic. This is necessary. As most practicing researchers know, there are a number of elements that go into ensuring thorough, consistent research.

A useful analogy for ResearchOps is a pizza. There are many different components (toppings) that can go on the pizza, which is reflected in how research exists in different organizations. The real point here is that no 2 research operations should look the same. Research at Facebook will look markedly different to research at a small local government agency in Europe.

We looked at the DesignOps Menu earlier as a model for ResearchOps, but there’s another, more specific map created as part of the #WhatisResearchOps project.

Like the DesignOps Menu, this map functions as a framework for what ResearchOps is. It’s the output of a series of workshops run by researchers across the globe as well as a large survey.

Who practices ResearchOps?

By now you should have a clear idea of the scale and scope of ResearchOps, given that we’ve covered the various components and why the practice matters so much. There are still 2 important topics left to cover, however: Who practices ResearchOps and (perhaps most interestingly) where it’s heading.

As the saying goes, “everyone’s a researcher”, and this certainly holds true when talking about ResearchOps, but here are some of the more specific roles that should be responsible for executing ResearchOps components.

• User researchers – Self-explanatory. The key drivers of research standardization and socialization.
• UX designers – Customer advocates to the core, UX designers follow user researchers quite closely when it comes to execution.
• Designers – Add to that, designers in general. As designers increasingly become involved in the research activities of their organizations, expect to see them having a growing stake in ResearchOps activities.
• Customer experience (CX) and marketing – Though they’re often not the foremost consideration when it comes to research conversations, marketing and CX certainly have a stake in research operations. 

There’s also another approach that is worth considering: Research as a way of thinking. This can essentially be taken up by anyone, and it boils down to understanding the importance of a healthy research function, with processes, systems and tools in place to carry out research.

What’s next for ResearchOps?

As Kate Kaplan said in DesignOps 101, “DesignOps is the glue that holds the design organization together, and the bridge that enables collaboration among cross-disciplinary team members”. The same is true of ResearchOps – and it’s only going to become more important. 

We’re going to echo the same call made by numerous other people helping to grow ResearchOps and say that if you’ve got some learnings to share, share them back with the community! We’re also always looking to share great UX and research content, so get in touch with us if you’ve got something to share on our blog.

Co-authored by Brandon Dorn, UX designer at Viget.As user experience designers, making sure that websites and tools are usable is a critical component of our work, and conducting user research enables us to assess whether we’re achieving that goal or not. Even if we want to incorporate research, however, certain constraints may stand in our way.

‍

A few years ago, we realized that we were facing this issue at Viget, a digital design agency, and we decided to make an effort to prioritize user research. Almost two years ago, we shared initial thoughts on our progress in this blog post. We’ve continued to learn and grow as researchers since then and hope that what we’ve learned along the way can help your clients and coworkers understand the value of research and become better practitioners. Below are some of those lessons.

‍

Make research a priority for your organization

‍

Before you can do more research, it needs to be prioritized across your entire organization — not just within your design team. To that end, you should:

‍

• Know what you’re trying to achieve. By defining specific goals, you can share a clear message with the broader organization about what you’re after, how you can achieve those goals, and how you will measure success. At Viget, we shared our research goals with everyone at the company. In addition, we talked to the business development and project management teams in more depth about specific ways that they could help us achieve our goals, since they have the greatest impact on our ability to do more research.

• Track your progress. Once you’ve made research a priority, make sure to review your goals on an ongoing basis to ensure that you’re making progress and share your findings with the organization. Six months after the research group at Viget started working on our goals, we held a retrospective to figure out what was working — and what wasn’t.
• Adjust your approach as needed. You won’t achieve your goals overnight. As you put different tactics into action, adjust your approach if something isn’t helping you achieve your goals. Be willing to experiment and don’t feel bad if a specific tactic isn’t successful.

‍

Educate your colleagues and clients

‍

If you want people within your organization to get excited about doing more research, they need to understand what research means. To educate your colleagues and clients, you should:

• Explain the fundamentals of research. If someone has not conducted research before, they may not be familiar or feel comfortable with the vernacular. Provide an overview of the fundamental terminology to establish a basic level of understanding. In a blog post, Speaking the Same Language About Research, we outline how we established a common vocabulary at Viget.
• Help others understand the landscape of research methods. As designers, we feel comfortable talking about different methodologies and forget that that information will be new to many people. Look for opportunities to increase understanding by sharing your knowledge. At Viget, we make this happen in several ways. Internally, we give presentations to the company, organize group viewing sessions for webinars about user research, and lead focused workshops to help people put new skills into practice. Externally, we talk about our services and share knowledge through our blog posts. We are even hosting a webinar about conducting user interviews in November and we'd love for you to join us.
• Incorporate others into the research process. Don't just tell people what research is and why it's important — show them. Look for opportunities to bring more people into the research process. Invite people to observe sessions so they can experience research firsthand or have them take on the role of the notetaker. Another simple way to make people feel involved is to share findings on an ongoing basis rather than providing a report at the end of the process.

‍

Broaden your perspective while refining your skill set

‍

Our commitment to testing assumptions led us to challenge ourselves to do research on every project. While we're dogmatic about this goal, we're decidedly un-dogmatic about the form our research takes from one project to another. To pursue this goal, we seek to:

• Expand our understanding. To instill a culture of research at Viget, we've found it necessary to question our assumptions about what research looks like. Books like Erika Hall’s Just Enough Research teach us the range of possible approaches for getting useful user input at any stage of a project, and at any scale. Reflect on any methodological biases that have become well-worn paths in your approach to research. Maybe your organization is meticulous about metrics and quantitative data, and could benefit from a series of qualitative studies. Maybe you have plenty of anecdotal and qualitative evidence about your product that could be better grounded in objective analysis. Aim to establish a balanced perspective on your product through a diverse set of research lenses, filling in gaps as you learn about new approaches.
• Adjust our approach to project constraints. We've found that the only way to consistently incorporate research in our work is to adjust our approach to the context and constraints of any given project. Client expectations, project type, business goals, timelines, budget, and access to participants all influence the type, frequency, and output of our research. Iterative prototype testing of an email editor, for example, looks very different than post-launch qualitative studies for an editorial website. While some projects are research-intensive, short studies can also be worthwhile.
• Reflect on successes and shortcomings. We have a longstanding practice of holding post-project team retrospectives to reflect on and document lessons for future work. Research has naturally come up in these conversations, and many of the things we've discussed you're reading right now. As an agency with a diverse set of clients, it's been important for us to understand what types of research work for what types of clients, and when. Make sure to take time to ask these questions after projects. Mid-project retrospectives can be beneficial, especially on long engagements, yet it's hard to see the forest when you're in the weeds.

‍

Streamline qualitative research processes 🚄

‍

Learning to be more efficient at planning, conducting, and analyzing research has helped us overturn the idea that some projects merit research while others don't. Remote moderated usability tests are one of our preferred methods, yet, in our experience, the biggest obstacle to incorporating these tests isn't the actual moderating or analyzing, but the overhead of acquiring and scheduling participants. While some agencies contract out the work of recruiting, we've found it less expensive and more reliable to collaborate with our clients to find the right people for our tests. That said, here are some recommendations for holding efficient qualitative tests:

• Know your tools ahead of time. We use a number of tools to plan, schedule, annotate, and analyze qualitative tests (we're inveterate spreadsheet users). Learn your tools beforehand, especially if you're trying something new. Tools should fade into the background during tests, which Reframer does nicely.
• Establish a recruiting process. When working with clients to find participants, we'll often provide an email template tailored to the project for them to send to existing or potential users of their product. This introductory email will contain a screener that asks a few project-related demographic or usage questions, and provides us with participant email addresses which we use to follow-up with a link to a scheduling tool. Once this process is established, the project manager will ensure that the UX designer on the team has a regular flow of participants. The recruiting process doesn't take care of itself – participants cancel, or reschedule, or sometimes don't respond at all – yet establishing an approach ahead of time allows you, the researcher, to focus on the research in the midst of the project.
• Start recruiting early. Don't wait until you've finished writing a testing script to begin recruiting participants. Once you determine the aim and focal points of your study, recruit accordingly. Scripts can be revised and approved in the meantime.

‍

Be proactive about making research happen 🤸

‍

As a generalist design agency, we work with clients whose industries and products vary significantly. While some clients come to us with clear research priorities in mind, others treat it as an afterthought. Rare, however, is the client who is actively opposed to researching their product. More often than not, budget and timelines are the limiting factors. So we try not to make research an ordeal, but instead treat it as part of our normal process even if a client hasn't explicitly asked for it. Common-sense perspectives like Jakob Nielsen’s classic “Discount Usability for the Web” remind us that some research is always better than none, and that some can still be meaningfully pursued. We aren’t pushy about research, of course, but instead try to find a way to make it happen when it isn't a definite priority.

‍

‍World Usability Day is coming up on November 9, so now is a great time to stop and reflect on how you approach research and to brainstorm ways to improve your process. The tips above reflect some of the lessons we’ve learned at Viget as we’ve tried to improve our own process. We’d love to hear about approaches you’ve used as well.