Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Handbook: Acronym clarification (#8796)

Browse source 
On the 'OKR planning' - it would be helpful to explain.
Eg. (Objective Key Results)
This commit is contained in:
Ringo 2022-11-22 13:35:11 -08:00 committed by GitHub
parent d9bf269c60
commit 576c5df9de
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
handbook/business-operations/ceo-handbook.md
View file

@ -25,7 +25,7 @@ If you don’t share a meeting with Mike, please post in the #help-ceo channel w
“Emergency” requests must be addressed the same day. If you need to contact the CEO ASAP, please post in #help-p1 Slack channel. This will send a text message to Mike’s cell phone, even if it’s in "do not disturb" mode.
## OKR planning
OKRs help to inform what to prioritize and communicate company goals while encouraging cross-team collaboration.
OKRs (Objective Key Results) help to inform what to prioritize and communicate company goals while encouraging cross-team collaboration.
At the end of the quarter and key points throughout the quarter (every three weeks), we review the status of each OKR (depending on the KR, either 100% or ≥70% completion is considered "success")
- Review topdown and departmental OKRs as they are turned in.
- OKRs are finalized one week from when topdown OKRs were initially reviewed.