Product Group and Team Pages

Purpose

Each team is empowered to work efficiently and document their practices in the GitLab Product handbook. This section is a collection of groups that have collected their processes and best practices in a single source of truth.


Analytics Section

What we cover

Who we are

Product Groups

Here are the individuals who work as part of one of the Analytics Section groups.

Analytics Instrumentation

Type Names Count
PM Tanuja Jayarama RajuTanuja Jayarama Raju 1
UX 0
EM Jiaan LouwJiaan Louw 1
FEM 0
FE 0
BE

Ankit PanchalAnkit Panchal

Sebastian RehmSebastian Rehm

Jonas LarsenJonas Larsen

Fulfillment Guide
The Fulfillment Sub-department is responsible for the infrastructure between the systems which affect the user purchasing process.
How the growth section works

Overview

The Growth stage is responsible for scaling GitLab’s business value. To accomplish this, Growth analyzes the entire customer journey from acquisition of a customer to the flow across multiple GitLab features - and even reactivation of lost users. Several groups help with this mission:

  • Activation, Conversion, Expansion, and Adoption connect users to the existing value that GitLab already delivers by rapid experimentation.
  • Analytics Instrumentation builds the backbone of data that other groups need to be successful, enabling a data-informed product culture at GitLab.

Growth’s ultimate goal is to connect GitLab’s value as a Single DevOps Platform with our customers. In order to do that, we take a zoom in and zoom out approach. We break down the entire GitLab growth model, and identify the highest ROI lever at this moment to focus on. In the Growth direction page we outline the Growth section’s long term direction and near term focus areas.

Plan:Project Management

Plan: Project Management

View all team members and stable counterparts

The responsibilities of this collective team are described by the Project Management Group. Among other things, this means working on GitLab’s functionality around work items, boards, milestones, iterations, to-do list, time tracking, planning analytics, and notifications.

  • I have a question. Who do I ask?

In GitLab issues, questions should start by mentioning the Product Manager (@gweaver). For UX questions, mention the Product Designer (@nickleonard). GitLab team-members can also use #s_plan.

Product Data Insights

Product Data Insights Handbook

The Product Data Insights group consists of a team of product analysts. This group reports to the VP, Product Management and serves as a functional analytics team to support the GitLab R&D Organization (Product and Engineering divisions), in addition to product data-related analysis across GitLab.

In addition to supporting the Product and Engineering divisions, the Product Data Insights team is an active contributor to the GitLab Data Program. As part of the Customer Product Adoption (CPA) Pod, the product analysts also work closely with members from the Enterprise Data team. In addition, the Product Data Insights team is part of the Functional Analytics Center of Excellence (FACE), along with other functional analytics groups across the GitLab Data Program.

Product Technical Program Manager
The Product Technical Program Manager (TPM) role supports cross-division initiatives across Product, UX, Engineering and other functions within R&D along with functions across GTM
Verify Product Group
The Verify Product Group wants to increase sharing, findability, and encourage bias for async communication.
Last modified November 1, 2024: Remove trailing spaces (6f6d0996)