The Growth:Conversion 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:Conversion team:
|Kamil Niechajewicz||Fullstack Engineering Manager, Growth:Conversion|
|Alper Akgun||Staff Fullstack Engineer, Growth:Conversion|
|Dallas Reedy||Fullstack Engineer, Growth:Conversion|
|Sam Figueroa||Fullstack Engineer, Growth:Conversion|
|Serhii Yarynovskyi||Fullstack Engineer, Growth:Conversion|
We work directly with the following team members in the Growth:Conversion group:
|Sam Awezec||Principal Product Manager, Growth:Conversion|
|Kevin Comoli||Product Designer, Growth:Conversion|
|Kati Paizee||Senior Technical Writer, Growth (Activation, Conversion, Expansion, Adoption), Ecosystem (Integrations)|
|Andrew Kelly||Senior Security Engineer, Application Security, Growth (Activation, Conversion, Expansion, Adoption), Fulfillment (Purchase, License, Utilization), Enablement (Distribution, Geo, Memory, Global Search, Database)|
We collaborate with our colleagues in the Growth Sub-department teams:
As well as the wider Growth Sub-department stable counterparts.
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.
|Planning||This board shows Conversion team work that has been allocated to a particular milestone.|
|Deliverables||A subset of the milestone board shows issues the Product Manager has determined to be
UX- defines what the team should aim to deliver. Once complete, the Product Manager will move to
workflow::planning breakdown(larger issues) or straight to
workflow::schedulingfor Engineering to pick up. If there is no Engineering input required the issue can be closed.
group::conversion) schedules issues for development in the build phase, based on the Product Managers priorities. For
security issues, Priority and Severity labels will have been added by the Product Manager.
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.