Latest / 5 Minute UX / Planning User Research: A Practical Guide
Transcript
- 0:08This lesson is Planning User Research: A Practical Guide.
- 0:11Let's get started.
- 0:18Before we dive into the full research plan, let's recall how
- 0:21you typically define primary user groups. You already create
- 0:24a framework describing the main types of users the team is
- 0:26designing for, which anchors your recruitment efforts. This
- 0:29defined set of primary user groups ensures you focus efforts
- 0:32in planning research and recruiting users effectively. If
- 0:35product analytics are unavailable, you identify other
- 0:37methods to build a foundation of understanding. This prevents the
- 0:41common pitfall where practitioners feel unprepared
- 0:43due to a lack of data. You also identify the highest areas of
- 0:46risk if acting without user insights, which guides your
- 0:49strategic choices. By establishing this baseline, you
- 0:51ensure that every subsequent decision in the research plan is
- 0:54grounded in real user needs. This initial clarity prevents
- 0:57scope creep and keeps the team aligned on who we are actually
- 1:00designing for.
- 1:06With those primary user groups defined, you move into
- 1:08structuring the research plan by working directly with your team
- 1:11and stakeholders to set clear research goals and objectives.
- 1:14This alignment ensures everyone understands exactly why the
- 1:16research is being conducted and what specific problems need
- 1:19solving. You then choose one or more methods, such as user
- 1:21interviews, usability studies, card sorting, or contextual
- 1:24inquiry, that will help meet those goals effectively. The
- 1:26selection depends entirely on whether you need to understand
- 1:29user motivations or validate specific design decisions. Once
- 1:32the method is selected, you must address several logistical
- 1:34considerations to ensure the study can happen. You need to
- 1:37determine the budget and timeline, which dictates how
- 1:39many activities you can realistically conduct within the
- 1:42available resources. Recruitment is another major factor,
- 1:44requiring screening questions to ensure participants fall into
- 1:47the targeted user groups you identified earlier. You also
- 1:50need to decide how participants will be compensated and what
- 1:52space, equipment, and software needs exist for in-person or
- 1:55remote sessions. To keep the execution tight, you should
- 1:57create research method scripts and guides that include a
- 2:00scripted opening for each session. These guides provide a
- 2:02detailed breakdown of topics, questions, tasks to observe, and
- 2:05activities for the user to perform during the interaction.
- 2:08Having this structure in place prevents scope creep and ensures
- 2:10consistent data capture across all sessions, regardless of who
- 2:13is facilitating. It turns abstract goals into concrete
- 2:16actions that any team member can follow reliably. Finally, you
- 2:18must define target research outputs early to prevent
- 2:21mismatched expectations between the team and the customer. This
- 2:23includes a brief description of how synthesis will be performed
- 2:26and the expected deliverables, ensuring stakeholders know what
- 2:29they will receive. By clarifying the synthesis plan upfront, you
- 2:32avoid the common pitfall of stakeholders expecting insights
- 2:34that the chosen methods cannot provide. This documentation
- 2:37serves as the contract for what the research will actually
- 2:40achieve. With the plan structured and expectations
- 2:42aligned, you are ready to move into the execution phase where
- 2:44these methods come to life in a worked example.
- 2:53Let’s look at a task-based application. You conduct user
- 2:55interviews during the Define phase to understand your users
- 2:58before designing. Then, you run usability testing on a prototype
- 3:01before development starts to validate the design. This two-
- 3:04round approach ensures you address risks early.
- 3:06Alternatively, for a content source, you might use contextual
- 3:09inquiry followed by a card sorting exercise. This sequence
- 3:11helps organize information architecture effectively. Your
- 3:14research plan must include detailed scripts. These scripts
- 3:17need a scripted opening, a breakdown of topics, specific
- 3:19questions, tasks to observe, and activities for the user to
- 3:22perform. This structure keeps sessions focused and consistent.
- 3:25By following these steps, you create a solid foundation for
- 3:27your research. You’ll have clear insights to guide your design
- 3:30decisions.
- 3:36Now you execute the plan by following the chosen methods,
- 3:39which often involves multiple rounds of research to build a
- 3:42complete picture. You might run one round during the Define
- 3:44phase to understand users, then a second round before
- 3:47development starts to validate the design. As you conduct
- 3:49sessions, use the scripted opening and specific tasks from
- 3:52your research method guides to keep everything consistent. If
- 3:55you need structure, templates and tutorials from usability.gov
- 3:58provide resources to start activities and ensure you don't
- 4:00miss steps. Once data collection ends, perform research synthesis
- 4:03exactly as you outlined in the initial planning phase to
- 4:06maintain alignment with your goals. This step transforms raw
- 4:08observations into synthesized insights, turning scattered
- 4:11notes into patterns that the team can use. You then share
- 4:14these defined outputs with stakeholders, ensuring everyone
- 4:16sees the same evidence and understands the implications for
- 4:19the design. This transparency prevents mismatched expectations
- 4:22and gives the team a clear foundation for the next phase of
- 4:24work.
- 4:31When product analytics are unavailable, it is natural to
- 4:33feel unprepared, but you can simply use other user research
- 4:36methods to uncover valuable insights. This approach builds a
- 4:39solid foundation of understanding without relying on
- 4:41historical data. Another frequent issue involves
- 4:43stakeholders holding mismatched expectations regarding results,
- 4:46which often leads to friction during the review phase. To
- 4:49prevent this, you should define target research outputs and the
- 4:51synthesis plan early in the planning phase. This ensures
- 4:54that expectations are met for the team and customer before any
- 4:57sessions begin. By applying mitigation strategies for common
- 5:00pitfalls like lack of analytics or unclear expectations, you
- 5:02safeguard your project against these predictable hurdles. You
- 5:05now have the complete framework to construct a comprehensive
- 5:08user research plan that defines primary user groups, selects
- 5:11appropriate methods, addresses logistical constraints, and sets
- 5:13clear synthesis expectations. The work is no longer abstract;
- 5:16it is a structured process you can execute with confidence.
- 5:19Take this plan to your next stakeholder meeting and anchor
- 5:22the conversation in shared goals rather than assumptions.
- 5:27Welcome to The Take. I'm joined by a fellow practitioner and
- 5:30together we're going to dig into Planning User Research: A
- 5:33Practical Guide — what it means in practice and what's worth
- 5:36remembering.
- 5:38[HOST] That section on defining synthesis outputs upfront really
- 5:42hit home for me. I keep seeing teams drown in raw notes because
- 5:45they never agreed on the format. [LEARNER] Exactly. It's the
- 5:48difference between delivering insights and just dumping a
- 5:51transcript folder. Stakeholders need to know if they're getting
- 5:55personas or journey maps before we start recruiting. [HOST] It
- 5:58forces us to be honest about what the chosen methods can
- 6:01actually deliver. We can't promise quantitative validation
- 6:04if we only planned for three deep-dive interviews. [LEARNER]
- 6:07True, but the logistics part is where I usually get stuck.
- 6:10Budget constraints often force us to cut the number of
- 6:13sessions, which risks skewing our data. [HOST] That's why we
- 6:16have to tie recruitment directly to those primary user groups. If
- 6:20the budget is tight, we narrow the scope to the highest risk
- 6:23areas rather than diluting our focus. [LEARNER] I agree on
- 6:26narrowing scope, but getting those screening questions right
- 6:29is harder than it looks. People lie on surveys to get into the
- 6:33study, especially if the incentive is high. [HOST] You're
- 6:36right. That's why I'm experimenting with AI tools to
- 6:39analyze initial screening responses for consistency. It
- 6:42helps flag participants who might be gaming the system.
- 6:45[LEARNER] That's a smart use of AI. I usually just rely on gut
- 6:48feeling during the intro call, which is obviously not scalable
- 6:51or reliable. [HOST] It isn't about replacing human judgment,
- 6:54but catching obvious red flags faster. We still need that human
- 6:58empathy during the actual session to build rapport.
- 7:01[LEARNER] Definitely. The script keeps us consistent, but the
- 7:04human connection uncovers the real motivations. Without that,
- 7:07we are just checking boxes. [HOST] Precisely. The plan is
- 7:10the skeleton, but the interaction is the life. If we
- 7:13get the skeleton right, the rest flows much smoother. [LEARNER]
- 7:16It takes the anxiety out of the "what if we miss something"
- 7:19fear. I feel much more confident walking into my next stakeholder
- 7:23meeting now. [HOST] That confidence comes from knowing
- 7:26your constraints and your goals are aligned. Go in there and
- 7:29anchor the conversation in those shared expectations.