UX Designer

On this page

UX Designer

Like other departments at GitLab, we follow the GitLab Workflow and the Engineering Workflow. Reviewing those resources is a good starting point for context on the UX designer workflow below.

UX Designer onboarding

If you are just starting out here at GitLab, welcome! Make sure to review all the pages here in the UX section of the handbook, they will help you get oriented. There is also a specific page dedicated to UX Designer onboarding.

Working on issues

Scheduling of issues in a milestone

All issues in a milestone labeled Deliverable that need UX will be assigned to a UX designer by the kickoff. The UX designer/designers for a given area should coordinate with the PM and their backup during scheduling for any work that is critical. UX designers assign themselves to issues in a milestone. UX designers should aim to schedule 80% of their capacity to work on responsibilities as outlined in the role descriptions and try to block off the remaining 20% for other pro-active work. This can be anything from exploring GitLab as a product, exploring competitive products and how GitLab compares to them, to conducting their own research and interacting with users and other team members.

Issues labeled Stretch may or may not be assigned to a UX designer by the kickoff.

Priority for UX issues

UX works on issues in the following order:


Define the scope:

Propose a solution:


Follow through

UX Reviews


If the UX work introduces or changes any of the UX standards or building blocks:


As design can be subjective, discussion can heat up. Always try to be direct, but kind. Try to give your best reasoning for your choices and evaluate everyone's opinions. Come up with a solution instead of discussing endlessly. If you think additional perspective is needed, mention a fellow UX Designer in the issue.