Display security navigation in left sidebar to a cohort of net new .com signups

Hypothesis

Some free users do not know that the GitLab platform offers security features.

Supporting data

When a net-new user signs up for GitLab.com account, the only way the can discover the security features is by reading the documentation on their own, talking to someone at GitLab, starting a trial or upgrading.

Experiment design

We split net new sign-ups into two groups. The control gets the standard experience today where we do not display Security in the navigation. The experiment group will get the same onboarding experience as the control but the Security navigation item will be present in the left-hand side navigation. If a user selects the security options we will display a paywall state where we pitch the value of security features available in GitLab and give them the opportunity to upgrade or start a trial.

Internal approvals for navigation changes

The handbook states the navigation is a shared space across the product organization based on who owns a particular feature. The secure PM has signed off on us running this experiment in this issue #97.

Design

We will use this locked feature page design and allow users to toggle between 4 images.

Image 1 (on page load) Image 2 Image 3 Image 4
project_security_dashboard_v12_3 pipeline_security_dashboard_v12_3 group_security_dashboard_v12_3 sast

Title copy:

Security capabilities, integrated into your development lifecycle.

Main body copy: Check your application for security vulnerabilities that may lead to unauthorized access, data leaks, and denial of services.

GitLab will perform static and dynamic tests on the code of your application, looking for known flaws and report them in the merge request so you can fix them before merging.

Security teams can use dashboards to get a high-level view on projects and groups, and start remediation processes when needed.

CTAs: Primary CTA: Start a free trial

Primary CTA URL: https://customers.gitlab.com/trials/new?gl_com=true

Secondary CTA: Upgrade now

Secondary CTA URL: https://gitlab.com/profile/billings

Success metric

We will compare the upgrade and trials rates of the control vs experiment group at both the user and account (namespace) levels. We will also want to track the page view to CTA section to action taken (i.e. trail started or upgrade succeeded) so we have a baseline to compare to for any future iterations to this experiment.

ICE score

Impact Confidence Ease Score
6 7 8* 7
  • Needs to be revised after UX design
Edited by Sam Awezec