Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Product Direction - Expansion

Overview

The Expansion Team at GitLab focuses on running experiments to increase the expansion of our platform and expanding usage by teams within an organization or by individual users additionally we strive to increase the value of Gitlab to existing customers getting them to adopt new features in higher paid tiers. It's easy to look at GitLab and quickly come to a conclusion that our platform is for technical teams only (e.g. developers and engineers) but in fact many other non-technical teams can use GitLab to increase efficiency and integrate their work into a company's development life-cycle. To call out a few Product Managers, Data Analysts, Marketers, Support, UI/UX and Executives use GitLab in their day-to-day. We want to get these teams to that ‘ah-Ha!’ moment so they can also benefit from using the platform. Our experiments are all public and we encourage feedback from the community and internal team.

Expansion Team

Product Manager: Tim Hey | Engineering Manager: Phil Calder | UX Manager: Jacki Bauer | Product Designer: Matej Latin | Full Stack Engineer: Doug Stull | Full Stack Engineer: Jackie Fraser

Expansion Team Mission

Expansion KPI

Supporting performance indicators:

Our approach

Expansion runs a standard growth process. We gather feedback, analyze the information, ideate then create experiments and test. As you can imagine the amount of ideas we can come up with is enormous so we use the ICE framework (impact, confidence, effort) to ensure we are focusing on the experiments that will provide the most value.

Maturity

The growth team at GitLab is new and we are iterating along the way. As of August 2019 we have just formed the expansion group and are planning to become a more mature, organized and well oiled machine by January 2020.

Problems we solve

Do you have issues… We’d love to hear about them, how can we help GitLab contributors find that ah-Ha! Moment.

Here are few problems we are trying to solve:

What user workflows does the expansion team focus on?

The user workflows on GitLab.com and our Self-managed instances are very different and should be treated separately. We will be focusing on the 2 described below. note: our sales team outlines the process in point 3. on this page. (Again the sales motion is very different than the self serve experience on GitLab.com).

Key User Focus:

External

The external user personas on GitLab.com and our Self-Managed instances are very different and should be treated as such. We will be focusing on the 2 described below.

In addition to the personas, it's also important to understand the permissions available for users (limits and abilities) at each level.

GitLab Team Members

Apps & Services we focus on: