The GitLab Product team includes team members at various levels of Product Management job titles across our organizational levels with scope at various points in our product hierarchy. As a result there can be instances where peers across layers don't have the same title. We will always abide by GitLab's layer structure.
|Level||Job Families||Hierarchy Scopes|
|IC||Product Manager||Group, Stage|
|Manager||Group Manager Product, Director of Product||Collection of Groups, Stage, Section|
|Director||Director of Product||Section|
|Senior Leader||VP||All Sections|
All Managers and above in the Product function are considered product leaders. They can be referenced using the
@gl-product-leadership handle. This document describes important leadership concepts specific to the product management team. See also our page on general GitLab leadership guidance.
Product team members who:
This group can be referenced in GitLab.com issues using the
As a product team leader, it's important to set the tone for the organization. We put our PMs individually in the forefront as Directly Responsible Individuals (DRI), with the trust and power that they can make the right decisions with our support as product leaders. This section is intended to outline some best practices for working between PMs and their leaders. It contains guidance on responsibilities and expectations the leader should have in working with PMs, but is not intended to be hard and fast rules that take the place of having a strong working relationship and prioritizing things effectively together.
Note - This is intended as a supplement to the product director or group manager of product job descriptions with specific focus on the interaction between PMs and their managers. General job responsibilities can be found at that link.
An effective product leader should: