This page has moved to the Upstream Studios handbook.
Makes the GitLab product and Pajamas Design System more accessible for our users
We assess the maturity of our product categories based on market evaluations and user testing
Competitor evaluations help us understand how a competing product addresses the Jobs-To-Be-Done that our product also tries to address.
This page acts as a quick reference of mental models for sync and async collaboration.
The GitLab UX Research team's guide to documenting insights in Dovetail
We deliver end-to-end insights, from Brand to Product, that inform what we build and how we position it, shaping decisions at every stage.
Navigation refers to elements that aid users in moving around GitLab, which includes organization and wayfinding clues.
This page goes into detail around the steps needed to create a user persona with a high degree of confidence.
Guidance on how the UX Department at GitLab works.
Jobs to be Done (JTBD) is a framework for viewing products and solutions from the user's perspective, focusing on the problems they want to solve rather than specific solutions. It helps GitLab team members uncover user needs, identify strategic opportunities, validate plans, and drive innovation.
Ownership, collaboration, and expectations for the Pajamas Design System
Product Designers are strategic partners who shape user experiences from concept to delivery at GitLab.
Comprehensive guide to design processes, collaboration practices, and craft for Product Designers who work as strategic partners positioned upstream in the product development process.
The purpose of a Remote Design Sprint is to create a shared understanding and a solution to a problem following a specific process over a set timeframe. Remote Design Sprint process is based on [Google's Design Sprint methodology](https://designsprintkit.withgoogle.com/methodology/overview), and adjusted using [AJ&Smart's Remote Design Sprint 2.0](https://drive.google.com/file/d/16bwrAqHVf8qxovd87Q7LdzqwAgy7a6Rx/view).
We empower Research DRIs with the resources needed for efficient and high-quality research, enabling team members to focus on generating insights that drive exceptional user experiences and product innovation.
The GitLab Technical Writing team collaborates with developers, product managers, and the community …
The purpose of think big & think small meetings is to develop a shared understanding of goals by discussing vision, roadmap, research, design, and delivery of upcoming features.
Critical Experiences are the make-or-break experiences, which we track in GitLab to monitor the quality of our design work in action.
User journeys help GitLab teams understand and optimize the complete experience of customers as they discover, adopt, and integrate our DevSecOps platform to drive both user success and business value.
This page contains links to internal and external resources that members of the UX Department at GitLab can use to build their skills.
Performance indicators for the UX department at GitLab
The UX Forum is a recurring meeting for UX team members to share and discuss their work.
Heuristics used by the UX team to evaluate our product.
Operational guidance for UX team members including headcount planning, procurement, labels, and team processes.
A framework defining what to measure and how to measure to assess the UX quality of concepts, designs and in-app experiences.
Resources and tools for UX team members across Product Design, UX Research, Technical Writing, and Design System, part of Upstream Studios.
The UX Scorecard is a process similar to a heuristic evaluation that helps identify usability issues and score a given experience.