Product Handbook

Maintained by:

Welcome to the Product Team Handbook

The Product Team is led by David DeSanto
The Product Handbook focuses on how we do product at GitLab.
Please see Product Direction to learn about what the Product Team plans to build

Product Team Functions

Product Team Mission

We create products and experiences that customers love and value.

Consistency wins as you scale. Our organizational goal is to create a Product Manager (PM) system that maximizes the chances of success across new products, new features, and new team members.
We are shipping an experience, and not just a product. Don’t forget about the links between the product and the website, pricing & packaging, documentation, sales, support, etc.
It’s about our customers and doing a job for them, not the product itself. Think externally about customer problems, not internally about the technology.
It’s about love AND value. Will customers value what we are building? We need to make sure what we build helps build and extract customer value.

Contributing to the Product Handbook

The product handbook is widely referenced by product managers and cross-functional team members. Therefore, we want to follow a consistent change management process so all affected collaborators are aligned and informed when there are changes (specially new requirements, processes, meetings, etc.) that affect their workflow. To help ensure awareness across teams, when suggesting a change to the product handbook, please use the Change-Product-Handbook merge request description template. This ensures your changes are included in Product Operations Releases.

This template will also help you out by automatically adding labels and assigning required reviewers.

You will also be asked to indicate which type of change you are suggesting:

Small improvement (typos, clarifications, etc.)
Adding a new section
Modifying existing section
Documenting a new process
Adding a new page or directory
Other

For a small improvement, please feel free to merge the MR yourself. Otherwise, the template will ping Product Operations for collaboration and review, and the guidance below should be followed for driving awareness:

Informing team members about the changes

Please note it is your responsibility to inform team members as needed about your merge request. Consider the following best practices:

If it's a significant change that broadly affects the whole Product team and/or the Engineering team, please consult Product Operations for the best communication strategy. Otherwise, please follow the suggestions:
- If only specifically relevant to product management, tag '@gl-product' in the MR prior to merging
- If relevant to other teams, tag department leads such as the VP of UX, VP of Development or the Director of Quality Engineering in the MR prior to merging
- Share and cross post the MR link with a brief description in relevant channels such as Slack #product, #product-leadership, #eng-managers, #ux-managers
- Add as a read-only or discussion topic as appropriate in the Weekly Product Management Meeting
- If you need more guidance on how/where/when to share, check out more tips and best practices in GitLab Communication

Product Management

If you'd like to collaborate with product management see the How to Engage guide.

Product Principles

The Product Principles section is where you can learn about our strategy and philosophy regarding product development here at GitLab.

Product Processes

For a detailed view on how we do Product Development, read up on our established Product Processes.

Product sections, stages, groups, and categories

To learn how the GitLab product and our Teams are organized review our Product Categorization section.

About the GitLab Product

Learn about GitLab as a product, including what does it mean to be a single application, our subscription tiers and pricing model, and the basics of permissions in the platform.

Product Manager Responsibilities

Understand the roles and responsibilities of product managers.

Being a Product Manager at GitLab

Want to know more on what being a Product Manager at GitLab is like? Checkout our Product Manager Role guide for helpful information like our Career Development Framework and learning/development resources.

Product Performance Indicators

Learn how we measure success in Product via our Product KPIs, which are tracked in our Product project. For best practices and guidance on how to add instrumentation for features please review our Product Intelligence workflow.

Product OKRs

Understand the OKR Process for the GitLab Product Team and review current and past OKRs.

Our Product Leadership Team

Learn about our Product Leadership Team and learn about them via their personal README’s.

Communicating with the Product Team

GitLab team members should leverage How to Engage to interact with the product team.

Members of the Product team are added to the private product group @gl-product. This group is used for internal communication and the @gl-product mention can only be used by project members. Please remember that tagging @gl-product on issues will generate in-product to-do items and email notifications to all product team members, so use it only when you need to communicate with the entire product team.

If you are tagging @gl-product:

Clearly state why you are tagging the entire product team and what action you need product team members to take.
Write a short summary in the same comment so team members can quickly understand the necessary context.
Review the issue title and description to ensure it has relevant details other product team members need BEFORE submitting the comment. The issue title will be the subject of email notifications and in-product to-do items.
If asking team members to review a change, please directly link to the specific page on the review app and any relevant issues or MRs.