Skip to main content

Introduction to User Research

Premium

What you'll learn in this module

Understanding and advocating for users throughout the product development cycle is one of your most important responsibilities as a PM. User research helps you gain the user understanding to do so effectively — and helps you answer questions that arise throughout the process. This module teaches you how to use this important tool, even if you don't have a user research team, and must do it yourself. We'll cover:

  • How user research fits into the PM process. When, in the product development process, should you incorporate user research? What sorts of research?
  • Types of user research studies. What are some popular user research study types and what are they best used for?
  • Planning and running an in-lab study. How do you go about finding participants, planning an in-lab usability study, and ensuring things run smoothly on the day?
  • Synthesis. After a study, how should you review and compile what you've learned?
  • Creating UXR deliverables. How can you turn your insights into personas, user stories, and jobs to be done that drive your product development process?

Your user research colleagues

  • If your company has a user researcher (or user research team), they'll of course be your primary collaborator(s). You can expect them to handle the logistics of planning studies. They will work with you to generate questions to explore and to ensure that any needed materials/prototypes will be ready. They'll likely also conduct the studies, leaving you free to observe and take notes.
  • Your UI/UX designer (or design team) is a key part of successful user research. Throughout their design process, they'll have questions that are best resolved by putting competing variants in front of users and seeing what happens. Your designers will also create the mocks that will help answer your questions in interviews and usability studies. A lot of design happens for research purposes and never makes it into the product — be cognizant of that when planning sprints and budgeting designer time.
  • You should invite your engineering team to participate in user research as much as possible. When you need fully functional prototypes, they'll help build them. But even when you're just testing UX mocks, it helps your engineering team to see how users interact with the product (and potential new features). Engineers make dozens of tiny tradeoffs in the course of building each feature. They'll ask you about some of those, but it makes your job a lot easier if you can trust them to independently make user-driven decisions... and giving them more exposure to user behavior makes them better at that.
  • If you have a community manager who monitors and moderates discussion forums, reviews, and product feedback email accounts, they can be a useful resource to help you understand how the patterns you see in the user research lab do or don't match the patterns of feedback from current users.

What to expect when doing user research

First, what not to expect: statistically significant data. (You may get it with some types of research, such as large-scale quantitative surveys, but not with most.) Much of user research is about thoughts and feelings — understanding people's needs and getting the how and why behind what they do. This can be infuriating to the analytically minded: how do you know what you're learning from user research is true? You don't, in a strict statistical sense, but that doesn't prevent the understanding you develop from user research from being valuable.

When you actually start doing user research, it will be time-consuming and uncomfortable. There are no shortcuts: running five one-hour usability studies requires five hours no matter how efficient you are at your job! (If you're in charge of setting up logistics for those studies, that can also be arduous.) Your first study sessions will likely be awkward. The skill of listening intently and asking probing questions isn't one we practice in a lot of settings. Don't worry, you'll get better. And some people love it. If you're naturally curious about people (a good trait for PMs to have!), you'll likely find yourself enjoying the user research process.

The good news: user research is also rewarding. The insights you gain will inspire your product road map. The time you spend observing users will increase your confidence and the quality of your decision-making. In brief, spending time on user research will make you a better PM.

Why user research matters

While we might wish we could answer all questions with hard data, that's simply not the case. In fact, the scope of questions that can be answered with analytics and A/B testing is very limited. For everything else, there's user research (and some even consider analytics and A/B testing a part of user research). With the broad array of study methods available, you can answer diverse questions:

  • What need(s) in users' lives does (should) our product solve?
  • What emotions does the product inspire? What about the competitors' products?
  • What information hierarchy would be most intuitive to our users?
  • What are the obstacles users face when trying to accomplish X task?
  • Why aren't people using X feature that we thought would be popular?