<!--In the title, include the sections/stage groups you cover and the quarter/year for this issue.-->
<!--Please answer fill out the information below to the best of your ability. For details on this entire research prioritization process, please visit: https://about.gitlab.com/handbook/engineering/ux/ux-research-training/research-prioritization/-->
#### What is this issue about? (Background and context)
This issue will help the UX researcher identify, coordinate, report, and synthesize findings across research studies by identifying a common list of research goals to rally around.
I need a list of prioritized goals for research to help research support the sections and stage groups I cover. I'll use this issue to determine how to focus time, synthesize, and report findings at a higher level, and ultimately how to craft research projects that will address as many goals as possible.
#### What research is happening now?
<!-- This table should include current and future research projects. Make sure to include any past projects that were not completed in past prioritization issues. This table will be updated with new projects after stakeholders have been able to add projects to the prioritization calculator sheet (see Resources & Documentation section below).-->
| Project Name | Research Issue | Support Level | Section/Stage Group | Status | Status Details | Estimated Completion |
### What level of support may we expect from our UXR?
We are currently **piloting** the use of a support level label. You can provide feedback on this approach, and how well this issue is or isn't working for you in the comments below.
| Support Level | Description | Scope |
| ------ | ------ | ------ |
| **Gold** :first_place: | **End-to-End Support:** UXR is the DRI, driving project management aspects of execution and will keep the project moving forward, but has support from PM/Design for milestone tasks - as delegated within each issue before a project is initiated. Task delegation is fixed with each team member committing to deliverables framed in the study plan during kick-off. Issues are used to formulate a plan, and then the UXR drives and executes. Keeping the team appraised but making key decisions about how to scope the project and next steps. | 1-2 executed per quarter, 1-2 in planning, 1-2 in impact stage |
| **Silver** :second_place: | **Task-Specific Support:** PM/Design is the DRI, driving project management aspects of execution and completing mosts tasks, but has support from UXR. UXR provides dedicated support for specific tasks that take less then a few days to execute, but may need to deprioritize if needed to keep higher tier support projects in play. If that happens, team members need to pick up with that work. | 1-4 active projects |
| **Bronze** :third_place: | **Consultant:** UXR advises on specific aspects of study planning and execution on an ad-hoc basis and during downtime between higher tier support. Here the UXR needs teams to tag them into issues, provide context and a due date for when feedback is needed by| 1-2 executed per quarter, 1-2 in planning, 1-2 in impact stage |
#### What will you do with this issue and our goals?
- I'll use these overarching goals to compile a set of research projects/questions into a list that we can prioritize (e.g., what research gets done sooner vs. later).
- I'll use this prioritized list to help guide decisions about how to allocate research resources.
- I'll provide updates in terms of what we've learned in terms of our research goals. I'll update this issue with links to research issues as they are built out and provide status of different projects, so teams are informed on progress.
#### What can I do to contribute to this issue?
1. In the issue comments below, post a comment of what you need / want to know about users within your area/stage group. Some prompts to get you thinking:
- What keeps you up at night, when you're thinking about our product?
- What do you need to know about users to help you increase MAUs?
- What do you need to know about user workflows for your stage group/area?
- What info do you need to know in order to make informed decisions about the direction of your stage group/area?
**Note:** It's hard to do, but try to articulate your thoughts at the [goal level](https://about.gitlab.com/handbook/engineering/ux/ux-research-training/defining-goals-objectives-and-hypotheses/#step-4---state-the-goals-for-the-research)
2. Create a UX Research issue along with your request, so it can be linked and prioritized within this issue. If you are unfamilar with how to create a UX Research issue, please review the following [slides](https://docs.google.com/presentation/d/1ZWI1g3FC_9F6IRVdyZHYKeRAlQyFVXLoLSaRZg1Ro_g/edit#slide=id.g10ad1ea730e_0_22).
3. Comment on other people's comments or upvote them. This will help me understand the importance or priority of the research being requested.
#### Important information about research requests
Please be aware that adding comments/suggestions for research does not guarantee that I will be able to support your request. I will do my best. However, there will be varying levels of support.
#### Prioritization Documentation
<!-- When using the link to the Research Prioritization Calculator, please create a copy of this Google Sheet: https://docs.google.com/spreadsheets/d/1sE-Eia73HnvavfwNMHTJdKrvIkNxP9N3xtzpd4JUalo/edit#gid=1093756030-->
-[Research Prioritization Calculator](Add your link here)
<!-- In the comments, include a link to this issue and share with stakeholders in your area (Product Designers, Product Design Managers and Product Managers) for the relevant group. If you're unsure of who that is, you can check here:
