Create a user research plan with these steps

With UX research so closely tied to product success, setting up a dedicated research practice is fast becoming important for many organizations. It’s not an easy process, especially for organizations that have had little to do with research, but the end goal is worth the effort.

‍

But where exactly are you supposed to start? This article provides 6 key things to keep in mind when setting up a research practice, and should hopefully ensure you’ve considered all of the relevant factors.

‍

1) Work out what your organization needs

‍

The first and most simple step is to take stock of the current user research situation within the organization. How much research is currently being done? Which teams or individuals are talking to customers on an ongoing basis? Consider if there are any major pain points with the current way research is being carried out or bottlenecks in getting research insights to the people that need them. If research isn't being practiced, identify teams or individuals that don't currently have access to the resources they need, and consider ways to make insights available to the people that need them.

‍

2) Consolidate your insights

‍

UX research should be communicating with nearly every part of an organization, from design teams to customer support, engineering departments and C-level management. The insights that stem from user research are valuable everywhere. Of course, the opposite is also true: insights from support and sales are useful for understanding customers and how the current product is meeting people's needs.

‍

When setting up a research practice, identify which teams you should align with, and then reach out. Sit down with these teams and explore how you can help each other. For your part, you’ll probably need to explain the what and why of user research within the context of your organization, and possibly even explain at a basic level some of the techniques you use and the data you can obtain.

‍

Then, get in touch with other teams with the goal of learning from them. A good research practice needs a strong connection to other parts of the business with the express purpose of learning. For example, by working with your organization’s customer support team, you’ll have a direct line to some of the issues that customers deal with on a regular basis. A good working relationship here means they’ll likely feed these insights back to you, in order to help you frame your research projects.

‍

By working with your sales team, they’ll be able to share issues prospective customers are dealing with. You can follow up on this information with research, the results of which can be fed into the development of your organization’s products.

‍

It can also be fruitful to develop an insights repository, where researchers can store any useful insights and log research activities. This means that sales, customer support and other interested parties can access the results of your research whenever they need to.

‍

When your research practice is tightly integrated other key areas of the business, the organization is likely to see innumerable benefits from the insights>product loop.

‍

3) Figure out which tools you will use

‍

By now you’ve hopefully got an idea of how your research practice will fit into the wider organization – now it’s time to look at the ways in which you’ll do your research. We’re talking, of course, about research methods and testing tools.

‍

We won’t get into every different type of method here (there are plenty of other articles and guides for that), but we will touch on the importance of qualitative and quantitative methods. If you haven’t come across these terms before, here’s a quick breakdown:

‍

• Qualitative research – Focused on exploration. It’s about discovering things we cannot measure with numbers, and often involves speaking with users through observation or user interviews.
• Quantitative research – Focused on measurement. It’s all about gathering data and then turning this data into usable statistics.

‍

All user research methods are designed to deliver either qualitative or quantitative data, and as part of your research practice, you should ensure that you always try to gather both types. By using this approach, you’re able to generate a clearer overall picture of whatever it is you’re researching.

‍

Next comes the software. A solid stack of user research testing tools will help you to put research methods into practice, whether for the purposes of card sorting, carrying out more effective user interviews or running a tree test.

‍

There are myriad tools available now, and it can be difficult to separate the useful software from the chaff. Here’s a list of research and productivity tools that we recommend.

‍

Tools for research

‍

Here’s a collection of research tools that can help you gather qualitative and quantitative data, using a number of methods.

‍

• Treejack – Tree testing can show you where people get lost on your website, and help you take the guesswork out of information architecture decisions. Like OptimalSort, Treejack makes it easy to sort through information and pairs this with in-depth analysis features.
• dScout – Imagine being able to get video snippets of your users as they answer questions about your product. That’s dScout. It’s a video research platform that collects in-context “moments” from a network of global participants, who answer your questions either by video or through photos.
• Ethnio – Like dScout, this is another tool designed to capture information directly from your users. It works by showing an intercept pop-up to people who land on your website. Then, once they agree, it runs through some form of research.
• OptimalSort – Card sorting allows you to get perspective on whatever it is you’re sorting and understand how people organize information. OptimalSort makes it easier and faster to sort through information, and you can access powerful analysis features.
• Reframer – Taking notes during user interviews and usability tests can be quite time-consuming, especially when it comes to analyze the data. Reframer gives individuals and teams a single tool to store all of their notes, along with a set of powerful analysis features to make sense of their data.
• Chalkmark – First-click testing can show you what people click on first in a user interface when they’re asked to complete a task. This is useful, as when people get their first click correct, they’re much more likely to complete their task. Chalkmark makes the process of setting up and running a first-click test easy. What’s more, you’re given comprehensive analysis tools, including a click heatmap.

‍

Tools for productivity

‍

These tools aren’t necessarily designed for user research, but can provide vital links in the process.

‍

• Whimsical – A fantastic tool for user journeys, flow charts and any other sort of diagram. It also solves one of the biggest problems with online whiteboards – finicky object placement.
• Descript – Easily transcribe your interview and usability test audio recordings into text.
• Google Slides – When it inevitably comes time to present your research findings to stakeholders, use Google Slides to create readable, clear presentations.

‍

4) Figure out how you’ll track findings over time

‍

With some idea of the research methods and testing tools you’ll be using to collect data, now it’s time to think about how you’ll manage all of this information. A carefully ordered spreadsheet and folder system can work – but only to an extent. Dedicated software is a much better choice, especially given that you can scale these systems much more easily.

‍

A dedicated home for your research data serves a few distinct purposes. There’s the obvious benefit of being able to access all of your findings whenever you need them, which means it’s much easier to create personas if the need arises. A dedicated home also means your findings will remain accessible and useful well into the future.

‍

When it comes to software, Reframer stands as one of the better options for creating a detailed customer insights repository as you’re able to capture your sessions directly in the tool and then apply tags afterwards. You can then easily review all of your observations and findings using the filtering options. Oh, and there’s obviously the analysis side of the tool as well.

‍

If you’re looking for a way to store high-level findings – perhaps if you’re intending to share this data with other parts of your organization – then a tool like Confluence or Notion is a good option. These tools are basically wikis, and include capable search and navigation options too.

‍

5) Where will you get participants from?

‍

A pool of participants you can draw from for your user research is another important part of setting up a research practice. Whenever you need to run a study, you’ll have real people you can call on to test, ask questions and get feedback from.

‍

This is where you’ll need to partner other teams, likely sales and customer support. They’ll have direct access to your customers, so make sure to build a strong relationship with these teams. If you haven’t made introductions, it can helpful to put together a one-page sheet of information explaining what UX research is and the benefits of working with your team.

‍

You may also want to consider getting in some external help. Participant recruitment services are a great way to offload the heavy lifting of sourcing quality participants – often one of the hardest parts of the research process.

‍

6) Work out how you'll communicate your research

‍

Perhaps one of the most important parts of being a user researcher is taking the findings you uncover and communicating them back to the wider organization. By feeding insights back to product, sales and customer support teams, you’ll form an effective link between your organization’s customers and your organization. The benefits here are obvious. Product teams can build products that actually address customer pain points, and sales and support teams will better understand the needs and expectations of customers.

‍

Of course, it isn’t easy to communicate findings. Here are a few tips:

‍

• Document your research activities: With a clear record of your research, you’ll find it easier to pull out relevant findings and communicate these to the right teams.
• Decide who needs what: You’ll probably find that certain roles (like managers) will be best served by a high-level overview of your research activities (think a one-page summary), while engineers, developers and designers will want more detailed research findings.

‍

Continue reading

‍

• Selling your design recommendations to clients and colleagues – Guest writer Jeff Tang outlines some of his techniques for presenting UX recommendations and answering objections.
• Quantifying the ROI of UX – Ashlea McKay delves into one of the toughest UX questions to answer: “What do we get for our money?”
• How do I explain what UX is? – Ashlea McKay covers how you can explain UX to people who may not necessarily have familiarity with the field.

Knowing and understanding why and how your users use your product is invaluable for getting to the nitty gritty of usability. Delving deep with probing questions into motivation or skimming over looking for issues can equally be informative. 

‍

Put super simply, usability testing literally is testing how usable your product is for your users. If your product isn’t usable users often won’t complete their task, let alone come back for more. No one wants to lose users before they even get started. Usability testing gets under their skin and really into the how, why and what they want (and equally what they don’t).

‍

As we have been getting used to video calling regularly and using the internet for interactions, usability testing has followed suit. Being able to access participants remotely has allowed us to diversify the participant pool by not being restricted to those that are close enough to be in-person. This has also allowed an increase in the number of participants per test, as it becomes more cost-effective to perform remote usability testing.

‍

But if we’re remote, does this mean it can’t be moderated? No - remote testing, along with modern technology, can mean that remote testing can be facilitated and moderated. But what is the best method - moderated or unmoderated?

‍

What is moderated remote research testing?

‍

In traditional usability testing, moderated research is done in person. With the moderator and the participant in the same physical space. This, of course, allows for conversation and observational behavioral monitoring. Meaning the moderator can note not only what the participant answers but how and even make note of the body language, surroundings, and other influencing factors. 

‍

This has also meant that traditionally, the participant pool has been limited to those that can be available (and close enough) to make it into a facility for testing. And being in person has meant it takes time (and money) to perform these tests.

‍

As technology has moved along and the speed of internet connections and video calling has increased, this has opened up a world of opportunities for usability testing. Allowing usability testing to be done remotely. Moderators can now set up testing remotely and ‘dial in’ to observe participants anywhere they are. And potentially even running focus groups or other testing in a group format across the internet. 

‍

Pros of moderated remote research testing:

‍

- In-depth gathering of insights through a back-and-forth conversation and observing of the participants.

‍

- Follow-up questions don’t underestimate the value of being available to ask questions throughout the testing. And following up in the moment.

‍

- Observational monitoring noticing and noting the environment and how the participants are behaving, can give more insight into how or why they choose to make a decision.

‍

- Quick remote testing can be quicker to start, find participants, and complete than in-person. This is because you only need to set up a time to connect via the internet, rather than coordinating travel times, etc.

‍

- Location (local and/or international) Testing online removes reliance on participants being physically present for the testing. This broadens your ability to broaden the pool, and participants can be either within your country or global. 

‍

Cons of moderated remote research testing:

‍

- Time-consuming having to be present at each test takes time. As does analyzing the data and insights generated. But remember, this is quality data.

‍

- Limited interactions with any remote testing there is only so much you can observe or understand across the window of a computer screen. It can be difficult to have a grasp on all the factors that might be influencing your participants.

‍

What is unmoderated remote research testing?

‍

In its most simple sense, unmoderated user testing removes the ‘moderated’ part of the equation. Instead of having a facilitator guide participants through the test, participants are left to complete the testing by themselves and in their own time. For the most part, everything else stays the same. 

‍

Removing the moderator, means that there isn’t anyone to respond to queries or issues in the moment. This can either delay, influence, or even potentially force participants to not complete or maybe not be as engaged as you may like. Unmoderated research testing suits a very simple and direct type of test. With clear instructions and no room for inference. 

‍

Pros of unmoderated remote research testing:

‍

- Speed and turnaround,  as there is no need to schedule meetings with each and every participant. Unmoderated usability testing is usually much faster to initiate and complete.

‍

- Size of study (participant numbers) unmoderated usability testing allows you to collect feedback from dozens or even hundreds of users at the same time. 

- Location (local and/or international) Testing online removes reliance on participants being physically present for the testing, which broadens your participant pool.  And unmoderated testing means that it literally can be anywhere while participants complete the test in their own time.

‍

Cons of unmoderated remote research testing:

‍

- Follow-up questions as your participants are working on their own and in their own time, you can’t facilitate and ask questions in the moment. You may be able to ask limited follow-up questions.

‍

- Products need to be simple to use unmoderated testing does not allow for prototypes or any product or site that needs guidance. 

‍

- Low participant support without the moderator any issues with the test or the product can’t be picked up immediately and could influence the output of the test.

‍

When should you do moderated vs unmoderated remote usability testing?

‍

Each moderated and unmoderated remote usability testing have its use and place in user research. It really depends on the question you are asking and what you are wanting to know.

‍

Moderated testing allows you to gather in-depth insights, follow up with questions, and engage the participants in the moment. The facilitator has the ability to guide participants to what they want to know, to dig deeper, or even ask why at certain points. This method doesn’t need as much careful setup as the participants aren’t on their own. While this is all done online, it does still allow connection and conversation. This method allows for more investigative research. Looking at why users might prefer one prototype to another. Or possibly tree testing a new website navigation to understand where they might get lost and querying why the participant made certain choices.

‍

Unmoderated testing, on the other hand, is literally leaving the participants to it. This method needs very careful planning and explaining upfront. The test needs to be able to be set and run without a moderator. This lends itself more to wanting to know a direct answer to a query. Such as a card sort on a website to understand how your users might sort information. Or a first click to see how/where users will click on a new website.

‍

Planning your next user test? Here’s how to choose the right method

‍

With the ability to expand our pool of participants across the globe with all of the advances (and acceptance of) technology and video calling etc, the ability to expand our understanding of users’ experiences is growing. Remote usability testing is a great option when you want to gather information from users in the real world. Depending on your query, moderated or unmoderated usability testing will suit your study. As with all user testing, being prepared and planning ahead will allow you to make the most of your test.

Few UX research techniques can surpass the user interview for the simple fact that you can gain a number of in-depth insights by speaking to just a handful of people. Yes, the prospect of sitting down in front of your customers can be a daunting one, but you’ll gain a level of insight and detail that really is tough to beat.

‍

This research method is popular for a reason – it’s extremely flexible and can deliver deep, meaningful results in a relatively short amount of time.

‍

We’ve put together this article for both user interview newbies and old hands alike. Our intention is to give you a guide that you can refer back to so you can make sure you're getting the most out of this technique. Of course, feel free to leave a comment if you think there’s something else we should add.

‍

What is a user interview?

‍

User interviews are a technique you can use to capture qualitative information from your customers and other people you’re interested in learning from. For example, you may want to interview a group of retirees before developing a new product aimed at their market.

‍

User interviews usually follow the format of a guided conversation, diving deep into a particular topic. While sometimes you may have some predefined questions or topics to cover, the focus of your interviews can change depending on what you learn along the way.

‍

Given the format, user interviews can help you answer any number of questions, such as:

‍

• How do people currently shop online? Are there any products they would never consider purchasing this way?
• How do people feel about using meal delivery services? What stops them from trying them out?
• How do ride sharing drivers figure out which app to use when they’re about to start a shift?

‍

It’s important to remember that user interviews are all about people's perception of something, not usability. What this means in practical terms is that you shouldn’t go into a user interview expecting to find out how they navigate through a particular app, product or website. Those are answers you can gain through usability testing.

‍

When should you interview your users?

‍

Now that we have an understanding of what user interviews are and the types of questions this method can help you answer, when should you do them? As this method will give you insights into why people think the way they do, what they think is important and any suggestions they have, they’re mostly useful in the discovery stages of the design process when you're trying to understand the problem space.

‍

You may want to run a series of user interviews at the start of a project in order to inform the design process. Interviews with users can help you to create detailed personas, generate feature ideas based on real user needs and set priorities. Looked at another way, doesn’t it seem like an unnecessary risk not to talk to your users before building something for them?

‍

Plan your research

‍

Before sitting down and writing your user interview, you need to figure out your research question. This is the primary reason for running your user interviews – your ‘north star’. It’s also a good idea to engage with your stakeholders when trying to figure this question out as they’ll be able to give you useful insights and feedback.

‍

A strong research question will help you to create interview questions that are aligned and give you a clear goal. The key thing is to make sure that it’s a strong, concise goal that relates to specific user behaviors. You don’t want to start planning for your interview with a research question like “How do customers use our mobile app”. It’s far too broad to direct your interview planning.

‍

Write your questions

‍

Now it’s time to write your user interview questions. If you’ve taken the time to engage with stakeholders and you’ve created a solid research question, this step should be relatively straightforward.

‍

Here are a few things to focus on when writing your interview questions:

‍

• Encourage your interviewees to tell stories: There’s a direct correlation between the questions you write for a user interview and the answers you get back. Consider more open-ended questions, with the aim of getting your interviewees to tell you stories and share more detail. For example, “Tell me about the last car you owned” is much better than “What was the last car you owned”.
• Consider different types of questions: You don’t want to dive right into the complex, detailed questions when your interviewee has barely walked into the room. It’s much better to start an interview off with several ‘warm-up’ questions, that will get them in the right frame of mind. Think questions like: “What do you do for work?” and “How often do you use a computer at home?”. Answering these questions will put them in the right frame of mind for the rest of the interview.
• Start with as many questions as you can think of – then trim: This can be quite a helpful exercise. When you’re actually putting pen to paper (or fingers to keyboard) and writing your questions, go broad at first. Then, once you’ve got a large selection to choose from, trim them back.
• Have someone review your questions: Whether it’s another researcher on your team or perhaps someone who’s familiar with the audience you plan to interview, get another pair of eyes on your questions. Beyond just making sure they all make sense and are appropriate, they may be able to point out any questions you may have missed.

‍

Recruit participants

‍

Having a great set of questions is all well and good, but you need to interview the right kind of people. It’s not always easy. Finding representative or real users can quickly suck up a lot of time and bog down your other work. But this doesn’t have to be the case. With some strategy and planning you can make the process of participant recruitment quick and easy.

‍

There are 2 main ways to go about recruitment. You can either handle the process yourself – we’ll share some tips for how to do this below – or use a recruitment service. Using a dedicated recruitment service will save you the hassle of actively searching for participants, which can often become a significant time-sink.

‍

If you’re planning to recruit people yourself, here are a few ways to go about the process. You may find that using multiple methods is the best way to net the pool of participants you need.

‍

• Reach out to your customer support team: There’s a ready source of real users available in every organization: the customer support team. These are the people that speak to your organization’s customers every day, and have a direct line to their problems and pain points. Working with this team is a great way to access suitable participants, plus customers will value the fact that you’re taking the time to speak to them.
• Recruit directly from your website: Support messaging apps like Intercom and intercept recruiting tools like Ethnio allow you to recruit participants directly from your website by serving up live intercepts. This is a fast, relatively hands-off way to recruit people quickly.
• Ask your social media followers: LinkedIn, Twitter and Facebook can be great sources of research participants. There’s also the bonus that you can broadcast the fact that your organization focuses on research – and that’s always good publicity! If you don’t have a large following, you can also run paid ads on different social platforms.

‍

Once a pool of participants start to flow in, consider setting up a dedicated research panel where you can log their details and willingness to take part in future research. It may take some admin at the start, but you’ll save time in the long run.

‍

Note: Figure out a plan for participant data protection before you start collecting and storing their information. As the researcher, it’s up to you to take proper measures for privacy and confidentiality, from the moment you collect an email address until you delete it. Only store information in secure locations, and make sure you get consent before you ever turn on a microphone recorder or video camera.

‍

Run your interviews

‍

Now for the fun part – running your user interviews. In most cases, user interviews follow a simple format. You sit down next to your participant and run through your list of questions, veering into new territory if you sense an interesting discussion. At the end, you thank them for their time and pass along a small gift (such as a voucher) as a thank-you.

‍

Of course, there are a few other things that you’ll want to keep in mind if you really want to conduct the best possible interviews.

‍

• Involve others: User interviews are a great way to show the value of research and give people within your organization a direct insight into how users think. There are no hard and fast rules around who you should bring to a user interview, just consider how useful the experience is likely to be for them. If you like, you can also assign them the role of notetaker.
• Record the interview: You’ll have to get consent from the interviewee, but having a recording of the interview will make the process of analysis that much easier. In addition to being able to listen to the recording again, you can convert the entire session into a searchable text file.
• Don’t be afraid to go off-script: Interviewing is a skill, meaning that the more interviews you conduct, the better you’re going to get. Over time, you’ll find that you’re able to naturally guide the conversation in different directions as you pick up on things the interviewee says. Don’t be discouraged if you find yourself sticking to your prepared questions during your first few interviews.
• Be attentive: You don’t want to come across as a brick wall when interviewing someone – you want to be seen as an attentive listener. This means confirming that you’re listening by nodding, making eye contact and asking follow-up questions naturally (this last one may take practice). If you really struggle to ask follow-up questions, try writing a few generic questions can you can use at different points throughout the interview, for example “Could you tell me more about that?”. There’s a great guide on UXmatters about the role empathy has to play in understanding users.
• Debrief afterwards: Whether it’s just you or you and a notetaker, take some time after the interview to go over how it went. This is a good opportunity to take down any details either you may have missed and to reflect and discuss some of the key takeaways.

‍

Analyze your interview findings

‍

At first glance, analyzing the qualitative data you’ve captured from a user interview can seem daunting. But, with the right approach (and some useful tools) you can extract each and every useful insight.

‍

If you’ve recorded your interview sessions, you’ll need to convert your audio recordings into text files. We recommend a tool like Descript. This software makes it easy to take an audio file of your recording and transform it into a document, which is much faster than doing it without dedicated software. If you like, there’s also the option of various ‘white glove’ services where someone will transcribe the interview for you.

‍

With your interview recordings transcribed and notes in-hand, you can start the process of thematic analysis. If you’re unfamiliar, thematic analysis is one of the most popular approaches for qualitative research as it helps you to find different patterns and themes in your data. There are 2 ways to approach this. The first is largely manual, where you set up a spreadsheet with different themes like ‘navigation issue’ and ‘design problem’, and group your findings into these areas. This can be done using sticky notes, which used to be a common ways to analyze findings.

‍

The second involves dedicated qualitative research tool like Reframer. You log your notes over the course of several interview sessions and then use Reframer’s tagging functionality to assign tags to different insights. By applying tags to your observations, you can then use its analysis features to create wider themes. The real benefit here is that there’s no chance of losing your past interviews and analysis as everything is stored in one place. You can also easily download your findings into a spreadsheet to share them with your team.

‍

What’s next?

‍

With your interviews all wrapped up and your analysis underway, you’re likely wondering what’s next. There’s a good chance your interviews will have opened up new areas you’d like to test, so now could be the perfect time to assess other qualitative research methods and add more human data to your research project. On the other hand, you may want to move onto quantitative research and put some numbers behind your research.

‍

Whether you choose to proceed down a qualitative or quantitative path, we’re pulled together some more useful articles and things for you to read:

‍

• Qualitative research methods – A breakdown of various qualitative research methods and why you’d want to use this research approach in the first place.
• Taking better notes for better sensemaking – Learn how you can improve your notetaking abilities before your next user interview or usability test.
• 13 time-saving tips and tools for conducting great user interviews – User interviews can be time-sinks, so take a look at these tips to make the process as smooth as possible.
• Pros and cons of conducting user interviews (Interaction Design Foundation) – A really useful resource that breaks down the pros and cons of user interviews.
• Tool: Reframer – You can use Reframer (our qualitative note taking tool) to capture detailed notes during your interviews. Then, you can apply tags and use Reframer’s analysis features to make the most of your interview data.
• Tool: Descript – Transcribing interviews is arduous, and can often take more time than the interview itself. Use a transcription tool like Descript to speed the process up.
• 16 tips for better user interviews – If you’d like another checklist to run through before you start your user interviews, this one is worth checking out.