How the UX Research team operates at GitLab

Maintained by:

How we decide what to research

UX Researchers collaborate with Product Managers to determine the scope of research studies. Where possible, UX Researchers should try to attend planning meetings for their designated groups. UX Researchers should proactively offer ways in which they can assist in the delivery of research. They should also suggest and discuss their own ideas for research studies with Product Managers.

How we spend our time

UX Researchers have the following guidance on how they should be spending their time:

<10% Solution Validation - This translates to less than 10% of a researcher's time being allocated to assisting Product Designers and Product Design Managers with Solution Validation research.
~60% Problem Validation - Researchers spend more than half of their time working with Product Managers conducting Problem Validation research, with the long-term goal of investing their time towards training and mentoring.
~30% Foundational/Strategic Research - Ideally, 1 big project per researcher, per quarter. These are projects that feed into the researcher's stage/team, cross-stages, or section and may be derived by the researcher. Examples:
- Go deeper into a SUS theme that is specific to the stage(s) they support. Doing this will help the team focus on issues that contribute to detractors.
- Look deeper into performance (ex: Why is our performance perceived the way it is?)
- Pain points - Are those known for each stage and/or group? Are they being dealt with? Are there real-life customer stories to help get those pain points addressed?
- A project could even be derived from a Problem Validation topic or follow-up area.

Three noteworthy benefits to conducting Foundational/Strategic research:

Researchers gain subject matter knowledge in that topic
Researchers have an opportunity to impact Product and influence strategy
Career growth opportunities

Metrics we measure

As user researchers, we leverage different types of metrics to aid in measuring the success of our product. We currently use metrics to evaluate navigation changes.

Milestones

Like other departments at GitLab, UX Researchers follow the Product Development Timeline and use milestones to schedule their work. Milestones change monthly (find out the dates for upcoming milestones).

How to request research

Any GitLab Team Member can open a research request. If you are not a Product Manager, Product Designer, or UX Researcher, please open a Research request issue using the available template in the UX Research project. Once completed, please assign the issue to the relevant Product Manager, Product Designer, and UX Researcher. The UX researcher assigned to the issue will review it and notify you when/if they plan to proceed with the work.

How we work

Assign yourself to any research issues you are leading. It is optional to assign yourself to any research issues you are supporting.
Proactively contact your Product Director and request their input to prioritize the existing UX research issues in your stage. Inform your Product Director of your capacity for research during the upcoming two or three milestones. This may be more effective as a Zoom call at first, and then you can transition to an async conversation in an issue.

UX Research peer reviews

UX Researchers will frequently drive research projects themselves in close collaboration with Product and/or Design. When this occurs, UX Researchers will take part in a peer review process on the test plan and the final output of the research. There are several benefits to a peer review process:

Visibility - UX Researchers will be more informed about the research being conducted outside of their direct area of coverage.
Learning - UX Researchers can learn from each other by reviewing the approaches being taken and the justification behind those approaches.
Quality - Research deliverables will be more standardized and of higher quality as a result of a peer review.
Onboarding - New UX Research hires will benefit by seeing standardized examples and learning about the quality bar to replicate.
Mentoring - UX Researchers will have more opportunities to mentor each other in their craft.

The UX Research peer review process is designed to be asynchonous and inclusive to all UX Researchers. The process is as follows:

A UX Researcher has either a test plan or a final report that needs to be peer reviewed. They ensure it's shareable and editable.
Within the #ux_research_team_lounge Slack channel, they post a link to it along with a request to review. They include a date that they need feedback by.
- Example: "Hi - can I please request a review of this test plan (link)? Feedback is needed by Thursday. Thank you!"
- Best practice: Reviewers should aim to provide reviewers at least 24 hours to review.
Another UX Researcher claims it by replying to the thread: "Claimed!"
The reviewer provides feedback directly in the document, issue, etc.
When the review is complete, the reviewer responds to the thread and mentions the UX Researcher.
- Example: "@ name - your testplan has been reviewed. Let me know if you have any questions!"
The UX Researcher reviews the feedback, follows up on any questions, and makes any adjustments necessary. When complete, they put a green check mark emoji reaction on their original post, indicating that the peer review request has been completed and is closed.

How problem validation research works

How solution validation research works

Solution validation research at GitLab is led by Product Designers, with support from Product Design Managers. Occasionally, Product Design Managers may need to escalate queries about solution validation research to UX Researchers for advice and feedback.

If capacity allows, UX Researchers can help with solution validation research efforts. Product Managers and Product Designers follow the steps in the Validation phase 4 when planning and executing solution validation research.