Product and user experience research can involve people who set priorities, investigate user needs, design interactions, or build the product. These responsibilities may be combined in a small team and separated in a large one. Identify the activity and context that matter to the study.
Define the experience before choosing titles
Start with the decision your study needs to understand. Establish whether participants personally used, evaluated, selected, approved, or implemented the product or process. A title is a sourcing clue; it is not sufficient evidence of those responsibilities. The roles below are examples to investigate, not universal organization charts.
| Perspective | Possible roles | Experience to confirm |
|---|---|---|
| Product direction | Product managers; product development leaders | Ownership of the relevant roadmap, prioritization, or evaluation |
| Research and design | User researchers; experience and interface designers | Recent work with the specific research or design task and tools |
| Development and delivery | Engineering; research and development professionals | Hands-on responsibility for implementation, experimentation, or technical constraints |
Questions to refine the participant profile
- Which part of the product lifecycle must participants have worked on?
- Is the study about choosing a tool, using it, or understanding the underlying workflow?
- Does the team need individual contributors, managers, or a planned comparison between them?
Plan meaningful comparisons
Consider product type, team structure, role seniority, current tools, and recent project experience. If a survey will feed into later groups, plan permission to recontact and check availability for both phases. Do not assume everyone with a design title performs the same tasks.
Avoid a misleading shortcut
Experience researching other users does not make someone a qualified end user of every product. Likewise, software development, scientific research, and user research are different activities; confirm the relevant domain before accepting a broad “research” title.
Turn the profile into a recruitment brief
Record the required experience, its recency, relevant organization characteristics, and the evidence that can reasonably confirm eligibility. Keep preferred characteristics separate from essential qualifications. Ask candidates for a short, nonconfidential example of their own involvement rather than a detailed account of an employer’s plans.
Agree on how unclear cases will be reviewed before outreach. If the profile is too narrow to recruit, revisit the research objective and preferred criteria with the researcher rather than substituting a different role without approval.
