Product Design

1. You are here:
2. Engineering
3. UX Department
4. Product Design

Maintained by:

On this page

• Product Design at GitLab
• Team Structure
• Product Design Workflow
• See our work
• Heuristics for Success

Product Design at GitLab

We support the business of GitLab by becoming experts in our stage group, educating ourselves about the entire product, and staying engaged with user and business goals. We partner closely with our stable counterparts in Product Management and Development.

Team Structure

Each Product Designer is assigned to an area of our product, called Stage Groups. They learn everything they can about users and their workflows to design solutions for real customer problems.

Information about and strategic direction for these groups can be found here:

• Development (@gitlab-com/gitlab-ux/dev-ux)
  • Create
  • Ecosystem:FE/UX Foundations
  • Ecosystem:Integrations
  • Manage
  • Plan
• Sec (@gitlab-com/gitlab-ux/secure-protect-ux)
  • Secure UX
  • Protect UX
• Ops (@gitlab-com/gitlab-ux/ops-ux)
  • CI/CD (@gitlab-com/gitlab-ux/cicd-ux)
    • Verify UX
    • Package UX
    • Release UX
  • Configure and Monitor (@gitlab-com/gitlab-ux/configure-monitor-ux)
    • Configure
    • Monitor
• Growth (@gitlab-com/gitlab-ux/growth-ux)
• Enablement (@gitlab-com/gitlab-ux/enablement-ux)

Product Design Workflow

Product Designers follow the guidance outlined in the Product Development flow while working on stage group work with our stable counterparts.

For specific details:

• Planning and managing capacity
• Prioritization
• Working on Issues
• Design Process
• Partnering with UX Resesarch
• Partnering with Technical Writers
• Contributing to Pajamas

Are you a new GitLab Product Designer? If so, welcome! Make sure you see the Product Designer onboarding handbook page that will help you get started.

See our work

YouTube Playlist for UX Showcases

Heuristics for Success

The more we can check off each item in this list the more successful we will be:

• General
  • Use the simplest, most boring solution for a problem.
  • You are automatically granted permission to experiment and learn from your mistakes.
  • If you identify a problem, just go ahead and fix it. We only ask that you validate that it's a real problem first.
  • Assist the community in making an impact on our product.
  • Quirkiness is part of our DNA. We should embrace it in the right moments and contexts. 🤪
• Empathy
  • See the world through other people's eyes, and try to understand their experiences deeply and meaningfully.
  • Understand the user journey and goals.
  • Provide sufficient feedback and direction to achieve user goals.
  • Steer the user in the right direction if they end up in a “bad” place (without blaming them), and recognize their efforts and accomplishments!
• Structure
  • Maintain a strong information architecture.
  • Design holistic experiences and workflows.
  • Create a hierarchy and a sense of direction to guide users through the flow.
• Focus
  • Respect the importance of users' work and avoid gimmicky details.
  • Minimize distractions and clutter so users can focus.
  • Remove things that don't contribute to the user flow.
• Iteration
  • Never stop improving our products, Pajamas, and documentation.
  • Continuously iterate on our processes.
  • Think big, but break it down into small steps.
  • Aggressively break down issues into the smallest effort that gets results.
  • When applying the MVC approach, make things smaller by reducing the scope of the job-to-be-done rather than sacrificing the end UX.
  • Whenever possible, start in low-fidelity (wireframes, greyscale, etc.) to make sure we get it right before we go any further.