As a Product Org we strive to consistently create products and experiences that customers love and value.
The Product Principles section is where you can learn about our strategy and philosophy regarding product development here at GitLab.
For a detailed view on how we do Product Development, read up on our established Product Processes.
To learn how the GitLab product and our Teams are organized review our Product Categorization section.
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.
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 the Roles and Responsibilities of a PM.
Learn how we measure success in Product via our Product KPIs and OKRs, 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.
Learn about our Product Leadership Team and learn about them via their personal README’s.
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 todos 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:
Required 🔎
The Product handbook contains a lot of content that includes a mix of advice, best-practices, mandatory process, team-specific content, and more. To help you find the most important items, look for the badge above that indicate the most essential, important, and/or obligatory processes that every Product Manager is expected to know by heart and follow, as opposed to other items which may be more for reference in certain situations or may be more optional than required. If you are adding or updating an essential handbook section, consider adding this badge there.
If you see any typos, copywriting improvements or small content clarifications you'd like to contribute, please create a merge request and merge it yourself (provided you have merge permissions to this repository). And please mention Product Operations in the merge request as a heads up and so we can thank you! Since we have a bias for action, we trust your judgement.
If you have a larger change such as wanting to add new sections or significantly modify content in an existing section, please create a merge request and direct ping Product Operations DRI to simply inform, request review or seek collaboration. If you have a larger change such as wanting to add/modify content to the product handbook landing page or adding entirely new pages (or don't have merge permissions), please create a merge request and direct ping Product Operations DRI for review, collaboration and approval. If you're looking ot create an entirely new directory, it is recommended you discuss in advance with product operations to avoid needing to move it or resturcture it later.
Please note it is your responsibility to inform GitLabbers as needed about your merge request, so we can all stay aligned and informed. Depending on the scope of changes, consider the following these best practices to inform product managers and other cross-functional team members:
