Master the four-step process of planning user research, from defining primary user groups to sharing synthesized findings. Learn to select appropriate methods like interviews or card sorting based on specific goals and constraints. Handle common pitfalls such as lack of analytics or unclear stakeholder expectations by establishing clear outputs early.
Learning Objective: By the end of this lesson, learners will be able to construct a comprehensive user research plan that defines primary user groups, selects appropriate methods, addresses logistical constraints, and sets clear synthesis expectations.
Before we dive into the full research plan, let's recall how you typically define primary user groups. You already create a framework describing the main types of users the team is designing for, which anchors your recruitment efforts. This defined set of primary user groups ensures you focus efforts in planning research and recruiting users effectively. If product analytics are unavailable, you identify other methods to build a foundation of understanding. This prevents the common pitfall where practitioners feel unprepared due to a lack of data. You also identify the highest areas of risk if acting without user insights, which guides your strategic choices. By establishing this baseline, you ensure that every subsequent decision in the research plan is grounded in real user needs. This initial clarity prevents scope creep and keeps the team aligned on who we are actually designing for.
Key Points:
Create a framework describing the main types of users the team is designing for.
Use this framework to focus efforts in planning research and recruiting users.
If product analytics are unavailable, identify other methods to build a foundation of understanding.
Identify the highest areas of risk if acting without user insights.
With those primary user groups defined, you move into structuring the research plan by working directly with your team and stakeholders to set clear research goals and objectives. This alignment ensures everyone understands exactly why the research is being conducted and what specific problems need solving. You then choose one or more methods, such as user interviews, usability studies, card sorting, or contextual inquiry, that will help meet those goals effectively. The selection depends entirely on whether you need to understand user motivations or validate specific design decisions. Once the method is selected, you must address several logistical considerations to ensure the study can happen. You need to determine the budget and timeline, which dictates how many activities you can realistically conduct within the available resources. Recruitment is another major factor, requiring screening questions to ensure participants fall into the targeted user groups you identified earlier. You also need to decide how participants will be compensated and what space, equipment, and software needs exist for in-person or remote sessions. To keep the execution tight, you should create research method scripts and guides that include a scripted opening for each session. These guides provide a detailed breakdown of topics, questions, tasks to observe, and activities for the user to perform during the interaction. Having this structure in place prevents scope creep and ensures consistent data capture across all sessions, regardless of who is facilitating. It turns abstract goals into concrete actions that any team member can follow reliably. Finally, you must define target research outputs early to prevent mismatched expectations between the team and the customer. This includes a brief description of how synthesis will be performed and the expected deliverables, ensuring stakeholders know what they will receive. By clarifying the synthesis plan upfront, you avoid the common pitfall of stakeholders expecting insights that the chosen methods cannot provide. This documentation serves as the contract for what the research will actually achieve. With the plan structured and expectations aligned, you are ready to move into the execution phase where these methods come to life in a worked example.
Key Points:
Set clear research goals and objectives with the team and stakeholders.
Choose methods (e.g., user interviews, usability studies, card sorting, contextual inquiry) that meet those goals.
Address key considerations: budget, timeline, recruitment screening questions, compensation, and space/equipment needs.
Define target research outputs, including how synthesis will be performed and expected deliverables.
Let’s look at a task-based application. You conduct user interviews during the Define phase to understand your users before designing. Then, you run usability testing on a prototype before development starts to validate the design. This two-round approach ensures you address risks early. Alternatively, for a content source, you might use contextual inquiry followed by a card sorting exercise. This sequence helps organize information architecture effectively. Your research plan must include detailed scripts. These scripts need a scripted opening, a breakdown of topics, specific questions, tasks to observe, and activities for the user to perform. This structure keeps sessions focused and consistent. By following these steps, you create a solid foundation for your research. You’ll have clear insights to guide your design decisions.
Key Points:
Step 1: Conduct user interviews during the Define phase to understand users.
Step 2: Conduct usability testing on a prototype before development starts to validate design.
Alternative: Use contextual inquiry followed by a card sorting exercise for content sources.
Ensure scripts include a scripted opening, topic breakdown, questions, tasks to observe, and activities.
Now you execute the plan by following the chosen methods, which often involves multiple rounds of research to build a complete picture. You might run one round during the Define phase to understand users, then a second round before development starts to validate the design. As you conduct sessions, use the scripted opening and specific tasks from your research method guides to keep everything consistent. If you need structure, templates and tutorials from usability.gov provide resources to start activities and ensure you don't miss steps. Once data collection ends, perform research synthesis exactly as you outlined in the initial planning phase to maintain alignment with your goals. This step transforms raw observations into synthesized insights, turning scattered notes into patterns that the team can use. You then share these defined outputs with stakeholders, ensuring everyone sees the same evidence and understands the implications for the design. This transparency prevents mismatched expectations and gives the team a clear foundation for the next phase of work.
Key Points:
Follow the chosen method(s), potentially involving multiple rounds of research.
Perform research synthesis as planned in the initial planning phase.
Share synthesized insights and defined outputs with the team and stakeholders.
Use templates and tutorials from usability.gov to kick-start activities if needed.
When product analytics are unavailable, it is natural to feel unprepared, but you can simply use other user research methods to uncover valuable insights. This approach builds a solid foundation of understanding without relying on historical data. Another frequent issue involves stakeholders holding mismatched expectations regarding results, which often leads to friction during the review phase. To prevent this, you should define target research outputs and the synthesis plan early in the planning phase. This ensures that expectations are met for the team and customer before any sessions begin. By applying mitigation strategies for common pitfalls like lack of analytics or unclear expectations, you safeguard your project against these predictable hurdles. You now have the complete framework to construct a comprehensive user research plan that defines primary user groups, selects appropriate methods, addresses logistical constraints, and sets clear synthesis expectations. The work is no longer abstract; it is a structured process you can execute with confidence. Take this plan to your next stakeholder meeting and anchor the conversation in shared goals rather than assumptions.
Key Points:
Pitfall: Lack of analytics makes practitioners feel unprepared.
Recovery: Use other user research methods to uncover valuable insights.
Pitfall: Stakeholders have mismatched expectations regarding results.
Recovery: Define target research outputs and synthesis plan early to ensure expectations are met.