Experience Recommendations: Fulfillment FY23-Q4 - Purchasing a subscription for a self managed instance
- UX Scorecard Part 1: {{#2177 (closed)}}
-
Resulting Recommendations: See below
👇
Some of these issues listed below are already known and highlighted in previous scorecards.
-
Consistent fulfillment emails. With the design of a new email template, we should start rolling the template out to more use cases. For example, when we send the license key via email.
-
Consolidating purchase flows. This issue will account for the problem I highlighted about the
billing information
column being too narrow and awkward in size. When we consolidate the purchase flows, we can incorporate the gitlab.com styling for thebilling information
column. -
Social Sign in.
Remember me
button on sign in is repeated under the social sign in. I think the overall layout of the social sign in section could be simplified. -
Show Success message on manage purchases page. This will simplify the purchase flow and removes an unnecessary step.
-
Research/Exploration: Deep linking activation key. Explore idea of deep linking the activation key so it can be done automatically.
Experience Recommendations Checklist
Learn more about UX Scorecards
-
Add this issue to the stage group epic for the corresponding quarter's UX scorecards. -
Brainstorm opportunities to fix or improve areas of the experience. - Use the findings from the Emotional Grading scale to determine areas of immediate focus. For example, if parts of the experience received a “Negative” Emotional Grade, consider addressing those first.
-
Create an issue for each recommendation using one of the Actionable Insight templates in the GitLab project, depending on if it relates to a product change or needs more exploration. Alternatively, you can create a separate epic to hold all your recommendations. Add a UX scorecard-rec
label to every issue or epic for traceability. To help with prioritization, add a severity label to communicate appropriate urgency and impact to the experience. Link to the epic or issues here.- Recommendations do not need to be documented in your Dovetail project.
-
Think iteratively, and create dependencies where appropriate, remembering that sometimes the order of what we release is just as important as what we release. - If you need to break recommendations into phases or over multiple milestones, create multiple epics and use the Category Maturity Definitions in the title of each epic: Minimal, Viable, Complete, or Lovable.