From 8d20e8a21bd027e30d3f9f01750771c79373681d Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Mon, 29 Sep 2025 16:33:04 -0400 Subject: [PATCH] Product Design handbook: 4 product groups (#33591) --- handbook/product-design/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/product-design/README.md b/handbook/product-design/README.md index 051a50a787..b1c70bb352 100644 --- a/handbook/product-design/README.md +++ b/handbook/product-design/README.md @@ -192,7 +192,7 @@ If the original request is a customer request, the PD also assigns the relevant [User stories](https://fleetdm.com/handbook/company/product-groups#scrum-items) are intended to be [drafted](#drafting) and estimated in a single sprint. When the Product Designers (PD) knows a user story will be pushed, it is the PD's responsibility to notify stakeholders: 1. Comment on the GitHub issue and at-mention the Head of Product Design and anyone listed in the requester field. -2. If `customer-` labels are applied to the user story, at-mention the [VP of Customer Success](https://fleetdm.com/handbook/customer-success#team) in the #g-mdm, #g-software, or #g-orchestration Slack channel. +2. If `customer-` labels are applied to the user story, at-mention the [VP of Customer Success](https://fleetdm.com/handbook/customer-success#team) in the #g-mdm, #g-software, #g-orchestration, or #g-security-compliance Slack channel. > Instead of waiting until the end of the sprint, notify stakeholders as soon as you know the story is being pushed.