Who can afford to participate?
We say participants give us their time, which is a polite way of saying we asked them to work and did not always plan to pay for it.
I used the phrase giving us their time for most of my career. It is generous, and it does a great deal of hiding.
They are working. We scheduled it, we set the agenda, we recorded it, and we took the output back to a company that will make money from it. Every part of that is a job except the part where somebody gets paid.
Who says yes when nobody is paid?
People with flexible time, which is not a random sample of anybody.
Retired people. People between jobs. The self-employed. Advocates who are already professionally adjacent to our field and have made a decision to spend their energy this way. These are thoughtful participants and I have learned an enormous amount from them.
They are also, systematically, not the person our products are hardest on. Not the hourly worker on a split shift. Not the parent whose evenings are already allocated. Not the person whose energy on any given day is finite and already spoken for, which describes a great many disabled people and is precisely the condition our interfaces handle worst.
So an unpaid study quietly recruits for surplus capacity, and then we write "we tested with disabled users" in the report as though the category were the sample.
What does that do to what we learn?
It produces a friendly sample and a flattering result.
There is a second effect that gets even less attention. The same few people say yes to everybody. Over a few years they become semi-expert: fluent in our vocabulary, patient with our prototypes, skilled at articulating a problem in terms a product team can act on.
That fluency is genuinely useful and it is not the same as being representative. A participant who can tell you the heading level is wrong here has already done half of our job for us. The person we most need to hear from is the one who cannot name what went wrong and leaves, and that person is very rarely in a study, because nothing in how we recruit reaches them.
We both believe our field does not intend to study only the reachable. It is what happens when recruitment is a line nobody owns and payment is a line that gets cut first.
What are we actually asking someone to spend?
More than the hour in the calendar invitation, and the extra is unevenly distributed.
Getting there, or getting a room and a connection sorted. Setting up assistive technology on a machine that is not theirs, or arguing with ours. I have sat in sessions that ran long because our equipment would not cooperate with a participant's, and every minute of that overrun was charged to them. The energy the session takes and the energy it takes afterwards, which for a lot of people is the larger number. And the part we almost never count: explaining your own disability to a stranger, again, as the price of admission to a conversation about a product.
Then there is a complication that many teams have never encountered. In the United States, payment can interact with disability benefits in ways that matter a great deal to the person receiving them. "We will pay you" is not automatically a kindness. It can be a problem someone now has to manage, and they may not want to explain why on a recruitment call.
I did not know any of that for most of my career, and nothing in my professional training mentioned it. It is not an argument against paying people. It is an argument for asking, early and privately, and for having more than one answer ready.
What does decent practice look like?
At the Rhonda Weiss Center we ran more than thirty studies with disabled participants around a stakeholder group of about eighty people, on a federal grant that made the logistics fundable. Most of what I took from it costs far less than that.
- Pay at the same rate you pay any other participant. Not a smaller amount because the session was remote, and not a gift because the person seemed glad to help.
- Offer a choice of how. Cash, a card, a donation to somewhere they choose, or declining the payment without losing the slot. Ask in writing, before scheduling, and do not ask them to justify the answer.
- Ask about access needs before you schedule, not after. A session booked first and adapted second has already told the participant where they came in the ordering.
- Budget the logistics as their own line. Recruitment, scheduling, setup time, coordination. This is the work that decides whether study two happens, and it is invisible in every research plan I have ever seen.
- Recruit past the people who always say yes. Disability organizations, employers, community groups, and the unglamorous work of building a list that is not the one you already have.
- Pay stakeholders too, not only usability participants. Advisory time is work. It is often more work, it is spread over months, and it is the category most likely to be treated as goodwill.
- Say in the report who you reached. Not "disabled users." How many, using what, recruited how. It makes the limits of the study legible to the next person instead of making the sample sound like the population.
The part that is really about power
Our defaults encode an assumption about who is in the room, and unpaid participation encodes a second one underneath it: that the people we are designing for have time to spare and a reason to spend it on us.
For the participants who most need our products to be better, neither is true. They are working, or tired, or both, and the only reliable way to reach them is to treat their contribution the way we treat everyone else's contribution to a commercial product, which is to pay for it.
Open the budget for your next round of research and find the line for participant payment. If it does not exist, that is the finding. And if it exists but has never been increased, ask who has been saying yes at that rate, and who has been quietly priced out of telling you what is wrong.