Skip to content

Revise Product OKRs timeline details

Omar Fernandez requested to merge product-okr-timeline into master

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

We had issues this quarter with some teams getting surprised by OKRs too late in the planning cycle. This was mainly because we didn't share and publicize draft OKRs per our stated timeline. (this is one of the issues raised in https://gitlab.com/gitlab-com/Product/-/issues/12414).

This MR doesn't change the timeline, as it would have worked. Instead, it clarifies that:

  1. 2 weeks prior to the new quarter start all groups, stage, and section leaders should have the draft OKRs so that they can write their respective OKRs.
  2. KR owners can propose changes to an OKR at any point within the quarter following the agreed to process

I'm also deleting an out-of-date and unused section tracking past year OKRs. If there's a need for this, we can discuss and add back in an updated list.

The related MR Product!825 (merged) will make changes to the product issue template to correspond to this timeline update.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Omar Fernandez

Merge request reports