Latest / 5 Minute UX / When To Schedule Each Round of Research
Transcript
- 0:08This lesson is When To Schedule Each Round of Research. Let's
- 0:11get started.
- 0:18Before scheduling, you must assess project capacity to
- 0:21ensure there is room for at least two rounds of research. If
- 0:24your organization is unfamiliar with user research or exhibits
- 0:27resistance, propose only one round initially. This strategic
- 0:29compromise allows you to use the results of that first round to
- 0:32build a strong case for including more research later.
- 0:35You select the technique that brings the most value to the
- 0:38designer, project team, and business stakeholders right now.
- 0:40To provide focus and scope, you answer eight specific planning
- 0:43inputs before finalizing the schedule. You define why you are
- 0:46testing, including your goals and objectives, alongside the
- 0:49budget and timeline constraints. You identify the highest areas
- 0:52of risk if acting without user insights, and determine the
- 0:54primary user groups to include. You also specify recruitment and
- 0:57screening methods for participants, along with their
- 1:00compensation and any space, equipment, or software needs.
- 1:03These inputs are often documented in a user research
- 1:05plan discussed with the project team and key stakeholders. By
- 1:08clarifying these prerequisites and conditions, you establish
- 1:11the organizational context necessary for successful
- 1:13execution. This upfront planning prevents scope creep and ensures
- 1:16everyone understands the value of the upcoming discovery phase.
- 1:19With these inputs defined, you are ready to determine when to
- 1:22conduct Round One to better understand your users.
- 1:31You conduct the first round during the Define phase or early
- 1:34in the Design phase, which is often called Discovery. The
- 1:36primary goal here is to better understand the users before you
- 1:39start designing any interfaces. This initial research
- 1:42establishes a foundation of user needs that informs every
- 1:45subsequent design decision you make. It prevents you from
- 1:48building solutions based on assumptions rather than actual
- 1:50user behavior. For task-based applications, you should conduct
- 1:54user interviews before designing. These conversations
- 1:56reveal how people currently perform their work and what
- 1:59tools they rely on daily. You learn about their workflows,
- 2:02their pain points, and their unmet needs directly from the
- 2:05source. This qualitative data guides your design choices and
- 2:07ensures the application supports real-world tasks. If you are
- 2:11designing a content source, start with contextual inquiry or
- 2:13a card sorting exercise. Contextual inquiry lets you
- 2:16observe how users find and consume information in their
- 2:19natural environment. Card sorting helps you understand how
- 2:22users mentally categorize content, which informs your
- 2:24navigation structure. Both techniques provide deep insights
- 2:27into user mental models before you commit to a specific layout.
- 2:30Understanding users first allows you to validate the design later
- 2:33with confidence. You now have the user insights necessary to
- 2:36move toward testing your prototypes.
- 2:44You schedule this second round before development starts, which
- 2:47ensures you validate the design and allow for iteration. This
- 2:50timing is critical because it lets you test a design, change
- 2:53it based on results, and retest the new design. You’re catching
- 2:56errors before code is written, which means you can pivot
- 2:58without expensive refactoring. The goal here is strictly
- 3:01validation, so you’re checking if the solution actually works
- 3:04for the users you identified in Round One. For task-based
- 3:06applications, you perform usability testing on a
- 3:09prototype. You watch users attempt specific tasks to see
- 3:11where they stumble or succeed. This direct observation reveals
- 3:14friction points that interviews alone might miss. It’s about
- 3:17verifying that the interface supports the workflow you’re
- 3:19trying to enable. If you’re building content sources, you
- 3:22run a usability test focused on content categorization. You’re
- 3:25checking if users can find what they need within your
- 3:27information architecture. This might involve tree testing or
- 3:30card sorting exercises to validate your navigation
- 3:32structure. You’re ensuring the content is organized in a way
- 3:35that makes sense to your audience, not just your team.
- 3:44To select the right technique, you first check the product
- 3:47type, determining if it is a task-based application or a
- 3:49content source. You then verify the current phase, asking
- 3:52whether you are in the Define or Discovery stage for Round One,
- 3:55or pre-development for Round Two. This two-step check ensures
- 3:58you match the method to the moment, applying technique
- 4:01selection rules for task-based applications versus content
- 4:03sources with precision. For task-based applications in Round
- 4:06One, you conduct user interviews before designing to understand
- 4:09user needs. If you are building a content source, you start with
- 4:12contextual inquiry or a card sorting exercise instead. In
- 4:15Round Two, you validate the design by performing usability
- 4:18testing on a prototype for task- based apps, or running a
- 4:20usability test focused on content categorization for
- 4:23content sources. This second round allows for testing a
- 4:25design, changing it based on results, and retesting the new
- 4:28design to ensure it works. By aligning these specific
- 4:31techniques with project phases and product types, you create a
- 4:34research schedule that delivers actionable insights. This
- 4:36structured approach prevents wasted effort and ensures every
- 4:39study addresses the highest areas of risk identified in your
- 4:42planning inputs.
- 4:49You need to conduct more than one round of research because
- 4:52critical issues often hide under other problems or get
- 4:54unintentionally introduced in new designs. If you stop after
- 4:57just one phase, you’ll miss those hidden flaws that only
- 4:59surface when the design evolves. [pause:1s] To ensure consistency
- 5:02across these rounds, create a simple checklist of steps and
- 5:05deploy a robust research operations framework. This
- 5:07structure allows more team members to conduct research
- 5:10frequently without relying on a single expert to remember every
- 5:13detail. You must also clarify expectations up front by
- 5:15outlining the process, specifying the number of rounds,
- 5:18their length, who attends, and the specific format for each.
- 5:20When you aim for five to eight users per group for qualitative
- 5:23usability tests, you get sufficient data without wasting
- 5:26time. Planning a two-round user research schedule that aligns
- 5:28specific techniques with project phases and product types
- 5:31prevents these common pitfalls. Now that you have the framework,
- 5:34you’re ready to apply this scheduling strategy to your next
- 5:37project’s discovery and validation phases.
- 5:41Welcome to The Take. I'm joined by a fellow practitioner and
- 5:44together we're going to dig into When To Schedule Each Round of
- 5:47Research — what it means in practice and what's worth
- 5:50remembering.
- 5:51[HOST] That part about proposing just one round to skeptical
- 5:54teams really resonated with me. It feels like a necessary
- 5:57compromise to build trust before demanding more resources.
- 6:00[LEARNER] Absolutely. I’ve burned bridges by insisting on a
- 6:04full two-round plan when the team wasn’t ready. Starting
- 6:06small lets the data speak for itself, which is harder to argue
- 6:10with than a methodology chart. [HOST] True, but the risk is
- 6:13that the first round becomes the only round if you don’t have a
- 6:16pre-agreed path to validation. You need to plant the seed for
- 6:19Round Two during the planning of Round One. [LEARNER] That’s the
- 6:23tricky part. How do you secure budget for a future study that
- 6:26hasn’t happened yet? I usually frame it as a contingency for
- 6:29high-risk features identified in the discovery phase. [HOST]
- 6:32Smart move. It ties the second round directly to business risk
- 6:35rather than just design curiosity. Speaking of risk, the
- 6:38distinction between task-based apps and content sources felt
- 6:41very rigid in the lesson. [LEARNER] I felt that too. In
- 6:44practice, most products are hybrids. You've a dashboard that
- 6:47tracks tasks but also serves as a knowledge base for new hires.
- 6:51Which bucket do you put that in? [HOST] It forces you to
- 6:53prioritize. If the primary value is workflow efficiency, treat it
- 6:57as task-based first. If the primary friction is finding
- 7:00information, lean into the content strategies. [LEARNER]
- 7:03Makes sense. I’d argue AI is gonna blur this line even more
- 7:06soon. Generative interfaces change how users interact with
- 7:09both tasks and content simultaneously. [HOST] That’s a
- 7:12fair point. If the interface adapts to the user, our
- 7:14traditional usability testing metrics might become less
- 7:17relevant. We might need to measure intent alignment instead
- 7:20of click paths. [LEARNER] Exactly. We’ll need to validate
- 7:23whether the AI understood the context, not just if the button
- 7:26worked. The core principle of validating before development
- 7:29still holds, though. [HOST] It does. The timing remains
- 7:32critical regardless of the interface type. Catching errors
- 7:35before code is written saves the most money, whether you’re
- 7:38testing a static prototype or a dynamic agent. [LEARNER] I’ll
- 7:42stick to that framework for now. It keeps the team focused on
- 7:45risk reduction rather than tool obsession. [HOST] Agreed.
- 7:48Structure protects us from chasing shiny objects while
- 7:51ensuring we actually solve user problems.