Define and recruit users for incident management CMS
## This issue is for completing the work in Step 1 of the [CMS workflow](https://about.gitlab.com/handbook/engineering/ux/category-maturity-scorecards/), to define and recruit users
**Guidelines for Step 1**
To balance expediency with getting a variety of perspectives, we conduct the Category Maturity Scorecard research with five participants from one set of user criteria. If you have multiple user types for your JTBD, it is ideal to recruit 5 from each user type. To keep the study manageable, focus on no more than 2 user types per study. If more than 2 user types are required to accurately measure your JTBD, conduct a separate follow-up study for the remaining user types.
Example: A JTBD can be completed by a DevOps Engineer and a Release Manager. In this case, you’d recruit a total of 10 participants: 5 DevOps Engineers and 5 Release Managers.
The recruiting criteria can be based on an existing persona, but needs to be specific enough that it can be turned into a screener survey. A screener survey should then be created in Qualtrics that your prospective participants will fill out to help you determine if they're eligible to participate.
The template survey includes a question asking people if they consent to having their session recorded. Due to the analysis required for Category Maturity Scorecards, participants must answer yes to this question in order to participate. Once your screener survey is complete, open a Recruiting request issue in the UX Research project, and assign it to the relevant Research Coordinator. The Coordinator will review your screener, reach out to you if they have any issues, and begin recruiting users based on the timeline you give them.
[WIP Screener google doc](https://docs.google.com/document/d/1TjTkg9ZAjEp9w7zXVAZmpgQ6-dvIIcipNlsABQ9KM7Q/edit?usp=sharing)
Quatrics [screener preview](https://gitlab.fra1.qualtrics.com/jfe/preview/SV_bPbzxLuhQjqX2xE?Q_CHL=preview&Q_SurveyVersionID=current).
issue