@@ -436,7 +436,7 @@ changes quickly in the future so we try to avoid complex code, complex data stru
- It is orthogonal to other features (prevents overlap with current and future features).
- The requirements are clear.
- It can be achieved within the scheduled milestone. Larger issues should be split up, so that individual steps can be achieved within a single milestone.
- Refer to [research participant gratuities](/handbook/product/ux/research-operations/participation-gratuities/) section to understand [if your study qualifies for incentive distribution](/handbook/product/ux/research-operations/participation-gratuities/).
- Refer to [research participant gratuities](/handbook/upstream-studios/research-operations/participation-gratuities/) section to understand [if your study qualifies for incentive distribution](/handbook/upstream-studios/research-operations/participation-gratuities/).
We schedule a prioritized issue by assigning it a milestone; for more on this see
@@ -38,4 +38,4 @@ The following is a non-exhaustive list of approaches to finding customers open t
- All continuous customer interview data should live in Dovetail. Any additional information (summaries, templates, etc.) can live in confidential issues as long as the data are connected back to the Dovetail project.
- Remove customers' [Personally Identifiable Information (PII)](/handbook/support/workflows/pii_removal_requests/) from Dovetail and GitLab issues, so that team members do not identify specific individuals as part of the research process.
- For example: Avoid including the first/last name of the user and company where the user works. Instead, you can reference them by their job title, persona type, or participant number (P6).
- With customer research, you may have the option to [compensate participants](/handbook/product/ux/research-operations/participation-gratuities/#incentive-qualification) for their time. Providing a small token of thanks is a best practice to show users how we value their time.
- With customer research, you may have the option to [compensate participants](/handbook/upstream-studios/research-operations/participation-gratuities/#incentive-qualification) for their time. Providing a small token of thanks is a best practice to show users how we value their time.
@@ -11,7 +11,7 @@ Our researchers work at two levels. Some of us are **embedded in Upstream Studio
## How we are structured
The ExR team is led by [Karen Li](https://gitlab.com/karenyli). It is one of 8 teams in GitLab [Upstream Studios](/handbook/upstream-studios/). The team consists of 3 disciplines: UX Research, [Service Design](/handbook/product/ux/experience-research/service-design/), and [Research Operations (ReOps)](/handbook/product/ux/research-operations/).
The ExR team is led by [Karen Li](https://gitlab.com/karenyli). It is one of 8 teams in GitLab [Upstream Studios](/handbook/upstream-studios/). The team consists of 3 disciplines: UX Research, [Service Design](/handbook/product/ux/experience-research/service-design/), and [Research Operations (ReOps)](/handbook/upstream-studios/research-operations/).
We have one researcher embedded in each of the four product studios, **working at the level of the trio**, VP of Product Management, VP of Engineering, and Product Design Manager, shaping decisions as they are being made. Two more researchers are embedded in the centralised teams, **working directly with the team leads,** supporting Design Strategy and Brand Experience. Service Design covers all studios and centralised teams, directing attention to where the seams may show the most. Research Operations enables research efficiency and quality at scale.
@@ -99,7 +99,7 @@ We then apply rigorous data analysis and synthesis to transform this data into v
#### How we help other GitLab team members do research
Note that UX Researchers are **one of the many** GitLab Team Members who conduct user research. Other roles, such as Product Managers and Product Designers, frequently conduct research with guidance from the Experience Research team. All Research DRIs are supported by our [Research Operations team](/handbook/product/ux/research-operations/) to conduct efficient and high-quality research.
Note that UX Researchers are **one of the many** GitLab Team Members who conduct user research. Other roles, such as Product Managers and Product Designers, frequently conduct research with guidance from the Experience Research team. All Research DRIs are supported by our [Research Operations team](/handbook/upstream-studios/research-operations/) to conduct efficient and high-quality research.
If you are planning to lead a research project, you can get started [here](/handbook/product/ux/experience-research/resources-for-research-dris).
@@ -232,21 +232,21 @@ Below is a full list of our Experience Research team handbook content:
-[How the UX Research team operates at GitLab](/handbook/product/ux/experience-research/how-uxr-team-operates/)
-[The IP Assignment and when to show it](/handbook/product/ux/research-operations/ip-assignment/)
-[How to fill in for a Research Operations Specliaist](/handbook/product/ux/research-operations/research-specialist-fill-in/)
-[The IP Assignment and when to show it](/handbook/upstream-studios/research-operations/ip-assignment/)
-[How to fill in for a Research Operations Specialist](/handbook/upstream-studios/research-operations/research-specialist-fill-in/)
-[UX Research growth and development](/handbook/product/ux/experience-research/ux-research-growth-and-development/)
-[Non-Disclosure Agreements for UX Research](/handbook/product/ux/research-operations/ndas)
-[Non-Disclosure Agreements for UX Research](/handbook/upstream-studios/research-operations/ndas)
-[How to publish a blog post to encourage community contributions on Actionable Insights](/handbook/product/ux/experience-research/community-contributions-for-actionable-insights/)
-[How to Conduct UX Research Workshops](/handbook/product/ux/experience-research/how-to-conduct-ux-research-workshops)
-[How to use AI in UX research](/handbook/upstream-studios/how-we-work/ai-usage/)
#### Resources for UX Research Operations Coordinators
-[UXR Operations Coordination at GitLab](/handbook/product/ux/research-operations/)
@@ -5,7 +5,7 @@ description: "Our team structure, working model, resource allocation, and more"
## Team structure
The UX research team is comprised of [UX Researchers](/handbook/product/ux/experience-research/), Service Designers and [UX Research Operations Coordinators](/handbook/product/ux/research-operations/)).
The UX research team is comprised of [UX Researchers](/handbook/product/ux/experience-research/), Service Designers and [UX Research Operations Coordinators](/handbook/upstream-studios/research-operations/).
- UX Researchers work within their assigned stage groups, where they conduct UX research on their own and consult on research efforts being done by their teams.
- Service Designers work across stages and groups, where they conduct user research and design to improve the end to end user journeys across GitLab.
@@ -52,7 +52,7 @@ A sample output could look something like the following chart, which demonstrate
1.[Open a recruitment issue](/handbook/product/ux/experience-research/recruiting-participants/#open-a-recruitment-request-issue) that outlines the number of touchpoints and time commitment for each one.
1. Determine the gratuities for each touchpoint.
1. During initial 1:1 interviews, work with participants directly to schedule the upcoming touchpoints.
1. Work with the [UX Research Operations Coordinator](/handbook/product/ux/research-operations/) to make sure gratuities are delivered in an efficient and timely fashion.
1. Work with the [UX Research Operations Coordinator](/handbook/upstream-studios/research-operations/) to make sure gratuities are delivered in an efficient and timely fashion.
