Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 21 Packages Projects Releases Wiki Activity

Drafting: Assisting other product groups (#41791)

Browse Source 
Real world example: https://github.com/fleetdm/fleet/issues/33418#issuecomment-4070514703
This commit is contained in:
Noah Talerman
2026-03-16 17:04:17 -04:00
committed by GitHub
parent dcfa21317c
commit 8533b17749
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
handbook/product-design/README.md
+4 -2
View File
@@ -86,6 +86,10 @@ Additionally:
- How the story addresses the original request.
- If the original request is a customer promise, specify what the due date is and who it's for.
- Sometimes a Product Designer in one product group drafts a user story or bug that will be specified, estimated, or implemented by another product group. This happens when the original group is constrained by design or engineering capacity. You'll know this is happening when they're a `assisting-g-*` label on the story or bug.
- For example, if a #g-mdm Product Designer drafts a story that #g-security-compliance will implement, the #g-mdm Product Designer invites the #g-security-compliance Tech Lead to #g-mdm design reviews. Once the story is approved, it’s brought to #g-security-compliance user story review.
- At that point, the #g-security-compliance Product Designer becomes the [DRI](https://fleetdm.com/handbook/company/communications#directly-responsible-individuals-dris). They bring the story to their group’s estimation and handle questions from their team, coordinating with others as needed.
>**Questions and missing information:** Take a screenshot of the area in Figma and add a comment in the story's GitHub issue. Figma does have a commenting system, but we use GitHub issues so that all questions/conversation live in one place.
>
>For external contributors: please consider opening an issue with reference screenshots if you have a Figma related question you need to resolve.
@@ -109,8 +113,6 @@ Before assigning an EM, double-check that the "Product" section of the user stor
If the story is tied to a customer feature request, the Head of Product Design (HPD) is responsible for adding the feature request issue to the [🏹 #g-customer-success board](https://github.com/fleetdm/fleet/issues#workspaces/g-customer-success-642c83a53e96760014c978bd/board). This way the Customer Success Manager (CSM) can review the wireframes and provide feedback on whether the proposed changes solve the customer's problem. If the changes don't, it's up to the HPD to decide whether to bring the user story back for more drafting or file a follow up user story (iteration).
Sometimes, a Product Designer from one product group will draft a user story or bug that is implemented by a different product group. This happens when the original product group is constrained by design or engineering capacity. If this happens, the Product Designer from the product group that implements the story/bug is the [DRI](https://fleetdm.com/handbook/company/communications#directly-responsible-individuals-dris) for that story/bug. This means, the product group members always reach out to their product group's Product Designer with any questions. It's up to this Product Designer to answer questions or reach out to other team members if necessary.
### Revise a draft currently in development
Expedited drafting is the revision of drafted changes currently being developed by