Create a user research plan with these steps

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.

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.

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.