# How to recruit research participants who can change what you learn.

Write a recruitment brief around the real task, include missing perspectives, and invite participation without asking for praise. Includes a hypothetical example and reusable worksheet.

## The direct answer

Recruit user research participants by defining the experience relevant to your question, writing clear selection criteria, and choosing channels that can reach those people. Plan participation arrangements before invitations, keep screening proportionate, and record who your recruitment method misses. A useful group can challenge a design; it does not automatically represent the whole audience or prove how common a need is.


- Author: Daniel Ziedins (https://www.danielziedins.com)
- Published: Oct 21, 2026
- Updated: Oct 21, 2026
- Scripture: James 1:19
- Read: 7 min
- URL: https://www.agent-six33.com/journal/how-to-recruit-user-research-participants

> Let every person be quick to hear, slow to speak, slow to anger.
> — James 1:19

The people easiest to ask are not always the people best placed to answer the question. A supportive colleague may know the website too well to reveal a first-visit problem. A follower who enjoys your writing may never have needed the service you are investigating. Recruiting only encouragement can leave a team with warm feedback and the original uncertainty intact.

This guide offers an original recruitment-planning aid for low-risk work with adults. It is not a legal compliance checklist, a consent form, or a safeguarding process. Work involving children, vulnerable circumstances, sensitive subjects, or essential services needs appropriate expertise and review. A small project is not exempt from treating a person's time, choices, and information with care.

## 1. Start with the experience that matters.

Write your research question before writing an invitation. If you need to understand how newcomers prepared for a first session, recent first-time participants are relevant in a way that long-standing organisers may not be. If you are investigating an unfinished task, people who abandoned it may know something that completed registrations cannot explain. The relevant experience should determine the brief, not the size of an existing mailing list.

Describe the experience in terms a person can recognise. Avoid requiring someone to agree that your proposed solution would help before they can participate. That would filter for your conclusion. Also distinguish a task condition from a personal characteristic. Ask only for information that helps answer the question or arrange participation; a detailed biography is not a substitute for a clear reason to include somebody.


## 2. Write criteria, exclusions, and missing perspectives.

GOV.UK's participant guidance emphasises actual or likely users and attention to different access needs. Use that as a starting boundary, then explain your own selection decisions. Record which experience is required, which differences you want to explore, and any condition that makes the proposed session inappropriate. Keep the reason beside each criterion so a convenient restriction cannot quietly become a claim about the audience.

Maintain a missing-perspectives line from the beginning. A session offered only during working hours may miss people whose schedules differ. A web-only invitation may miss those who rely on another person or channel. You may not resolve every gap in one round, but you can stop the report from saying users when it really means people who saw this invitation and could attend under these conditions.


## 3. Choose recruitment channels that fit the question.

Compare channels for the experience you need, not just response speed. An opt-in invitation to recent participants might suit a preparation question; an approved community notice might reach people who have never registered. A gatekeeper's opinion can help you understand the setting, but it is not automatically an account from the people using the service. Keep the two source types separate.

Ask permission before posting in a group or approaching people through an organisation. Describe the research accurately and make declining uncomplicated. If a colleague helps arrange introductions, agree what information is actually necessary to share. Do not add people to a marketing list because they expressed research interest, and do not imply that giving a positive answer is the price of being helpful.


## 4. Make participation understandable before scheduling.

Draft a plain invitation with the purpose, activity, expected commitment, contact method, and how to ask questions or decline. State whether the session concerns a prototype or a working service. Explain any planned recording and who would see the material through your agreed information and consent process. This worksheet helps you notice those decisions; filling it in does not itself establish informed consent.

Ask about participation arrangements in a way that does not demand an unnecessary diagnosis or personal history. A person might need a different format, communication method, device setup, or time. Arrange what you can support before confirming the session. If compensation or expenses are offered, state the terms through the appropriate process and do not make favourable feedback a condition. Keep the invitation separate from a request for a testimonial.


**Prepare the observed task:** Give people a clear goal and make the assistance boundary visible.  
https://www.agent-six33.com/journal/how-to-run-a-small-usability-test

## 5. Work through a hypothetical recruitment brief.

Imagine a team trying to understand confusing arrival information for a community workshop. This is a hypothetical example, not a SIX33 study. The first draft asks enthusiastic supporters to review our improved welcome page. That wording selects for goodwill and points attention toward the proposed page before establishing how people prepared for the session.

A better brief names adults who recently prepared to attend for the first time, including people who asked for clarification or did not complete the arrival process where an appropriate invitation route exists. The question is how they found the time, place, and contact information. Prior experience with the team and the channel used for preparation are context to record, not reasons to manufacture a balanced-looking group.

Suppose the eventual sessions include only people who successfully arrived after a direct message from the coordinator. The team can learn from those experiences, but it cannot describe the findings as the experience of every newcomer or of people who never reached the venue. The next recruitment decision might deliberately seek a different preparation route. The useful output is a visible limitation and a better next question, not an unsupported claim of representativeness.


## 6. Review who took part, not just how many.

Before the first session, check the achieved group against the question and the participation arrangements. Keep a cancellation or non-response as a recruitment status, not an opinion about the service. A person who did not reply has not rejected your idea. If a criterion changes, record the reason and the version of the brief so the final account can explain how the group was assembled.

Afterward, report the channels, relevant experience, exclusions, and gaps alongside the session count. Avoid presenting a convenience group as a population estimate. The method and question determine what further research is appropriate; there is no universal participant number that certifies a need, a product, or an impact claim. Repeated sessions with highly familiar people may answer a different question from a first encounter.

Finally, follow the agreed handling and retention arrangements for contact and screening material. Keep the recruitment record separate from public findings, using private source pointers where needed. A public report usually needs to explain why a participant's experience was relevant, not reveal who they are. Recruitment has done useful work when it makes the eventual claim narrower, clearer, and more open to being challenged.


**Ask about the recent experience:** Use neutral questions once the relevant participants and arrangements are clear.  
https://www.agent-six33.com/journal/first-five-customer-interviews


## Research recruitment brief and coverage worksheet

Copy this blank template into your private working document. It contains no journal notes or tool drafts.

```markdown
# Research recruitment brief and coverage worksheet

Project, brief version, and date: [name / version / date]
Research question and next decision: [question / decision]
Method and proposed activity: [interview / observed task / other]
Owner and required review: [person / appropriate review before recruiting]

## Relevant experience
Required recent experience or likely task: [plain criteria / why relevant]
Different contexts to explore: [channels / familiarity / access methods / other task-relevant differences]
Exclusions and reasons: [appropriateness / avoid convenience-only restrictions]
Who this plan may miss: [perspectives / recruitment limitations]

## Invitation and participation arrangements
Approved recruitment channels and permission: [where / owner / permission]
Neutral invitation purpose: [what you want to learn, not praise for a solution]
Activity, expected commitment, and prototype limits: [details]
Contact, questions, declining, and stopping process: [clear arrangements]
Information and consent process: [reviewed material / recording choices / agreed use]
Requested format, communication, or device arrangements: [arrange privately]
Compensation or expense terms, if offered: [process / not conditional on favourable answers]
Minimum screening information needed: [each field / reason]
Access, handling, and retention arrangements: [approved process / owner / review date]

## Recruitment review
Participant code: [private ID, contact details stored separately where practical]
Relevant experience and channel: [bounded context]
Status: [invited / opted in / confirmed / cancelled / no response / other]
Arrangements confirmed: [yes / unresolved action]
Coverage gaps and changed criteria: [gap / revision / reason]

## Reporting boundary
What this group can help investigate: [bounded question]
Who or what it does not represent: [missing perspectives / frequency limits]
Next recruitment decision and owner: [action / person]

This is a planning aid, not a consent form, legal compliance checklist, or safeguarding process. Do not publish completed screening or contact details, and do not treat non-response as an opinion about the idea.
```



> **The short version:** Recruit for a relevant experience and an honest challenge, not for the answer you hope to hear.


## Questions

### Who should I recruit for a small user research project?

Choose people with the actual or likely task experience relevant to your question. Record the contexts you need to explore and who your recruitment channels may miss. Supportive followers, colleagues, and gatekeepers are not automatically substitutes for the people doing the task.

### Can I use friends or colleagues in a usability test?

They can help rehearse the script and identify obvious technical problems. If they genuinely match the research criteria, their session may provide relevant evidence, but familiarity can change how they use the resource. Record that context and do not present a rehearsal as research with unfamiliar users.

### Does a small research group represent my whole audience?

Not automatically. Recruitment channels, availability, selection criteria, familiarity, and missing perspectives limit what a group can establish. Explain those limits beside the findings rather than converting a small set of sessions into population percentages.

### Is a recruitment worksheet a consent form?

No. It helps a team plan the information, participation arrangements, review, and handling decisions that need attention. It does not establish informed consent or replace the appropriate process for the people, subject, risks, and jurisdiction involved.


## Sources

- GOV.UK Service Manual: finding research participants: https://www.gov.uk/service-manual/user-research/find-user-research-participants — Reference for actual or likely users, participation arrangements, and recruitment limitations. The brief and workshop example are original working aids, not a reported study.
- GOV.UK Service Manual: moderated usability testing: https://www.gov.uk/service-manual/user-research/using-moderated-usability-testing — Further reading on the task-based sessions a recruitment brief may support. No endorsement or universal participant-count rule is implied.



## Explore the wider topic

- Research and testing: https://www.agent-six33.com/journal/topics/research-and-testing

— Daniel Ziedins · https://www.danielziedins.com · AGENT SIX33
https://www.agent-six33.com/journal/how-to-recruit-user-research-participants