For an overview of our overall approach to OKRs, as well as any company-wide OKR due dates, visit Objectives and Key Results (OKRs).
This page provides an overview of the Product Division OKR workflow. All departments (product management, UX, etc.) collaborate by following this guidance. For clarifications on the OKR process, team members can post in Slack #product and tag Product Operations. Team members can also attend Product Operations office hours for live support. Every quarter, there will also be a feedback issue linked on this page as part of the current quarter references that anyone can contribute to.
This section will be updated by Product Operations quarterly.
Product Division (PM and UX) OKRs for the following quarters can be found in this sheet as Ally.io usage is has been sunsetted:
When to update the status of Product OKRs
How to report progress of Product OKRs
How this will look in Product Key Review slides
It is highly recommended that product groups limit the number of OKRs they commit to so they have reasonable bandwidth to deliver on them. PMs should consider either setting 1 OKR that's not related to a product theme OR 3 or fewer KRs if they are using the product themes as their objectives.
Here's are some examples of how GPMs and PMs can use epics/issues to plan and outline their product group OKRs:
For more resources on OKRs, such as more about what OKRs are, the importance of OKRs at GitLab, and how to write OKRs and examples, see the company OKR handbook page. You can also find more resources in Product Management Learning & Development.
For previous quarters, please see previous quarter OKR timelines
We encourage suggestions and improvements to the Product OKR process so please feel free to raise an MR to this page. To keep us all aligned, as the process touches all teams across the company, please assign all MRs for collaboration, review and approval to Product Operations.