From 26fe4012dbcc201bb20f90a6576c145e02b5d76f Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Tue, 18 Mar 2025 15:46:48 -0400 Subject: [PATCH] Product Design handbook (#27247) - Update what Product Designers work on when we hit capacity --- handbook/product-design/README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/handbook/product-design/README.md b/handbook/product-design/README.md index b5039d724d..f08d6bc2ce 100644 --- a/handbook/product-design/README.md +++ b/handbook/product-design/README.md @@ -78,11 +78,10 @@ Additionally: - If the story has a requester and the title and/or description change during drafting (scope change), notify the requester. The customer DRI should confirm that the updated scope still meets the requester's needs. - Each [product group](https://fleetdm.com/handbook/company/product-groups#current-product-groups) stops drafting once they reach engineering capacity for the upcoming engineering sprint. This way, we avoid creating a backlog which causes us to spend time updating soon-to-be stale designs. It's up to the product group's Product Designer to stop drafting and shift their focus to the following tasks: - - Run back through the unestimated user stories and do extra iterations to make sure they're as good as we think they are + - Run back through the test plan for unestimated user stories and make sure they're as good as we think they are - Go through the Fleet UI and look for bad/inconsistent text - - Go through bugs to see if there’s Product Design input needed + - Go through the reference docs and look for issues (inconsistent naming/formatting, broken links, etc.) - File stories and draft changes for making form fields in the Fleet UI consistent (fixing conventions, moving out the tooltips, etc.) - - File stories and draft changes for bringing the screen width down to 375px. (one screen at a time, in which we can squeeze it into engineering sprints as front-end only work, small stories, doesn't compete with other stuff) >**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. >