Group:Activation is part of the Growth Sub-department. We work on connecting our users with our product value.
Questions should start by @ mentioning the Product Manager for the Activation group or creating a new issue in the Activation Workflow board.
The Growth:Activation Group works on product priorities and growth deliverables with our Growth product managers and contributes to Growth initiatives including the Registration Flow and Continuous onboarding.
The following people are permanent members of the Growth:Activation team:
| Person | Role |
|---|---|
| Jay Swain | Acting Fullstack Engineering Manager, Growth:Activation and Adoption |
| Alex Buijs | Senior Fullstack Engineer, Growth:Activation |
| Eugie Limpin | Senior Fullstack Engineer, Growth:Activation |
We work directly with the following team members in the Growth:Activation group:
| Person | Role |
|---|---|
| Jensen Stava | Senior Product Manager, Growth:Activation |
| Emily Bauman | Product Designer, Growth:Activation |
| Kati Paizee | Senior Technical Writer, Growth (Activation, Conversion, Expansion, Adoption), Ecosystem (Integrations) |
| Alex Buijs | Senior Fullstack Engineer, Growth:Activation |
| Andrew Kelly | Senior Security Engineer, Application Security, Growth (Activation, Conversion, Expansion, Adoption), Fulfillment (Purchase, License, Utilization), Enablement (Distribution, Geo, Memory, Global Search, Database) |
| Eugie Limpin | Senior Fullstack Engineer, Growth:Activation |
We collaborate with our colleagues in the Growth Sub-department teams:
As well as the wider Growth Sub-department stable counterparts.
The Growth UX team has a handbook page which includes Growth specific workflows.
Prioritization is a collaboration between Product, UX, Data, and Engineering.
We use the Product Development workflow when working on issues and merge requests across multiple projects.
While not all of the work we do relates to the GitLab project directly, we use
milestones to track Deliverables and other enhancements.
The above boards can be filtered by milestone to provide additional context around priority.
For example a priority::3 security issue (due within 90 days)
will be added to one of the next 3 milestones by the Engineering team during the workflow::scheduling stage to ensure that SLA is met.
#g_activation in Slack (GitLab internal)#s_growth in Slack (GitLab internal)