Collate a list of design related tests for backlog planning
Problem
As a product manager, it is clear that many areas of our user experience and design could potentially be improved. As a team, we should gather a list of potential small design experiments and the learning we would like to gain.
Goal
Create a backlog of design related tests for future milestone planning.
Example
Test | Learning |
---|---|
Merge "Profile" (name and role) with payment page | Does removing a step from our paid signup process increase conversion, while still collecting the same information |
Show video for non-signed in users on https://about.gitlab.com/demo/ | Will we gain more sign ups by showing the video first vs. not showing the video without a sign up |
Incorporate "Buy now" CTAs on the feature comparison page | Can we increase conversion to paid packages by adding CTAs to this page? |
Customize content on the .com Register page based on what button the user clicked to get there. For example, if they clicked "Buy now" under the Bronze plan, we would show a value prop on that page specific to the Bronze plan | Does showing a value prop specific to the user's interests reduce dropoff on the registration page? |
Show yearly prices (instead of monthly) on the pricing page | Can we make this change without reducing conversion? Would this change make users less likely to drop out of the process when they get to the checkout screen and see price calculated annually? |
Mandatory group creation (similar to what we're doing in the .com paid signup) during registration for free users who have indicated that they are using GitLab for their company/team | Will starting out with a group make a user more likely to convert to a paid customer? |
Improve discoverability of the "Upgrade" button for free users who have a group and have indicated that they are using GitLab for their company/team | Will we see better conversion rates from within .com if we make upgrade options more obvious? |
Edited by Emily Sybrant