From 2ffd8ec91dea070888cc5bbd61c4005a417cea65 Mon Sep 17 00:00:00 2001
From: Sampfluger88 <108141731+Sampfluger88@users.noreply.github.com>
Date: Wed, 27 Sep 2023 21:32:46 -0500
Subject: [PATCH] Update communications.md (#14169)

---
 handbook/ceo.md                    | 2 +-
 handbook/company/ceo.rituals.yml   | 6 +++---
 handbook/company/communications.md | 6 +++---
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/handbook/ceo.md b/handbook/ceo.md
index 5f17fae611..cfe5885c29 100644
--- a/handbook/ceo.md
+++ b/handbook/ceo.md
@@ -106,7 +106,7 @@ When the final signature is added to an envelope in DocuSign, it is marked as co
 
 ## Responsibilities
 
-### Manage g-ceo intake
+### Process new requests from the #g-ceo kanban board
 The Apprentice to the CEO is the DRI for the [#g-ceo kanban board](https://app.zenhub.com/workspaces/g-ceo-645b0eab68a4d40c0795ff61/board?sprints=none) and responsible for [managing all intake](https://fleetdm.com/handbook/company/communications#manage-intake) including issues and PRs.
 
 
diff --git a/handbook/company/ceo.rituals.yml b/handbook/company/ceo.rituals.yml
index 90cd790ab8..2caf559d69 100644
--- a/handbook/company/ceo.rituals.yml
+++ b/handbook/company/ceo.rituals.yml
@@ -19,11 +19,11 @@
   moreInfoUrl: "https://fleetdm.com/handbook/company/ceo#process-the-ceos-email"
   dri: "sampfluger88"
 -
-  task: "Manage g-ceo intake"
+  task: "Process all /"New requests/" on the #g-ceo kanban board"
   startedOn: "2023-07-29"
   frequency: "Daily ⏰"
-  description: "Process the CEO's inbox"
-  moreInfoUrl: "https://fleetdm.com/handbook/company/communications#manage-intake"
+  description: "Process and prioritize all new issues and PRs"
+  moreInfoUrl: "https://fleetdm.com/handbook/company/ceo#process-new-requests-from-the-g-ceo-kanban-board"
   dri: "sampfluger88"
 -
   task: "Process the CEO's calendar"
diff --git a/handbook/company/communications.md b/handbook/company/communications.md
index b7af500345..b22840d45c 100644
--- a/handbook/company/communications.md
+++ b/handbook/company/communications.md
@@ -84,14 +84,14 @@ maintaining an expressive labeling system. For example, instead of a label calle
 | `:`               | Verb        | `:dev`, `:research`, `:design`
 | `~`               | Adjective   | `~blocked`, `~frontend`, `~backend`
 
-### Manage intake
-Team members [process their department's kanban boards](https://fleetdm.com/handbook/company/why-this-way#why-lean-software-development) daily, prioritizing all new intake within 24hrs from when it was submitted. 
+### Process new requests
+Team members [process their department's kanban boards](https://fleetdm.com/handbook/company/why-this-way#why-lean-software-development) daily, prioritizing all new requests including issues and PRs within one business day.
 
 To process intake team members will:
 - Inspect each item in the "📨 New requests" column and understand the next steps needed to complete the task.
 - Indicate to the requestor when they can expect the task to be completed by placing each item in the appropriate column (e.g. Not yet, Planned, In progress) and estimate if necessary.
 - If the goal/user story is unclear, assign the issue to the requestor and at-mention them in an issue comment asking to clarify the intended action. 
-- If the task is to be backlogged (e.g. Not yet), place the issue in the "Not yet" column and at-mention the requestor in an issue comment. Explain why the task is unable to be prioritized and provide a tentative ETA on when the task will be completed.  
+- If the task is to be backlogged (i.e. "Not yet"), place the issue in the "Not yet" column and at-mention the requestor in an issue comment. Explain why the task is unable to be prioritized and provide a tentative ETA on when the task will be completed.  
 
 
 ### Making a pull request