We create products and experiences that customers love and value.
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:
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:
It is your responsibility to communicate with relevant team members about your merge request. Here are some best practices to follow:
@gl-productin the merge request before merging.
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.
Understand the roles and responsibilities of product managers.
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.
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.
Understand the OKR Process for the GitLab Product Team and review current and past OKRs.
Learn about our Product Leadership Team and learn about them via their personal README’s.
Below are team emails and handles that can be used for different departments and sub-departments in the Product Division. These groups are used for internal communication and the
@mention can only be used by project members. Please remember that tagging
@mention on issues will generate in-product to-do items and email notifications to all team members in that project, so use it only when you need to communicate with the entire team. For communication specifically for product managers, please leverage How to Engage.
@gl-product-leadershiptags all group managers, directors and VPs in the Product Division
@gl-product-plttags all direct reports to the VP Product in the Product Division
@gl-producttags to all members of Product Management, Product Monetization and Product Operations in the Product Division
firstname.lastname@example.org all members of Product Management, Product Monetization and Product Operations in the Product Division
email@example.com all members of UX (UX Research, Technical Writing and Product Design) in the Product Division
@gitlab-com/gitlab/-uxtags all members of UX (UX Research, Technical Writing and Product Design) in the Product Division
@gitlab-com/gitlab-ux/managerstags all people managers within UX (UX Research, Technical Writing, and Product Design)
@gitlab-com/gitlab-ux/designerstags all Product Designers and Design Managers in UX
@gl-docsteamfor all Technical Writers in UX
When you are tagging