Update `#ux` Slack channel references to `#upstream-studios`

- Understand [how to become a maintainer](/handbook/product/ux/pajamas-design-system/design-review/#how-to-become-a-maintainer).

- All designers are maintainers of [`gitlab-design`](https://gitlab.com/gitlab-org/gitlab-design) project. If you are interested in becoming a Maintainer of UI (`.scss`) for `gitlab`, and `gitlab-ui` projects, please follow the [Engineering Review Workflow](/handbook/engineering/workflow/code-review).

- It is up to you to ensure that you are getting enough MRs to review, and of varied types. You could also seek out more reviews from your team, for example by asking for reviews on the `#ux` and `#pajamas-design-system` Slack channels. If you are not receiving enough MRs to advance in your training, be proactive and work on your own improvements to Pajamas. This will demonstrate overall understanding of the product, as well as quality contributions, and help propel your progress. Maintainers are available to help guide you.

- It is up to you to ensure that you are getting enough MRs to review, and of varied types. You could also seek out more reviews from your team, for example by asking for reviews on the `#upstream-studios` and `#g_pajamas-design-system` Slack channels. If you are not receiving enough MRs to advance in your training, be proactive and work on your own improvements to Pajamas. This will demonstrate overall understanding of the product, as well as quality contributions, and help propel your progress. Maintainers are available to help guide you.

- Your reviews should aim to cover maintainer responsibilities as well as reviewer responsibilities. Design Maintainers should be focused on MRs that have an impact on usability, iterate on existing user experience, and/or include usage of design guidelines, standards, and patterns. Your approval means you think it is ready to merge.

- As maintainer, you must keep [relying on others](/handbook/values/#its-impossible-to-know-everything) for the expertise they have that you don't. In the MR description, highlight the efforts that showcase your results at a maintainer-level, what skills you want to continue working on, and add a link to this issue. ([Example](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2395)).

- PMs who need to create designs can request access to Figma by creating an [Access Request issue](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/issues/new). **Note:** We cannot grant an Editor seat by requesting an upgrade within Figma. An access request issue is required.

- Review and follow the [Pajamas guidelines](https://design.gitlab.com/).

- If you have a small design question, or the Pajamas guidance is not clear, reach out via the `#ux` or `#ux_coworking` Slack channel.

- If you have a small design question, or the Pajamas guidance is not clear, reach out via the `#g_pajamas-design-system` or `#ux_coworking` Slack channel.

- If you have a Community Contribution MR that needs a design review, follow the process for [MR Reviews for Groups without a Designer](/handbook/product/ux/product-designer/mr-reviews/#stage-group-mrs).

### Working with Product Management external to the company

- Link to the issue for additional details.

- A note around the expected timeline for when you'll share the results. A rough estimate is acceptable. For example, '*Results will be shared in 3-4 weeks from now'*.

- Optional: if you would like to use this post as a way to invite attendees to your research sessions, you can certainly do that. An example on how to do that: '*If you are interested in attending sessions live, please reply to this thread. Otherwise, I'll post recordings to this Dovetail project [insert link], where you can watch on your own time.'*

- The posting is shared out via Slack to *at least* the three following channels: #ux, #ux_research, and #product.  It's advised to also share the posting in any relevant stage-group channels, too.

- The posting is shared out via Slack to *at least* the three following channels: #upstream-studios, #experience_research, and #product.  It's advised to also share the posting in any relevant stage-group channels, too.

#### Socialising research findings

- List 3-4 bullets with the key insights. These should not include any detail - just very short sentences on the high-level findings.

- Links to the: Research report, Video readout, Data sheet, Research issue, Dovetail project

- A 'Next steps' sections that includes bullets on what will be happening as a result of the research.  These should be links to issues that are actionable insights.

- The posting is shared out via Slack to *at least* the four following channels: #ux, #ux_research, #ux_research_reports and #product.  It's advised to also share the posting in any relevant stage-group channels, too.

- The posting is shared out via Slack to *at least* the four following channels: #upstream-studios, #experience_research #experience_research_reports and #product.  It's advised to also share the posting in any relevant stage-group channels, too.

### How we maintain coverage

**Q: How can I find open issues that relate to SUS?**

A: Issues that relate to SUS will have one of the labels indicated in the [How we use labels](/handbook/product/ux/operations/#ux-labels) section of the UX Department Handbook. If you see an issue that relates to usability problems that fall in line with recent SUS findings, feel free to add one of the labels to it. When in doubt, reach out to your manager or ask in the `#ux` Slack channel.

A: Issues that relate to SUS will have one of the labels indicated in the [How we use labels](/handbook/product/ux/operations/#ux-labels) section of the UX Department Handbook. If you see an issue that relates to usability problems that fall in line with recent SUS findings, feel free to add one of the labels to it. When in doubt, reach out to your manager or ask in the `#upstream-studios` Slack channel.

- The UX Research Operations Coordinator will @ mention you on any ongoing recruitment issues that you need to pick up. They will provide you with a clear description of the status of the issue and what needs to be completed.

- The UX Research Operations Coordinator will assign you to any of these ongoing issues so you can easily track them.

- The UX Research Operations Coordinator will also share the Open Recruitment Projects sheet with you and tag you on projects that require assistance.

- Introduce yourself, in the `#product` and `#ux` Slack channels, as the recruitment point of contact for the next X days and/or weeks.

- Introduce yourself, in the `#product` and `#upstream-studios` Slack channels, as the recruitment point of contact for the next X days and/or weeks.

  - If people attempt to raise recruiting requests in Slack, remind them to [create a recruiting request issue](/handbook/product/ux/experience-research/recruiting-participants/#opening-a-recruitment-request) and assign it to you for tracking and visibility purposes.

  - Remind them an issue has been handed off to you once you confirm the handoff in a comment.

- Be sure to join the `#uxr_reops` Slack channel for easier coordination if there is more than one person covering for the UX Research Operations Coordinator.

- Be sure to join the `#research_operations` Slack channel for easier coordination if there is more than one person covering for the UX Research Operations Coordinator.

- If the UX Research Operations Coordinator is going to be unavailable for more than 7 consecutive business days they will open an MR on the Research Recruiting & Incentive Request Issue Template to make sure whoever is covering for them is auto-assigned to newly opened issues.

### Step 2 - Dealing with new recruiting requests

  - We can leverage their panel to recruit technical users

- **Using Team members to socialize requests:**

  - How to use it:

    - Post in Slack channels like #ux, #product, and #whats_happening_at_gitlab . Include a concise call to action, due date, and share the link that you want people to post.

    - Post in Slack channels like #upstream-studios, #product, and #whats_happening_at_gitlab . Include a concise call to action, due date, and share the link that you want people to post.

- **[Direct outreach](https://www.youtube.com/watch?v=rc2IX1e2sQ8&feature=youtu.be) on LinkedIn:**

  - How to use it:

    - You can search for the criteria you are looking for and use inMail credits to invite them.