Participant Recruiting

One study is enough to learn that seating people is harder than picking a method. The method takes a day to choose; two weeks in, five participants still haven't come together. So early on teams reach for whoever is within arm's length — the colleague at the next desk, a friend, someone from a previous job. It feels reasonable at the time, because the plan was to watch somebody use the product and these are people who will say yes today.

Pagedeck's first usability test went exactly that way. Five people from a neighboring team came into a room and none of them got stuck. All five already used the product internally and knew where the buttons were. The result said there was no problem, and support requests kept arriving afterward from people who had stalled on that same screen.

So Mia wrote the criteria down as a sentence: a manager of a team of five or more who has never seen this product. From the moment that sentence existed, finding people became a separate piece of work. Participant recruiting is the name for that work, and in practice it takes up roughly half the calendar of a study.

It starts with defining who qualifies and ends with those people actually showing up. Six steps.

1. Write the criteria as a sentence. "Users" lets you pick anyone, so write something countable instead — a manager of a team of five or more who created ten or more documents in the last month. Everything later filters against this sentence.
2. Decide how many you need. Qualitative research, which works out why people behave a certain way through what they say and do, starts repeating itself at five to eight people. A study that has to state a percentage needs hundreds. The number is a consequence of the question, not a budget decision, and inflating it for a qualitative study mostly buys more of the same quotes.
3. Add the people who won't turn up. Roughly one in every two or three confirmed participants doesn't appear. To talk to six, confirm eight or nine. Skip that margin and the study ends with two empty interview slots on its last day.
4. Choose where to look. Pulling from your own user list by criteria is the cheapest route, and if a ResearchOps layer holds a record of past participants, that record gets checked first. When nobody in your own data matches, you pay an agency that keeps a panel of participants on hand.
5. Build the screening questions. The trick is not to ask the criteria directly. Ask whether document management frustrates them and only people who say yes remain; ask how many documents they created last week and you get a fact. Two or three factual questions are usually enough, and each one should map to a clause of the criteria sentence.
6. Book the session and cover incentives and recording. Say how much is paid, when, and by what method, say what gets recorded and how far it may be used, and take consent in advance. A reminder the day before and another an hour before cuts no-shows noticeably.

Who you invite is decided by what you want to know. Three groups, each able to answer something the others can't. Current users tell you where the product is awkward, people who left tell you why they stopped, and people who haven't started tell you what would have to exist before they would. Ask about churn while recruiting only happy active users and two weeks later you've confirmed what you already knew.

Decide who not to invite as well. Friends and colleagues either know the product already or soften their answers in front of someone they know, which bends the result. Avoid the regulars too. By the fifth session the same person is no longer a user but somebody fluent in your study, which is why a participant record keeps a contact history. The record is also what makes a 90-day gap enforceable, since nobody remembers who was called in March.

Timing runs backward from the date the team has to decide something. Allow two weeks for recruiting, put defining the criteria in front of it and running plus analysis behind it. The method changes the shape of the booking. A customer interview, which is roughly an hour with one person, and a usability test, where someone is handed a real task, both need individual time slots, so lining up calendars eats a few days. A diary study, where people log their own activity for two weeks, loses some participants partway through, so it gets a wider margin than the others.

"Give recruiting two weeks. The criteria are narrow, so eight people will take that long."

Flagging in advance that half the schedule goes into finding people.

"Drop the screener question about document management being frustrating. Only people who agree will show up."

The screening questions are skewing who ends up in the room.

"I confirmed nine to talk to six. Someone always drops."

The count was padded for the no-show rate.

Pagedeck changed its approach from the second usability test onward. Mia pulled managers of teams of five or more who had created ten or more documents in the last month, then removed internal accounts and anyone contacted in the previous 90 days. Invitations went to what was left, nine confirmed, and seven arrived.

Noa ran those seven and got a different picture from the first test. Five of them stopped on the same screen, and that screen was the one support requests had been pointing at all along.

The most common belief is that volume fixes it. A larger number looks like a sturdier result, so it reads that way. But eight people who don't match the criteria tell you nothing. The first test with five people from the next team is that case: it failed not because the group was small but because it was the wrong group. Three people who match beat ten who were never filtered, and the narrow group is usually cheaper to run as well. Miss that and the only thing left is a record that a study happened, while the next decision still gets made on instinct.

The other belief is that raising the incentive solves recruiting. It's the first lever anyone reaches for when nobody signs up. Push the amount far above compensation for the time, though, and you attract people willing to misreport their situation — someone who isn't a manager answering that they are. Keep the amount fair for the hour, and instead rewrite the screener to ask about facts and widen where you look. Invert that order and the slots fill easily while the findings become unusable.