Growth Stage

The Growth Stage is one team that removes what stops people from buying GitLab, through product changes and experiments.

Mission

Growth turns GitLab’s self-serve funnel into a reliable, compounding source of new paid customers by removing what stops people from buying, rather than by generating more traffic.

Our north star is Web Direct first orders across GitLab.com and self-managed. A Web Direct first order is a first order (GitLab internal) that a customer places through self-service, without sales assistance. We rank work by its impact on first orders, not signups.

Each funnel stage has one input metric that the roadmap is built to move:

flowchart LR
    ACQ["Acquisition\nValuable trial starts and free signups"]
    ACT["Activation\nValuable Aha activation within 14 days"]
    MON["Monetization\nValuable activation to first order"]
    FO["Outcome\nWeb Direct first orders"]

    ACQ --> ACT
    ACT --> MON
    MON --> FO

Growth owns the in-product path from first visit to first purchase: registration, onboarding, in-product upgrade and purchase entry points, the trial experience, in-product notifications, and experimentation tooling (GitLab Experiment (GLEX) and the Experimenator). Key partners are Fulfillment, Pricing, Digital Experience, Lifecycle Marketing, and Enterprise Analytics.

For Growth’s principles, metrics, ownership, and current priorities, see the Growth direction page and how the growth section works.

How We Work

Working inline with our values, we focus on iteration and collaboration, working with and across areas of the product our development department counterparts maintain.

We work on the issues prioritized by our product teams including running experiments on GitLab.com. Growth is one team with one roadmap, and engineers are assigned to the highest-ranked work on the roadmap. Growth engineers are Fullstack Engineers. The reason for this is that Growth needs both Frontend and Backend skill-sets, but as a small team, has optimized for team member efficiency to adopt the Fullstack role.

Growth Leadership & Teams

Leadership

Role Person
Product Director Elyse MallingerElyse Mallinger
Engineering Director Ekwa Duala-EkokoEkwa Duala-Ekoko
Engineering Manager Travis ShieldsTravis Shields
Senior Staff Fullstack Engineer Doug StullDoug Stull
UX Design Manager Emily SybrantEmily Sybrant

Product & Design

Role Person
Product Managers Elyse MallingerElyse Mallinger
Product Designers Jesse YoungJesse Young , Katie MacoyKatie Macoy

Teams & Communication

Growth uses these Slack channels:

Team GitLab Handle
Growth (All) @gitlab-org/growth
Growth engineers @gitlab-org/growth/engineers

All Team Members

Name Role
Travis ShieldsTravis Shields Engineering Manager, Growth
Fullstack EngineerFullstack Engineer Fullstack Engineer, Growth:Engagement
Buck O'LearyBuck O'Leary Senior Fullstack Engineer, Growth:Activation
David Hamp-GonsalvesDavid Hamp-Gonsalves Senior Fullstack Engineer, Growth:Acquisition
Konstantin "Konsti" GreifKonstantin "Konsti" Greif Fullstack Engineer, Growth:Engagement
Kiesha HermanKiesha Herman Fullstack Engineer, Growth:Activation
Marco TomasiMarco Tomasi Fullstack Engineer
Paul Gascou-VaillancourtPaul Gascou-Vaillancourt Staff Fullstack Engineer, Growth:Engagement
Roy LiuRoy Liu Fullstack Engineer, Growth:Activation

Shared Processes

Our teams collaborate using shared processes and tools:

Experimentation

Experiment velocity is Growth’s top-ranked problem, because it multiplies the impact of all our other work. Growth owns GLEX and the Experimenator, our AI-assisted experiment pipeline. Every experiment is read out before we decide whether to ship it. See Growth experimentation for the process.

Resources

Some useful links to see how and what we are working on include:

Team Boards

We track our current work on these boards:

See work queue boards for what belongs on each board.

Team Days

On occasion we hold virtual team days or meetings to take a break and participate in fun, social activities with our Growth counterparts.

CustomersDot Trials Collaboration

For information about trials ownership and collaborating with the Fulfillment/Monetization team on trials work, see our Trials Ownership and Collaboration Framework. This framework defines the conceptual ownership model — Growth owns trial entry points; Fulfillment/Monetization owns the deeper trial codebase and all CustomersDot support — along with the decision framework and escalation paths for priority conflicts.


Engineering DRI for Large-Scale Initiatives
Managing complex workstreams and epics within Growth teams
Experimentation
Information about creating and running experiments at GitLab.
GitLab Epic Summary with Duo Agent
Process for summarizing epic status based on related issues, comments and statuses.
GitLab Follow-up Issue Enhancement with Duo Agent
Process for transforming generic GitLab follow-up issues into well-structured, actionable work items using Duo Agent.
Growth Fast Boot September 2019
Growth groups met in September 2019 for a fast boot to discuss, plan, and begin implementing a Growth strategy at GitLab
Growth Milestone Planning, Refinement and Estimation
Continuous refinement process and estimation guidelines for Growth teams
Modular Code Guiding Principle
Why and how Growth Engineers write modular code by default, optimizing for AI-native collaboration and long-term maintainability
Operating Model for Growth Stage
The operating rhythm for the Growth team: one team, one roadmap, and a weekly reporting cadence.
Technical Exploration ("Spike") Guidelines
Guidelines for research and technical exploration work within Growth teams
Trials Ownership and Collaboration Framework
Conceptual ownership model and decision framework for trials work across Growth and Fulfillment/Monetization