Listen

Description

Master the four-step process for selecting appropriate UX research techniques based on project phase and user groups. Learn to align methods like contextual inquiry or usability testing with specific goals, while avoiding common pitfalls like unvalidated models.

Learning Objective: By the end of this lesson, learners will be able to select appropriate UX research techniques by applying a four-step decision framework that accounts for user groups, project phase, and logistical constraints.



Transcript

Prerequisites for Technique Selection

Before selecting techniques, you need to identify the four prerequisites required before selecting research techniques. Start by establishing a User Group Definition framework. This creates a defined set of user groups to prioritize for the project, which allows for focused recruiting efforts. Without this structure, your participant screening lacks direction. You must also conduct a Risk Assessment to identify high-risk areas lacking user insights. This helps the team understand where acting without data creates the most danger. Next, define Project Constraints including specific budget and timeline limits. These boundaries dictate what is actually feasible for your team. If direct user contact is impossible, create Existing Models verified with external sources like customer service. This mitigates the risk of incorrect assumptions when you cannot reach users directly. Once these prerequisites are in place, you can move to the four-step selection process.

Key Points:

The Four-Step Selection Process

Once those prerequisites are set, you move into the four-step selection process that transforms constraints into a concrete plan. The first step is to define primary user groups, which means creating a framework that describes the main types of users you need to reach. This output gives you a defined set of groups to prioritize for the project, ensuring your recruiting efforts are focused rather than scattered. By narrowing your target audience early, you avoid the common mistake of trying to recruit everyone, which dilutes your insights and wastes valuable time. Next, you determine research goals and scope by deciding exactly what you want to learn from the study. You identify the primary topics to be covered, which results in clear research objectives and a topic coverage list. This step forces you to articulate specific questions, because every technique you choose must serve one of those defined goals. When your objectives are sharp, it becomes much easier to match them with the right methodological tools later in the process. The third step involves selecting techniques based on project phase and type, which requires applying specific decision logic to your situation. For task-based applications, you conduct user interviews before designing to understand needs, then perform usability testing on a prototype later. In contrast, for content sources, you start with contextual inquiry to observe behavior, then include a card sorting exercise later to validate structure. If you have room for at least two rounds of research, use the first round during the define or early design phase, and the second round before development starts. Finally, you plan logistics and resources to ensure the study can actually happen within your constraints. This means determining how to get participants through rigorous recruiting and screening, as well as setting appropriate participant compensation. You also need to determine space, equipment, and software needs based on whether the research is in-person or remote, along with deciding how information will be captured. This logistical plan covers recruitment, compensation, environment, and data capture tools, turning your strategic choices into an executable reality. With this framework in place, you can see how these steps apply to a specific task-based application scenario.

Key Points:

Worked Example: Task-Based Application

Let’s apply this framework to a specific scenario where your team is designing a new task-based application with a two-round research window. Because the project type dictates the method, you’ll conduct user interviews in the first round to understand user needs before designing any interfaces. This happens during the Define phase or early in the Design phase, which means you’re gathering foundational insights while the scope is still flexible. For the second round, you’ll perform usability testing on a prototype before development starts, ensuring the design actually works for real users. This timing strategy validates your design decisions against actual behavior, so you don’t waste engineering resources on untested concepts. By applying the two-round timing strategy, you confirm usability before coding begins, creating a feedback loop that reduces risk. This sequence ensures insights inform design and validation confirms usability, demonstrating how technique selection aligns with project phase. Now that we’ve seen the ideal workflow, let’s look at what happens when those constraints shift or assumptions go unverified.

Key Points:

Avoiding Common Pitfalls

Which of these three pitfalls is most likely to impact your current project's timeline? You might be using an unvalidated model, which introduces higher risk that your assumptions will be incorrect. The recovery is simple: verify the model with sources outside the project team, such as customer service or training groups. A verified model is better than having no model at all, so make that check before you proceed. Another common issue is a lack of familiarity with techniques, which can cause practitioners to struggle with determining the right research approach. To recover, refer to standard tables of commonly used research techniques and their typical use cases to match technique to utility. This ensures you are selecting methods based on established best practices rather than guesswork. Finally, unrealistic expectations often derail projects when teams deviate from the defined performance profile or project constraints. Stick strictly to the defined performance profile and project constraints, including budget and timeline limits. This ensures candidates and team members are prepared for the specific research demands, keeping the project on track and effective.

Key Points: