Draft: Reorganize Product OKR sections

Related to:

• !94747 (closed)

Please provide a brief explanation for this change:

Due date: Fri Dec 10

This MR will continue moving the Product OKR page toward a more digestible SSOT for the Product team. The page has served as a living history of the OKR process, but those sections have now been removed and will live on in the gitlog if reference is needed in the future.

The current and previous quarter OKR data has been moved to the top and placed within collapsible sections. This will give visitors looking for data a way to access it immediately without scrolling, while also allowing visitors who are looking for Process information to get to that section quickly without scrolling past vast amounts of data.

Please indicate the types of revisions being suggested for the Product Handbook (please check all that apply):

• Small improvement (typos, clarifications, etc.)
• Adding a new section
• Modifying existing section
• Documenting a new process
• Adding a new page or directory
• Other

Please indicate Milestone

• Assigned to Milestone

Author Checklist

• Provided a concise title for the MR
• Provided a brief explanation for this change (Say why, not just what)
  • (Attach screenshots, Slack conversations, etc. as necessary)
• Indicated the types of changes included in this MR
• Verified that no confidential data is in this MR
• Assigned reviewers for this change to the correct DRI(s)
  • 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 in 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.
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #product or #whats-happening-at-gitlab linking to this MR.
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.