Here is the standard, company-wide process for OKRs. Engineering has some small deviations from (and extensions to) this process.

OKR Kickoff

This process should begin no later than two weeks before the end of the preceding quarter. And kickoff should happen on or before the first day of the new quarter.

  1. OKR owners shouldauthor new issuesin the handbook project using the “Engineering OKR” description template
    • The issuetitleshould beFY20-Q2 Organization Type OKR: Objective phrase => 0%
      • Type should be one of “IACV”, “Product”, or “Team”
      • e.g. FY20-Q3 Engineering Product OKR: Build our product vision => 0%
    • Update the issuedescription
      • Add your Key results phrases to the issuedescription. Valid Key results are:
        • Raising a KPI from one specific value to another
        • Building out a new KPI
        • Failing either of the first two… Completing a high-profile project with specific outcomes
        • e.g. * Raise first reply-time SLA for premium from 92% to 95% => 0%
      • Add your manager’s and your direct report’s handles to the CC line
    • Assign the issue to yourself
    • Set the due date to the last day in the quarter
    • Apply the appropriate labels to make sure it appears in your appropriate column of our management board
    • Interlink related OKRs (usually by OKR type) of your manager and direct reports using the related issues field
  2. Get approvalprior to the first day of the quarterfrom your manager
    • For the VPE and their direct reports:
      • Do an MR to that quarter’s markdown handbook page
        • * Department: [Objective phrase](https://placeholder.com/) => 0% e.g.* Support: Raise first reply-time SLA for premium from 92% to 95% => 0%
        • Indent department level OKRs underneath the Engineering Division OKRs
        • One line for each objective
      • Assign the Mr to the VPE and address changes asynchronously like a code review
      • Discuss in 1:1 if needed
    • For everyone else: Ask you manager to do an async review of your issues via Slack or email and address any changes. Alternatively, discuss in a 1:1.
  3. Communicate dependencies to other divisions, departments, or teams. Encourage them to take on corollary OKRs.

    OKR Status

  • Update the OKR issue whenever you have additional information
  • For direct reports of the VPE, expect to give an update in each weekly 1:1 as part of the management issue board review.
  • For individuals that do a monthly key review meeting, expect to give an OKR update there.

    OKR Retrospection

    This process should begin on the first day of the subsequent quarter, and complete no later that two weeks after.
  1. OKR owners should score their OKRs in the issue
    • Update the overall score in the issue title.
    • Update the individual key result scores in the issue description.
  2. OKR owners should retrospect in the issue description.
  3. OKR owners should do an MR to that quarter’s OKR page with just the final scores after the objective phrase/link (e.g. => 70%) and assign it to their direct manager for review.
  4. The manager should review each individual issue, ask any questions, and merge
    • The OKR owner should incorporate any manager feedback like in a code review