How to write an effective screener (2024)

How to write an effective UX research screener at GitLab

Screener goals

The questions in a screener have two conflicting goals:

• They must elicit specific information about users.
• They should also avoid revealing specific information about the study.

Step 1: Define the traits of the participant(s) you are looking for

When thinking about the users of your product, you will likely come up with a number of categories of ’typical’ users. The more specific you can make your descriptions of your users, the better you will be at identifying people who match your user profile. It is important to note that job titles alone don’t fully reflect a person’s tasks, duties, or behaviors. The example below shows how you can turn user traits into screener questions.

Step 2: Structure your screener questions

When thinking about your screener questions, try to organize them like a funnel to narrow down participants, starting with broad questions and moving to more specific questions.

Step 3: Build the screener

Here are some best practices when making a screener from scratch:

• Create a screener draft in Google Docs to easily collaborate with others before implementing in a survey platform.
• When writing up a screener draft, use brackets for internal notes, so the researcher and other stakeholders can indicate whether an answer should terminate/reject a respondent. Brackets can also be used to indicate when a question should be skipped.
• If you need to use advanced logic to display questions and/or route respondents down a certain path based on their previous answers, Qualtrics is a great tool.

Final drafts of screeners at GitLab are created in Qualtrics. If you don’t have access to Qualtrics, request it. If you are using a different recruiting method or an unmoderated study platform (such as UserTesting.com), you will create the screener in those platforms.

Screener tips

When crafting questions, keep the following in mind:

• Ask open-ended questions about behavior, similar to the questions you ask in an interview. Yes/No questions lead participants to assume what you’re looking for.

• Provide similar options to choose from to mitigate guessing the purpose of the study.
  • To screen participants for their natural behavior, provide multiple options to mask what you’re looking for.

• Use plausible distractor answers to conceal the subject of the study.
• Avoid stand-out screener options, which indicate behavior that you’re looking for.
  • Participants can look for answers that stand out from the other answer options.
  • Using multi-select can allow for multi-guess without consequence.
• Multiple correct answers are OK and can provide information about your participants you’d normally get from an interview.

• If you are looking for a specific behavior, you can ask for verification of that behavior by including a statement in the screener such as “As part of the session, you will be asked to share your screen and walk through a previous hotel reservation.” Give them the option to agree or disagree to share their information.
  • This can guarantee your participant has completed the behavior you are looking for.
  • This is helpful if you need to verify actions or usage to bucket participants into segments.

Example GitLab Screener

• Screener template