From b4db8d5cf55ce82d807767aeab8c538634f1b484 Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Wed, 21 Jan 2026 17:58:01 -0500
Subject: [PATCH] Product design handbook: Clarify guide updates during
 drafting (#38588)

Context:
https://fleetdm.slack.com/archives/C084F4MKYSJ/p1768936713202219
---
 handbook/product-design/README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/handbook/product-design/README.md b/handbook/product-design/README.md
index 4d14d00494..9f97065055 100644
--- a/handbook/product-design/README.md
+++ b/handbook/product-design/README.md
@@ -67,7 +67,9 @@ At Fleet, like [GitLab](https://about.gitlab.com/handbook/product-development-fl
 
 5. Add links to the user story as specified in the [issue template](https://github.com/fleetdm/fleet/issues/new?template=story.md).
 
-6. Draft changes to the Fleet product that solve the problem specified in the story.
+6. If you (Product Designer) have capacity to update Fleet's guides, add a link to the guide update PR in the "Feature guide changes" checkbox under the "Engineering" section. If not, it's up to the Engineer assigned to the story during implementation to make sure guides are updated.
+
+7. Draft changes to the Fleet product that solve the problem specified in the story.
    - Constantly place yourself in the shoes of a user while drafting changes.
    - Use dev notes (component available in our library) to highlight important information to engineers and other teammates. - Reach out to sales, customer success, and demand for a business perspective.
    - Engage engineering to gain insight into technical costs and feasibility.