When to run this checklist
Run it in the days before the first session of a moderated study, once recruits are confirmed and before anyone is in the room or on the call. Run it again when a study adds a new format part-way, such as a round of usability tests after the interviews, because the materials and set-up groups change with the format.
The person who ticks it is the researcher running the study, with whoever owns data protection on the consent and data lines. When the study is one of several in a research programme, the customer research programme playbook keeps recruitment, consent and the repository standing across studies; this list is the gate for one study. A survey sent to a sample has its own gate, the survey launch checklist, because it needs a frame and a draw rather than recruits and a rehearsal. When the sessions point to a change worth testing on the live site, the A/B test launch checklist gates that test.
Each format has a tutorial that holds the method: customer interviews, focus groups, usability tests and diary studies. The participant information and consent tutorial prepares the documents for all of them, and the customer interviews tutorial ends with a recruiting and consent checklist of its own for interviews, which this list links rather than repeats. Lines that apply to one format only, such as rotating stimulus or a practice diary entry, are ticked as not applicable for the others.
Before you start
- The research brief: the decision, the learning goal, the method and the audience, as the research design and brief guide sets out.
- The participant profile, the screener and the quotas, with the completed screeners of everyone booked.
- The recruitment log, kept apart from notes and findings, with the reserves marked.
- The participant information and consent statements, signed off by whoever owns data protection.
- The draft discussion guideThe plan for a research interview or group: a warm-up, the episode to reconstruct, open questions about past behaviour and probes, used as a plan, not a script., task list, stimulus or diary prompts, depending on the format.
- The tools: the call or room booking, the recording and transcription set-up, test accounts and test payment details for any usability task, and the shared notes space.
- The names of the note-taker and the observers, and a time after each session for the debrief.
The checklist
The groups follow the order the study comes together: who is being asked and why, what they are told and agree to, what they will see or do, a rehearsal of the whole session, and the notes that turn sessions into findings. A line that fails in the first two groups stops the study at that point.
Brief and people
Consent and data
Materials
Rehearsal and set-up
Notes and observers
Where each check is explained
The widget keeps the lines short so they can be ticked; the reasoning lives in the guides. Each check links to the page that explains it, and the other format tutorials make the same point for their own sessions.
| Check | Explained in |
|---|---|
| Learning goal and decision written | Customer interviews, step by step |
| Participants described by behaviour, not persona | Recruiting research participants |
| Screener confirms fit without revealing the answer | Recruiting research participants |
| Quotas for each group compared | Recruiting research participants |
| Reserves from the same quota | Recruiting research participants |
| Participant information covers every use | Participant information and consent |
| A consent statement for each optional use | Participant information and consent |
| Recruitment log kept apart | Recruiting research participants |
| Test accounts and test payment details | Running a usability test |
| Discussion guide built for the format | Customer interviews, step by step |
| Usability tasks written as goals | Running a usability test |
| Stimulus order rotated between groups | Running a focus group |
| Diary prompts ask what happened | Running a diary study |
| Pilot with an outsider to the subject | Running a usability test |
| Recording captures screen, room or call | Running a usability test |
| Online participants can join, see and speak | Running a focus group |
| Practice entry and briefing call booked | Running a diary study |
| Note-taker and shared notes space | Customer interviews, step by step |
| Observer debrief after each session | Running a focus group |
| Repository entry with participant codes | Building a research repository |
Two lines lean on ideas with their own pages. Describing people by what they did echoes the jobs-to-be-done framework, which the interview tutorial uses to structure its questions: the situation and the progress someone wanted say more about whom to recruit than a profile does. The business's SegmentationDividing a market or customer list into groups that need different offers or messages. and its personasA research-based profile of a typical customer type: goals, problems and buying behaviour. are still useful for setting quotas, as the recruiting tutorial explains.
If an item fails
The brief and people group is the first hard stop. A study that cannot name the decision it informs goes back to the brief before anyone is booked. A screener that gives away the qualifying answer has let in people who guessed it, and the fix is to rescreen the booked participants with a neutral version, not to hope they fit. A participant who turns out to fail a quota is replaced from the same quota's reserves, never from whoever happens to be free, as the recruiting tutorial sets out; if no reserve fits, the session is cancelled with thanks and the incentive paid as the participant information promised.
The consent and data group is the second hard stop. Recordings and transcripts are Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier., so a use the participant information does not cover, or an optional use with no statement of its own, cannot be made. Either the documents are corrected and signed off by whoever owns data protection before the session, or that use is dropped for this study. Notes that would mix names with findings are fixed now by giving every participant a code. The names behind those codes stay in the recruitment logThe study's restricted record of who was approached, who qualified and took part, with screener answers, consent, sessions, incentives and a deletion date., where only the people running recruitment can see them. For a Usability TestA research session in which a person attempts a realistic task on a site, app or prototype while an observer notes where they struggle., a task that would ask a participant to type their own card or address waits until test details exist.
The materials group can be fixed in the time before the pilot, which is what the pilot is for. A diary prompt that asks for opinions or a task written as an instruction is rewritten rather than noted.
The rehearsal group decides whether the first real session goes ahead. A pilot that finds a long guide or a leading task is followed by a fix and, if the changes were large, another pilot. A recording set-up that misses the screen, the room or a participant's voice is fixed and checked again, because a session that is not recorded properly can only be reported from memory.
The notes group can ship with a note and a date, but not past the first session. An observer debrief booked after the first session has already lost that session's impressions, and a repository entry prepared afterwards tends to inherit names from the notes, so both are settled before the first participant arrives.
A meal-kit company prepares its first focus groups (illustrative)
Gruvane Meal Kits gets ready for groups and usability tests
Gruvane Meal Kits, an invented meal-kit delivery company, is redesigning the page where subscribers choose each week's recipes. Its researcher plans 2 focus groups, one with subscribers who skip at least one week a month and one with subscribers who never skip, followed by 5 moderated usability tests of the new menu page on phones. The learning goal, written with the head of product, is why people skip, and the decision is which of two menu layouts goes to a test.
In the brief and people group, one recruit for the skipping group answers the confirmation call by saying he has not skipped since the spring. He fails the quota, so the researcher thanks him, pays the incentive and books the first reserve from the same quota rather than a never-skipping reserve who was free that evening.
The consent group passes after the data protection owner adds a separate statement for showing clips at the quarterly staff meeting; the original participant information mentioned only analysis. Test accounts with test card details are set up for the usability tasks.
The pilot, with a colleague from the finance team, finds that the screen recording captures the laptop running the call but not the phone the participant is using for the tasks. The set-up is changed to mirror the phone's screen into the call, and a second pilot confirms both the face and the phone are recorded. The stimulus, three recipe-card designs, is rotated so that each group sees them in a different order.
The note-taking template had a column headed "Name". It becomes "Participant code", the key that links codes to names stays in the recruitment log, and the repository entry is created with codes before the first group. All 20 lines are ticked or marked not applicable two days before the first session.
Common mistakes
- Recruiting from personas. People described by who they are rather than what they did fill the room with the wrong experience.
- A screener with an obvious right answer. Candidates who want the incentive pass it, whatever they have done.
- Filling a no-show with whoever is free. The quota the decision compares quietly changes.
- Consent for the session only. Clips, quotes and re-contact then need agreement nobody asked for.
- Skipping the pilot. The first real participant finds the long guide, the leading task and the broken recording.
- Names in the notes. Identities then travel into findings, reports and every tool the notes reach.
- Observers without a debrief. The most quotable participant becomes the finding in the next meeting.
The checklists library holds the lists that sit beside this one, from the survey launch gate to the launch of a test.
