diff --git a/handbook/product/README.md b/handbook/product/README.md
index 88e0599199..f466619fcb 100644
--- a/handbook/product/README.md
+++ b/handbook/product/README.md
@@ -442,7 +442,7 @@ Directly Responsible Individuals (DRI) engage in the ritual(s) below at the freq
 | Pre-sprint prioritization          | Sprintly (Monday)        | The Head of Product Design and each group's EM meet before each sprint to align on priorities and note what wasn't completed in the previous sprint. Head of Product Design.                                                                                                                                                              | Noah Talerman            |
 | Bug review (#g-endpoint-ops)                               | Weekly (Tuesday)         | The Head of Product design meets with the engineering manager and a product quality engineer to ensure synchronization on bug prioritization and actions preceding Endpoint ops estimation sessions.                                                                                                         | Noah Talerman            |
 | Bug round-up   | Mid-sprint | Head of Product Design will compile a list of churned bugs, including issue numbers, specifics, and age. They will also notify the Customer Success team of any churned bugs that have customer tags  | Noah Talerman |
-| Churned bug review                            | Mid-sprint     | The Head of Product Design meets with the CEO and Head of Product Development to examine churned bugs and categorize them as either schedule, needs prioritization, or de-prioritize.                                                                    | Churned bug clean-up | Mid-sprint  | Following the churned bug review, Head of Product Design completes the churned bug clean-up, ensuring all necessary follow-up tasks are actioned to classify bugs as schedule, needs prioritization, or de-prioritized. This may include relocating bug tickets, adjusting labels, communicating with stakeholders, writing documentation, and closing issues. | Noah Talerman |                                                                 | Noah Talerman            |
+| Churned bug review                            | Mid-sprint     | The Head of Product Design meets with the Head of Product Development to examine churned bugs and categorize them as either schedule, needs prioritization, or de-prioritize.                                                                    | Churned bug clean-up | Mid-sprint  | Following the churned bug review, Head of Product Design completes the churned bug clean-up, ensuring all necessary follow-up tasks are actioned to classify bugs as schedule, needs prioritization, or de-prioritized. This may include relocating bug tickets, adjusting labels, communicating with stakeholders, writing documentation, and closing issues. | Noah Talerman |                                                                 | Noah Talerman            |
 | Stand-up (#g-website)           | Daily (Monday - Thursday) | The website product team meets to discuss completed tasks, upcoming work, and address any questions. | Mike Thomas |
 | Prioritization session (#g-website) | Sprintly                | The website product team meets to prioritize tasks for the upcoming sprint. | Mike Thomas |
 | Design review (#g-website)      | Daily (Monday - Thursday) | Review designs from the website team.                                       | Mike Thomas |