Here is the standard, company-wide process for OKRs. Engineering has some small deviations from (and extensions to) this process.
We sometimes have Engineering OKRs that require assistance from Product to ensure the issues are scheduled in that quarter. An example would be work to burn down our SUS backlog. As our quarters use calendar months, and our product development means we release every month on the 22nd, there is a disconnect that means we can 'lose' development time. To start work in the first milestone of a quarter (which starts just before the fiscal quarter), we need the issues to be in validation phase 3 of the preceding milestone.
As a result, Engineering will communicate with Product 6 weeks before the start of the quarter for any upcoming OKRs that need scheduling assistance from PMs. This is earlier than the typical company timeline for OKRs, but should not be a large proportion of Engineering OKRs in any quarter anyway.
As of 2021-05-01 the Product and Engineering Divisions are using a third-party vendor, Ally.io, for OKRs.
Ally has provided a feature that allows you to embed OKR views into our Handbook. This is done via a sharing option that produces an embeddable iFrame link. This option is available for any "OKR View." For example, you might embed OKRs from the "Active period" view (current quarter) or the "Previous period" (last quarter), or you might embed granular views of Sub-Team OKRs. The embedded OKRs use a dynamic link that automatically updates each quarter without additional effort.
<iframe src="INSERT_URL_HERE" class="dashboard-embed" height="1500" width="100%" style="border:none;"> </iframe>
1500is optimal for Engineering's structure (3 OKRs x 3 KRs).
We are actively tracking the following important feature requests to improve our workflow efficiency.
We will use the following guidelines to a clear standard and consistency.
“CultureAmp Survey Action Item”,
“ReverseAMA Action Item”
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.
* Raise first reply-time SLA for premium from 92% to 95%
Please be aware of these completion rules for KRs that are linked to GitLab issues with the GitLab integration:
The Key Result percent completion will roll up to the objective equally unless the objective is manually configured for unequal KR contributions under the Progress -> Manage Contributions setting in the objective.
This process should begin on the first day of the subsequent quarter, and complete no later than two weeks after.
@mention your direct report DRI in Ally and ensure retrospection is captured in that OKR/KR object.
The Chief Technology Officer and the leaders of each department meet synchonously on the second Tuesday in the month after each quarter ends to discuss the OKRs from the previous quarter. This is an opportunity to collaborate on cross-functional initiaties with the focus being the retrospective. Leaders will voice-over the good, bad and try items from the past quarter. The meeting will not cover the status and scores of the OKRs.