guide 4 min read
Recruit Participants Who Can Inform Your Design
Useful research recruitment starts with the behavior you need to understand, not a broad demographic label.
THE SHORT ANSWER
What you need to know
Useful research recruitment starts with the behavior you need to understand, not a broad demographic label. Define recent relevant experience, include meaningful differences in context, and screen without revealing the preferred answer. Make participation practical and accessible. Document who is missing from the sample so design decisions reflect the evidence available rather than an imagined average user.
Key takeaways
- Recruit around real behavior.
- Select meaningful context differences.
- Avoid leading screeners.
- Keep sample limits visible.
Recruit for the question you need to answer
Begin with the decision the research will inform. A team redesigning an equipment request form needs people who recently requested equipment, people who approve requests, and possibly people whose requests were rejected. Recruiting anyone who works in an office will produce a much looser picture. Specify a relevant time window and explain why that experience matters.
In a hypothetical internal operations product, the immediate question might be whether requesters understand when approval is required. Recruit people with routine and unusual requests rather than selecting only enthusiastic power users. Keep job titles as context, but avoid using titles as substitutes for actual behavior. Someone with a junior title may handle more relevant requests than a senior manager.
Choose differences that could change the design
Build a small recruitment matrix around conditions that may produce different needs. These could include device access, familiarity with the task, assistive technology use, language comfort, or authority to approve a request. Do not add categories simply to make the matrix look comprehensive. Each dimension should connect to a design risk you can explain.
For equipment requests, compare an employee with a dedicated laptop against someone who completes forms on a shared device. Their privacy and interruption needs may differ even when their job titles are similar. Avoid treating one participant as the representative of an entire group. Note variations within groups and recruit further when an important unanswered difference emerges during sessions.
Screen without teaching the answer
Ask factual questions about recent activity before asking preferences. “When did you last request equipment, and how did you do it?” is more useful than “Would a simpler request form help you?” The second question advertises the team’s intended solution. A short screener should identify relevant experience without making participants feel they must demonstrate expertise.
Separate recruitment details from research prompts so scheduling does not prime the session. Explain the topic honestly, but avoid describing the exact design hypothesis. Offer participation options that match the task and the person’s access needs. Confirm whether a remote session requires software installation, a quiet space, or a device they cannot reasonably provide.
Record the limits and protect the session
Keep a recruitment record containing the relevant criteria, completed participation, and remaining gaps. Store only the personal information needed to arrange and conduct the work. Provide clear information about the session, recording, and how notes will be used. Make withdrawal practical rather than a line buried in a document.
After sessions, compare the achieved sample with the original matrix. If every participant had uninterrupted desktop access, do not generalize findings about shared devices. Write that limitation beside the recommendation. Use the missing perspective to guide the next recruitment round or constrain the initial design, especially where an assumption could exclude someone from a core task.
- Tie every criterion to a research decision.
- Check recent behavior before opinions.
- Explain participation requirements in advance.
- Record sample gaps beside recommendations.
When sessions produce findings, keep participant context attached and prioritize the consequence for the task rather than the number of comments about a screen.Prioritize Design Findings by Task Impact
Common questions
Can existing customers be enough?
They can answer questions about their current workflow, but they may miss barriers experienced by people who never adopted the product. Match the recruitment source to the decision being studied.
Should participants be paid?
Consider a fair recognition of time and participation burden. Decide the approach before recruitment and communicate it clearly; do not make compensation depend on agreeing with the design.
What if recruitment is difficult?
Narrow the question or test a lower consequence assumption with available participants. Keep the missing audience explicit and avoid describing a convenience sample as complete validation.
References & further reading
These primary references support the background. The practical frameworks and illustrative examples are written for this guide.
Prepared with AI assistance. Examples are illustrative; no client results are implied. Read our editorial approach.