From 75b956bcb971285b957f091671f70e77c3ca2074 Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Wed, 13 Jul 2022 12:30:30 -0400
Subject: [PATCH] In Product handbook, add "epic" DRI (#6643)

---
 handbook/company.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/handbook/company.md b/handbook/company.md
index c4a2550336..db690f1cb9 100644
--- a/handbook/company.md
+++ b/handbook/company.md
@@ -281,13 +281,14 @@ At Fleet, groups define the relevant sections of the engineering org chart.  A p
 interim product manager):
 
 - Interface PM: Noah Talerman
-- Platform PM: Zach Wasserman
+- Platform PM: Mo Zhu
 - Agent PM: Mo Zhu
 
 Each group is associated with an engineering manager (EM), who, with their group of engineers, form the engineering members of the group.
 
-Each group's PM works very closely with engineers within their group:
+Each group's PM works closely with engineers within their group:
 - The PM **prioritizes** work and defines **what** to iteratively build and release next within their group's domain to best serve the group's goals and the company's goals as a whole. The PM communicates **why** this work is prioritized and works with engineering to come up with the best possible **how**.
+- The PM is responsible for epics. Sometimes initiatives require multiple issues that may, or may not, include multiple development groups. These initiatives are tracked as GitHub issues with the "epic" label. To make sure that all issues associated with the epic (child issues) make it into a release, one PM is assigned to the epic. It's the PM's responsibility to track progress and close the epic when the initiative is complete.
 - The EM (along with engineers) defines **how** to implement that definition within the surface area of code, processes, and rituals owned by their group while serving their group’s goals and the company's goals as a whole.
 
 ### Interface group