From 576c5df9dee310b52e9fbb4b79df6b770d880f0e Mon Sep 17 00:00:00 2001
From: Ringo <117302805+Ringoshere@users.noreply.github.com>
Date: Tue, 22 Nov 2022 13:35:11 -0800
Subject: [PATCH] Handbook: Acronym clarification (#8796)

On the 'OKR planning' - it would be helpful to explain.
Eg. (Objective Key Results)
---
 handbook/business-operations/ceo-handbook.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/handbook/business-operations/ceo-handbook.md b/handbook/business-operations/ceo-handbook.md
index c3813c397d..a09cadd2ee 100644
--- a/handbook/business-operations/ceo-handbook.md
+++ b/handbook/business-operations/ceo-handbook.md
@@ -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.