One of the ways we track our progress is by measuring the UX of our different workflows (scorecards) and progress towards closing out issues that impact UX (issues labeled SUS:Impacting).
View Fulfillment Cross-Functional Dashboard
View the complete Fulfillment UX Scorecard Playlist on YouTube
| JTBD | Score | Date | Opportunities |
|---|---|---|---|
| SSO: Registering for CDot | Backlog | ||
| SSO: Signing in to CDot | Backlog |
View Open SUS:Impacting Issues for Fulfillment Platform
| JTBD | Score | Date | Opportunities |
|---|---|---|---|
| Renew a subscription (SaaS and SM) (based on renewals research) | NA | Jan 2023 | - Consolidate and improve renewal messaging in app and emails - Improve seat usage visibility |
| Manually renewing a GitLab subscription | C- | Jan 2023 | - customize email content and timing to customer context - improve SSO for seamless log in - improve UI with better readability and workflow |
| Upgrade a self-managed subscription | C- | Jan 2021 | Needs to be re-scored to identify opportunities |
| Upgrade a GitLab.com subscription | C | April 2020 | Needs to be re-scored to identify opportunities |
| Add additional seats to my subscription | To be scheduled | ||
| Link to a different namespace to use my plan with a different group | To be scheduled | ||
| Cancel a subscription | To be scheduled | ||
| Change/update subscription contact | To be scheduled |
View Open SUS:Impacting Issues for Billing & Subscription Management
| JTBD | Score | Date | Opportunities |
|---|---|---|---|
| Purchasing a Self-Managed Subscription | C | Jan 2023 | - update emails to all use same template - Improve navigation from purchase to activation |
| Purchasing a GitLab.com Subscription (new user via a Trial) | C | Oct 2022 | - Auto sign-in users after email verification - Allow users to verify email later - Improve findability of upgrade link - More immediate access to paid features after purchase |
| Purchasing a GitLab.com Subscription (existing user) | C | Oct 2022 | - Improve findability of purchase link for a group - More immediate access to paid features after purchase |
| Purchase add-on storage | |||
| Buy add-on units of compute | C | April 2020 | Needs to be re-scored to identify opportunities |
View Open SUS:Impacting Issues for Purchase
| JTBD | Score | Date | Opportunities |
|---|---|---|---|
| Determining where my storage is high in order to reduce it | D | Jan 2023 | - Support setting up good storage policies - Improve transparency into storage by project and type, including history Ensure accurate documentation |
| Removing a user from my SaaS subscription | D | Sep 2022 | - Improve clarity around who uses a seat - Improve workflow clarity (buttons, alerts) |
| Removing a user from my self-managed subscription | To be scheduled | ||
| Exclude a user from billing in my self-managed subscription | To be scheduled | ||
| Determine how to make a single user non-billable (self-managed) | To be scheduled | ||
| Set up auto-provisioning such that users are non-billable (self-managed) | To be scheduled |
View Open SUS:Impacting Issues for Utilization
| JTBD | Score | Date | Opportunities |
|---|---|---|---|
| Activate a self-managed license | To be scheduled | ||
| Opt out of usage data and get offline license | To be scheduled | ||
| Linking a sales-assisted subscription to GitLab.com | To be scheduled |
View Open SUS:Impacting Issues for Provision
We follow the Product Designer workflows and UX Researcher workflows described in the Product Design section of the handbook. As Growth designers, we relentlessly measure the impact of our design changes following the experimentation workflow. In addition:
We use the Product Development Flow to help move issues through the product lifecycle. For the design phase to begin, the following are important:
The template can also be copied into the main issue that is the SSOT.
There is a lot of overlap between Fulfillment groups, so we work very closely. To keep things simple and clear, we follow GitLab internal communication guidelines. In addition the following tips will make it easier to collaborate with Product Designers who span multiple groups:
We collaborate with each other on issues across different Fulfillment Groups. On our monthly planning issues, each designer should indicate high priority or time consuming issues from other groups. A link to the other planning issue is fine too, just so it's easy for the Product Design Manager and Product Managers to navigate to this information.
The engineering team applies the UX label to any MR that introduces a visual, interaction or flow change. These MRs can be related to new issues, bugs, followups, or any type of MR. If the engineer isn't sure whether the MR needs UX, they should consult the designer who worked on the related issue, and/or the designer assigned to that stage group, or the Product Design Manager.
Live reviews are desired for any MR with the UX label. When the MR is in workflow::In review, the engineer assigns the MR to the designer for a review using the reviewer functionality in the sidebar. This can happen in parallel with the maintainer review. Designers should prioritize these reviews to complete them as quickly as possible.
There are times when it isn't possible or practical for a Product Designer to complete their review via their local environment. At these times, the Product Designer can review screenshots and videos in the MR description or coordinate a demo with the Engineer. Another option for more complicated changes is keeping the change behind a feature flag and reviewing the change on staging after the MR has been merged. This is up to each Product Designer's discretion.
