From b7ac7afafc902a3d50e648aabf3d1a23a97798ef Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Thu, 17 Apr 2025 11:24:09 -0400
Subject: [PATCH] Product Design: when we reach capacity (#28330)

@eugkuo and I realized it's important to design further out than 1
sprint. Even when we reach capacity. To do this, we can convert user
stories on the drafting board to air guitars.
---
 handbook/product-design/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/handbook/product-design/README.md b/handbook/product-design/README.md
index f0f710e8a3..83cf9119ca 100644
--- a/handbook/product-design/README.md
+++ b/handbook/product-design/README.md
@@ -80,6 +80,7 @@ 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:
+  - Wireframing for air guitars. This way, we can see further ahead and make better design and engineering decisions.
   - Dogfooding: pick up any issues in the "New requests" or "Ready" column on the 🍽️ Dogfood board
   - 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