Growth Stage
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
Product & Design
| Role | Person |
|---|---|
| Product Managers |
Elyse Mallinger
|
| Product Designers |
Jesse Young
,
Katie Macoy
|
Teams & Communication
Growth uses these Slack channels:
- #s_growth - the main Growth channel
- #sd_growth_engineering - Growth engineering discussion
| Team | GitLab Handle |
|---|---|
| Growth (All) | @gitlab-org/growth |
| Growth engineers | @gitlab-org/growth/engineers |
All Team Members
Shared Processes
Our teams collaborate using shared processes and tools:
- Operating Model - operating rhythm for growth
- Milestone Planning, Refinement and Estimation - continuous refinement process and estimation guidelines
- Engineering DRI for Large-Scale Initiatives - managing complex workstreams and epics
- Modular Code Guiding Principle - why and how we write modular code by default
- Technical Exploration Guidelines - guidelines for research and spike work
- Growth Experimentation Guidelines - guidelines for growth experimentations
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:
- Growth direction
- Growth Epic Kanban board
- Growth Issue Kanban board for development
- Experimentation
- GLEX
- Experiment rollout
Team Boards
We track our current work on these boards:
- Driving First Orders epic board - Driving First Orders epics that are next up
- Feature Work board - Driving First Orders feature work in the current milestone
- Product Foundations board - bugs, tech debt, and Engineering Excellence work in the current milestone
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.
Common Links
- Growth stage
- Growth workflow board
#s_growthin Slack (GitLab internal)- Growth opportunities
- Growth meetings and agendas (GitLab internal)
- GitLab values
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.
Experimentation
GitLab Epic Summary with Duo Agent
GitLab Follow-up Issue Enhancement with Duo Agent
Growth Fast Boot September 2019
Growth Milestone Planning, Refinement and Estimation
Modular Code Guiding Principle
Operating Model for Growth Stage
Technical Exploration ("Spike") Guidelines
Trials Ownership and Collaboration Framework
30467738)

Elyse Mallinger
Ekwa Duala-Ekoko
Doug Stull
Emily Sybrant
Jesse Young
Katie Macoy
Buck O'Leary
David Hamp-Gonsalves
Konstantin "Konsti" Greif
Kiesha Herman
Marco Tomasi
Paul Gascou-Vaillancourt
Roy Liu