feat: clarify ux workflow

Katie Macoyrequested to merge
update-ux-process into main

Why is this change being made?

The goal of this change is to make sure that all Growth product designers use the same workflow.

This MR addresses a discussion in the Growth PM/UX/EM sync regarding issue and epic estimation. There was some confusion if product designers should be using UX issues. The documentation could be interpreted that designers work only at the epic level, not in issues.

After a Slack discussion with the Growth product designers, we would like to work in the following way:

  • Product designers create UX issues under a parent epic
  • Product designers use the UX issue to discuss early versions of the designs and ask for informal, pre-refinement feedback
  • When the designs are nearly final, the product designer documents them in the parent epic
  • The epic moves to ~workflow::refinement
  • After refinement, the product designer makes sure the epic is the SSOT for the designs (documenting any changes that resulted as part of refinement). The product designer closes the UX issue.
Screenshots of slack discussion

CleanShot_2025-12-04_at_11.25.19

CleanShot_2025-12-04_at_11.25.24

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct
    • The when to get approval handbook section explains when DRI approval is required
    • The who can approve handbook section explains how to identify the DRI
    • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
    • The approver may merge the MR. If they approve but don't merge, you can merge.
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • feat: clarify ux workflow

Merge request reports