Latest / 5 Minute UX / Selecting Research Techniques Based on Project Constraints
Transcript
- 0:08This lesson is Selecting Research Techniques Based on
- 0:10Project Constraints. Let's get started.
- 0:19When you sit down to choose a research technique, you are not
- 0:21starting from a blank slate. You are responding to three specific
- 0:24constraints that dictate what is actually possible. First, you
- 0:27must assess the client company’s appetite for user research,
- 0:29which varies based on the importance placed on it by the
- 0:32project team or project sponsor. This internal alignment often
- 0:34determines whether you have room to propose a single round of
- 0:37research or if you must justify every minute of engagement.
- 0:40Second, you look at the available time and budget
- 0:42constraints of the project. These financial and temporal
- 0:44limits define the scope of your logistics, from the space and
- 0:47equipment required to the compensation for participants.
- 0:49You cannot conduct interviews or surveys if the budget does not
- 0:52support the necessary data capture tools or participant
- 0:54recruitment. Third, you evaluate the flexibility to
- 0:56incorporate user research into the current phase of
- 0:58development. A technique that works perfectly in the discovery
- 1:01phase might be entirely impossible during a tight
- 1:03release window. You must match your method to where the team
- 1:06stands in their lifecycle. Finally, you anchor your choice
- 1:08to the specific information needs of the project. You are
- 1:11identifying the highest areas of risk if the team acts without
- 1:13user insights, and your technique must address that gap
- 1:16directly. Once you have weighed these factors, you can move
- 1:18toward selecting the right approach for your environment.
- 1:27I'm going to walk you through how to move a team that has
- 1:29never seen user research before, because in those situations,
- 1:32proposing a comprehensive program just triggers more
- 1:34resistance. If no one at the organization is familiar with
- 1:36user research and there is resistance to the practice
- 1:38altogether, the recommended approach is to propose a single
- 1:41round of research rather than a comprehensive program. That
- 1:43single round needs to be chosen with a very specific lens: you
- 1:46pick the one technique that will bring the most value to the
- 1:48designer, the project team, and the business stakeholders. This
- 1:51isn't about picking what’s easiest for you, it’s about
- 1:53identifying the single highest- impact insight that will change
- 1:56how they view the product. When you deliver those results, the
- 1:58project team gains a better understanding of what is
- 2:00involved in the process and how the project can benefit from it.
- 2:03This is the critical shift that moves the conversation from
- 2:05skepticism to curiosity, because they are now seeing the direct
- 2:08connection between the research and their specific business
- 2:10goals. With that foundation of trust established, you can start
- 2:13looking at the specific constraints that will dictate
- 2:15exactly what that next round of research looks like in terms of
- 2:18time and budget.
- 2:25Once you have selected your high-value technique, you must
- 2:27map out the execution. This requires addressing nine
- 2:29specific planning considerations that determine whether the study
- 2:32actually happens. You start by locking in the budget and
- 2:35timeline, because the financial and temporal limits of the
- 2:37project dictate what is feasible. Next, you conduct a
- 2:39risk assessment to identify the highest areas of risk if the
- 2:42team acts without user insights. This step ensures your research
- 2:45targets the most critical unknowns rather than trivial
- 2:47details. Simultaneously, you define your goals and objectives
- 2:50by stating exactly what you want to learn from the research. This
- 2:52clarity prevents the study from drifting into generic
- 2:55observations that do not serve the project’s immediate needs.
- 2:57You then identify the target audience, pinpointing the
- 3:00primary user groups to be included in the sessions. With
- 3:02that group defined, you determine how to get
- 3:04participants and craft the specific questions needed to
- 3:06screen them effectively. This screening process is vital for
- 3:09ensuring every participant genuinely falls into the
- 3:11targeted user groups you are studying. You also need to
- 3:14decide how participants will be compensated, as this influences
- 3:16both participation rates and the perceived value of the study.
- 3:19Logistics come next, where you determine the space, equipment,
- 3:22and software required based on whether the research is
- 3:24conducted in person or remotely. This physical or digital setup
- 3:27must be ready before the first session begins. You then define
- 3:29the scope by outlining the primary topics to be covered,
- 3:32keeping the conversation focused on your core objectives.
- 3:34Finally, you plan data capture by deciding on the number of
- 3:37people involved in the process and the tools they will use to
- 3:39capture information. With these nine elements in place, the
- 3:42research is ready to be applied to a specific scenario.
- 3:50Imagine a client with low research appetite, a tight two-
- 3:52week timeline, and a need to validate a new feature concept.
- 3:55You have to select a single high-value technique, like
- 3:57usability testing or interviews, that addresses the highest risk
- 4:00area. Why not a comprehensive program? Because in a high-
- 4:03resistance environment, proposing a single round of
- 4:05research demonstrates immediate value without overwhelming the
- 4:08team. Your goal is to define exactly what you want to learn
- 4:10from the research. This specific information need drives your
- 4:13choice. By focusing on one technique, you ensure the
- 4:15results are clear and actionable. The project team
- 4:17gains a better understanding of what is involved in the process
- 4:20and how the project can benefit from it. This immediate value is
- 4:23what secures stakeholder buy-in for further research. Think
- 4:25about the specific data you need to validate the feature concept.
- 4:28Does it require observing users in action, or do you need direct
- 4:31feedback on their goals? The technique you choose must align
- 4:34with this specific need. A broad, multi-method approach
- 4:36would dilute the focus and likely face resistance. Instead,
- 4:39a targeted single round proves the worth of user insights.
- 4:41This approach respects the client’s constraints while
- 4:44delivering tangible results. You are not just picking a method;
- 4:46you are making a strategic decision based on project
- 4:49constraints and organizational resistance. The outcome is a
- 4:51clear, valuable insight that the team can act on immediately.
- 4:54This foundation sets the stage for expanding research efforts
- 4:56later.
- 5:03Here is the closing section of the lesson. [pause:2s] The
- 5:06most common failure in technique selection is proposing a
- 5:08comprehensive research program into a high-resistance
- 5:10environment. This approach leads to immediate rejection because
- 5:13it ignores the client’s appetite for user research. You are
- 5:15proposing techniques that demand high stakeholder involvement,
- 5:18which clashes with the organization’s current capacity
- 5:20to support the work. A second critical error is failing to
- 5:23define the specific information needs before selecting a method.
- 5:26Without clear goals and objectives, you end up with
- 5:28irrelevant data that does not address the project’s risk
- 5:30assessment. The technique becomes a generic exercise
- 5:32rather than a targeted solution to a specific business problem.
- 5:35Finally, overlooking logistical constraints creates execution
- 5:38risk. Ignoring recruitment difficulty or compensation
- 5:40requirements means you cannot secure the right participants to
- 5:43validate your user group definitions. Selecting the
- 5:45right technique requires balancing these constraints
- 5:47against the value of the insights. When you align your
- 5:49method with the client’s appetite, your timeline, and
- 5:52your specific information needs, you ensure the research delivers
- 5:54actionable results that the team can actually use. This is how
- 5:57you move from proposing a study to solving a problem.
- 6:02Welcome to The Take. I'm joined by a fellow practitioner and
- 6:05together we're going to dig into Selecting Research Techniques
- 6:08Based on Project Constraints — what it means in practice and
- 6:11what's worth remembering.
- 6:13[HOST] That bit about proposing a single round of research
- 6:16instead of a full program hit home. It feels counterintuitive
- 6:20when you wanna show your full capability. [LEARNER] It does.
- 6:23But I found that pitching a comprehensive study to a
- 6:25skeptical team is a sure way to get a hard no. [HOST] Exactly.
- 6:29They see a massive time commitment and immediately think
- 6:32it’s a distraction from shipping. [LEARNER] I’ve seen
- 6:34clients reject a two-day workshop just because it sounded
- 6:37complex. But they loved a one- hour expert review. [HOST]
- 6:40That’s the risk assessment factor at work. You’re targeting
- 6:44the highest risk area, not the most impressive method.
- 6:46[LEARNER] Right. If the risk is whether users can find the
- 6:49checkout button, you don’t need a diary study. [HOST] And that’s
- 6:53where the logistics come in. You need to lock in the budget and
- 6:56timeline before you even pick the method. [LEARNER] Often we
- 6:59skip that step and end up with a great idea we can’t execute.
- 7:02[HOST] True. I’ve had to drop a planned usability test because
- 7:06we couldn’t recruit the right participants in time. [LEARNER]
- 7:09That’s a brutal constraint. How do you decide what’s feasible
- 7:12when the budget is tight? [HOST] You look at the data capture
- 7:15tools. If you can’t afford a specialized recording suite, you
- 7:19use a simple screen share. [LEARNER] That makes sense.
- 7:21Simplicity reduces the friction for the client too. [HOST] And
- 7:25honestly, AI is changing how we handle the analysis side of
- 7:28that. [LEARNER] Oh, I’ve used it to transcribe sessions. It saves
- 7:31hours of manual work. [HOST] But the real value is in pattern
- 7:34recognition. AI can flag recurring pain points across
- 7:37multiple sessions quickly. [LEARNER] That’s a game changer
- 7:40for small teams. We don’t have the time to watch every hour of
- 7:43footage. [HOST] So you can focus your human insight on
- 7:46interpreting the context, not just logging the words.
- 7:49[LEARNER] That shifts the role from scribe to strategist. I
- 7:52like that. [HOST] It does. It lets you deliver that high-value
- 7:55insight faster, which builds the trust for the next round.
- 7:58[LEARNER] So the AI handles the volume, and you handle the
- 8:01meaning. [HOST] Precisely. And that speed is what convinces the
- 8:05resistant stakeholders that research isn’t a bottleneck.