This page includes information about UX Resources to help you do your job. It is not intended to be an all-inclusive list or to limit the methodologies or approaches you might take in your daily work. If you believe that something useful is missing, please submit an MR!
The following resources are intended primarily to help Product Designers.
The GitLab design project is primarily used by the Product Design team to document workflows and processes. For details, please visit the project README.
The GitLab Design System, Pajamas, was developed to increase iteration speed and bring consistency to the UI through reusable and robust components. This system helps keep the application DRY and allows designers to focus their efforts on solving user needs, rather than recreating elements and reinventing solutions. It also empowers Product, Engineering, and the Community to use these defined patterns when proposing solutions.
Our SVG repository manages all GitLab SVG assets by creating an SVG sprite out of icons and optimizing SVG-based illustrations.
Our Dribbble team account is a collection of design work that we've produced at GitLab:
We use the Jobs To Be Done framework to encourage thinking from the customer's point of view and focusing on the value customers are looking for. We also use JTBD to help build scorecards that assess our Category Maturity.
Synchronous design feedback is an effective tool for capturing design feedback from stakeholders and team members.
There are many ways to gather feedback in a sync meeting. One example is to use a Round Robin turn-based structure that gives everyone on the call an opportunity to share their thoughts quickly and efficiently.
This conversation should be timeboxed to 15 minutes, so remember to be concise and have fun with it! If you ever need inspiration for feedback, consider taking a few different hats for a spin!
The setup is very simple. Before the sync session, prepare the agenda by pasting a link to these notes. As the meeting starts, look at the attending members' names and form a randomly ordered list. This will be the order for participants to go in. Make sure to put this ordering into the agenda.
The designer will kick off the process by quickly reviewing the rules and starting the 15-minute timer. After the timer has started, the activity goes as follows:
As a participant, you can do a few different things on your turn. Try to be quick, as each turn should only last around 1 minute. During your turn, you can do a few things (in order of priority):
Remember, the goal is to capture a quantity of specific feedback. While it may be tempting to start discussions around the design choices and feedback, this activity doesn't make for a good forum. The designer will follow up with discussions asynchronously afterward in the issue(s) to start discussions and conversations around the feedback.
The UX team is encouraged to make UI improvements directly in the product when they find something that is small and easy to change. If you've never made a change to the product before, start by reading The Designer's Guide to contributing UI changes in GitLab
Mural We use Mural for collecting design feedback, mapping workflows, brainstorming, affinity mapping, and anything else where we need a visual, whiteboard-like workspace.
Everyone in the UX department and all Product Managers can get a Mural account with the ability to create new Murals. If you want to share your Mural to get feedback from members of your team who do not have a Mural account, you can send an anonymous link via the Share dialog.
Figma We use Figma for designing and prototyping. Our Pajamas UI kit contains design assets, components, and styles for GitLab's design system, Pajamas. Every product designer should receive access to Figma during onboarding. If you don't have the access you need, reach out to your manager. If you are not a product designer but want View access (including the ability to leave commnets), create a free Figma account and ask your stage group designer for a link to the relevant files.
The following resources may be helpful to UX Researchers, Product Designers, and Product Managers, since all of these roles conduct user research. For more information, see the UX Research section of the handbook.
The UX Research project contains all research undertaken by GitLab's UX researchers and is only used for the organization and tracking of UX research issues.
Once each quarter, we run a System Usability Scale (SUS) survey to measure user perception of the GitLab product. We send the survey to members of the wider GitLab community, with the goal of asking for a response from any individual no more than twice per year.
At GitLab, we want everyone to be able to contribute. To that end we created First Look where we accept applicants to participate in various studies and testing.
We track our effectiveness through UX performance indicators (PIs). Our e-group reviews these PIs once a month in the Engineering Key Review.
User personas represent the people who actually use GitLab. The UX and Marketing teams use personas to inform decisions around the user experience and design.
Not only do our team members create great work for the wider GitLab community, but they also create some amazing industry-related resources to push our craft forward.