Determine when to schedule discovery research in the Define phase versus validation research before development. Select appropriate techniques like interviews or usability testing based on whether the product is task-based or a content source. Build a case for multiple rounds by addressing organizational resistance and defining clear scope inputs.
Learning Objective: By the end of this lesson, learners will be able to plan a two-round user research schedule that aligns specific techniques with project phases and product types.
Before scheduling, you must assess project capacity to ensure there is room for at least two rounds of research. If your organization is unfamiliar with user research or exhibits resistance, propose only one round initially. This strategic compromise allows you to use the results of that first round to build a strong case for including more research later. You select the technique that brings the most value to the designer, project team, and business stakeholders right now.
To provide focus and scope, you answer eight specific planning inputs before finalizing the schedule. You define why you are testing, including your goals and objectives, alongside the budget and timeline constraints. You identify the highest areas of risk if acting without user insights, and determine the primary user groups to include. You also specify recruitment and screening methods for participants, along with their compensation and any space, equipment, or software needs.
These inputs are often documented in a user research plan discussed with the project team and key stakeholders. By clarifying these prerequisites and conditions, you establish the organizational context necessary for successful execution. This upfront planning prevents scope creep and ensures everyone understands the value of the upcoming discovery phase. With these inputs defined, you are ready to determine when to conduct Round One to better understand your users.
Key Points:
Assess capacity: Ensure the project has room for at least two rounds of research.
Handle resistance: If the organization is unfamiliar with research, propose only one round initially to build a case for more later.
Define scope inputs: Answer eight specific questions including goals, budget, timeline, risk areas, user groups, recruitment methods, compensation, and equipment needs.
Document the plan: Discuss the user research plan with the project team and key stakeholders before scheduling.
You conduct the first round during the Define phase or early in the Design phase, which is often called Discovery. The primary goal here is to better understand the users before you start designing any interfaces. This initial research establishes a foundation of user needs that informs every subsequent design decision you make. It prevents you from building solutions based on assumptions rather than actual user behavior.
For task-based applications, you should conduct user interviews before designing. These conversations reveal how people currently perform their work and what tools they rely on daily. You learn about their workflows, their pain points, and their unmet needs directly from the source. This qualitative data guides your design choices and ensures the application supports real-world tasks.
If you are designing a content source, start with contextual inquiry or a card sorting exercise. Contextual inquiry lets you observe how users find and consume information in their natural environment. Card sorting helps you understand how users mentally categorize content, which informs your navigation structure. Both techniques provide deep insights into user mental models before you commit to a specific layout.
Understanding users first allows you to validate the design later with confidence. You now have the user insights necessary to move toward testing your prototypes.
Key Points:
Timing: Conduct during the Define phase or early in the Design phase (Discovery).
Goal: Better understand the users before designing.
Task-based apps: Conduct user interviews before designing.
Content sources: Start with contextual inquiry or a card sorting exercise.
You schedule this second round before development starts, which ensures you validate the design and allow for iteration. This timing is critical because it lets you test a design, change it based on results, and retest the new design. You’re catching errors before code is written, which means you can pivot without expensive refactoring. The goal here is strictly validation, so you’re checking if the solution actually works for the users you identified in Round One.
For task-based applications, you perform usability testing on a prototype. You watch users attempt specific tasks to see where they stumble or succeed. This direct observation reveals friction points that interviews alone might miss. It’s about verifying that the interface supports the workflow you’re trying to enable.
If you’re building content sources, you run a usability test focused on content categorization. You’re checking if users can find what they need within your information architecture. This might involve tree testing or card sorting exercises to validate your navigation structure. You’re ensuring the content is organized in a way that makes sense to your audience, not just your team.
Key Points:
Timing: Conduct before development starts.
Goal: Validate the design and allow for iteration.
Task-based apps: Perform usability testing on a prototype.
Content sources: Run a usability test focused on content categorization.
To select the right technique, you first check the product type, determining if it is a task-based application or a content source. You then verify the current phase, asking whether you are in the Define or Discovery stage for Round One, or pre-development for Round Two. This two-step check ensures you match the method to the moment, applying technique selection rules for task-based applications versus content sources with precision.
For task-based applications in Round One, you conduct user interviews before designing to understand user needs. If you are building a content source, you start with contextual inquiry or a card sorting exercise instead. In Round Two, you validate the design by performing usability testing on a prototype for task-based apps, or running a usability test focused on content categorization for content sources.
This second round allows for testing a design, changing it based on results, and retesting the new design to ensure it works. By aligning these specific techniques with project phases and product types, you create a research schedule that delivers actionable insights. This structured approach prevents wasted effort and ensures every study addresses the highest areas of risk identified in your planning inputs.
Key Points:
Check product type: Is it a task-based application or a content source?
Check phase: Are you in Define/Discovery (Round 1) or pre-development (Round 2)?
Select technique: Match interviews/contextual inquiry to Round 1; match usability testing to Round 2.
Iterate: Use Round 2 results to change the design and retest if necessary.
You need to conduct more than one round of research because critical issues often hide under other problems or get unintentionally introduced in new designs. If you stop after just one phase, you’ll miss those hidden flaws that only surface when the design evolves. [pause:1s] To ensure consistency across these rounds, create a simple checklist of steps and deploy a robust research operations framework. This structure allows more team members to conduct research frequently without relying on a single expert to remember every detail. You must also clarify expectations up front by outlining the process, specifying the number of rounds, their length, who attends, and the specific format for each. When you aim for five to eight users per group for qualitative usability tests, you get sufficient data without wasting time. Planning a two-round user research schedule that aligns specific techniques with project phases and product types prevents these common pitfalls. Now that you have the framework, you’re ready to apply this scheduling strategy to your next project’s discovery and validation phases.
Key Points:
Uncover hidden issues: Conduct more than one round to find problems hiding under other issues or introduced in new designs.
Ensure consistency: Create a checklist of steps and deploy a research operations framework.
Clarify expectations: Outline the process up front, specifying the number of rounds, length, attendees, and format.
Set participant size: Aim for five to eight users per group for qualitative usability tests.