Ritual Heading with OKR planning subheading (#4861)

* Ritual Heading with OKR planning subheading

Proposing to add the ritual heading to handbook/people in line with [https://github.com/fleetdm/confidential/issues/1013] and [https://github.com/fleetdm/fleet/issues/4671].

cc: @hollidayn

* Ritual update

Added OKR planning context and ritual steps to "Ritual" section of handbook.

* Move ritual section above Slack channels

Co-authored-by: Eric <eashaw@sailsjs.com>
This commit is contained in:
Charlie Chance 2022-04-04 17:19:54 -06:00 committed by GitHub
parent 4ff9f6702d
commit d7505b4665
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -248,6 +248,18 @@ When the final signature is added to an envelope in Docusign, it is marked as co
link: drive.google.com/[destinationFolderID]
```
## Rituals
### OKR Planning
OKRs help inform what to prioritize, and communicate company goals while encouraging cross team collaboration.
At the end of the quarter, and at key points throughout the quarter (every 3 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 they are finalized 1 week from when topdown OKRs were initially reviewed.
- Finalized OKRs are shared company-wide and at "all hands" and, at least to some degree, become public.
## Slack channels
Please see [Brand > Slack channels](https://fleetdm.com/handbook/brand#slack-channels).