Product Design
Role of Product Designers
Product Designers are assigned to a specific area of the product, known as Stage Groups, where they immerse themselves in user workflows to solve real customer problems.
They are also responsible for broader UX department efforts, such as:
- Supporting community contributions
- Contributing to the Pajamas Design System
- Reviewing other designers’ work
Each designer works as a manager of one to solve customers problems and align with the direction of the product. They collaborate with stage peers and managers to manage their capacity and deliver results on time. For a detailed view into how Product Designers work, review the Product Designer workflow page.
For more information on Stage Groups, team member assignments, and product direction, visit the product category page.
Process and Design Responsibility
Owner of design judgment
As Product Designers, we are entrusted with the authority of design judgment. Our process begins with understanding the problem and prioritizing for the best user experience. When additional constraints or insights (e.g. technical considerations or marketing strategies) arise, we collaboratively evaluate and adjust our designs accordingly. We proactively communicate how these constraints impact our designs and what changes will affect the user.
In cases where our counterparts have differing opinions, we consider their perspectives but hold the final say on design decisions as we are the ultimate guardians of design judgment.
Design Principles and Tools
Our design principles are outlined in the Pajamas Design System.
Product Designer Tools
- UX Scorecard
- Category Maturity Scorecard
- UX Issue Triage
- Heuristics
- Competitor Evaluation (GitLab Team Member access only)
- UX Cloud Sandbox
Figma and Figjam are our primary design tool of choice. Refer to the usage and access details.
Product Design Workflow
Product Designers adhere to the Product Development flow in collaboration with stable counterparts. Key aspects include:
- Planning and managing capacity
- Prioritization
- Working on Issues
- Design Process
- Partnering with UX Research
- Partnering with Technical Writers
- Contributing to Pajamas
- Designing with AI
New GitLab Product Designers should refer to the Product Designer Workflow handbook page for a comprehensive guide to getting started.
Product Design Management Workflow
Learning and Development
Our continuous learning initiatives are documented in the UX Department Learning and Development section.
Cross-functional Initiatives
Beautifying our UI
This initiative aims to enhance our product’s usability by leveraging the best practices from the “Macro UX” experiment, which paired Product Designers and Engineers to make self-directed improvements. See the retro issue for details.
Key Elements:
- Self-directed improvements: Product Designers and Engineers are empowered to fix usability issues they identify without strict prioritization constraints.
- No restrictions on product area: Improvements can be made across any product area, fostering broad collaboration.
- Work in MRs, not issues: Direct changes are made through Merge Requests (MRs), with comprehensive documentation and explanations.
- Length of rotation: Pairings last 1-3 milestones, depending on what the pairing believes is appropriate. Multiple pairs can be working simultaneously on Beautifying our UI.
- Prioritization: Participants coordinate with their managers to balance their involvement with regular responsiblities.
- Documentation: All changes must be documentated, adhering to the Definition of Done, and involving relevant Technical Writers.
Volunteering and Participation
To volunteer, Product Designers and Engineers should:
- Create an MR to add their name to the volunteer table and assign it to their manager for review.
- Indicate the percentage of capacity dedicated to the initiative.
- Create an issue and link all related MRs for transparency and tracking.
- Ensure all changes align with the Pajamas Design System and leverage feature flags where appropriate.
Volunteers:
Milestone | Product Designer | Engineer |
---|---|---|
17.5 | ||
17.6 | ||
17.7 | Emily Bauman | Anna Vovchenko |
17.8 | ||
17.9 |
Previous Volunteers
Milestone | Product Designer | Engineer |
---|---|---|
17.1 (2024-05-13) | Veethika M | Miguel Rincon |
16.1 (2023-05-18) | Veethika M | Payton Burdette |
15.11 (2023-03-18) | Annabel Gray | Phil Hughes |
15.6 (2022-10-18) | Matej Latin | Deepika Guliani |
15.5 (2022-09-18) | Katie Macoy | Anna Vovchenko |
15.4 (2022-08-18) | Nadia Sotnikova | Alex Kalderimis |
15.2 (2022-06-18) | Emily Bauman | Jannik Lehmann |
15.1 (2022-05-18) | Sascha Eggenberger | Robert Hunt |
15.0 (2022-04-18) | Annabel Gray | Phil Hughes |
Measuring Success
Success of the program will be tracked by the total number of MRs merged with the “Beautifying our UI” label.
Risks and Considerations
- Time commitment: The time required for these pairings is variable, potentially impacting regular milestone work and OKRs.
- No user research: Focusing on heuristic reviews might introduce new friction points without direct user feedback.
By following these guidelines, GitLab’s Product Design team can continue to drive meaningful, user-centric improvements across the platform.
Product Design Manager Workflows
UX Themes
ac0e3d5e
)