From 0492dcbcdf1a48903fcb31befd4439a285cf1a18 Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Thu, 17 Jul 2025 13:17:56 -0400
Subject: [PATCH] Making a request: Fast track for Fleeties (#31004)

Why?
- Fleetie feature requests are creating a bottleneck during the
[Unpacking the
why](https://fleetdm.com/handbook/product-design#unpacking-the-why)
stage in the new feature request pipeline.
- Most, if not all, Fleetie feature requests don't need to be unpacked.
They come from dogfooding use cases that don't require a former IT admin
to understand.
---
 handbook/company/product-groups.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md
index 285747fd9d..190ec7388c 100644
--- a/handbook/company/product-groups.md
+++ b/handbook/company/product-groups.md
@@ -384,6 +384,8 @@ To make a feature request or advocate for a feature request from a customer or c
 
 New requests are reviewed daily by the Head of Product Design and a former IT admin during the ["Unpacking the why"](https://fleetdm.com/handbook/product-design#unpacking-the-why) call. If the request meets the [criteria for prioritization](#criteria-for-prioritization), the request will be added to the upcoming feature fest (`~feature fest` label). If it doesn't, the request will be put to the side and the requester will be notified.
 
+> **Fast track for Fleeties:** Fleeties do not have to wait for "Unpacking the why" to add a request to feature fest. If you think Fleet is missing something and have described in detail what you already tried, it can be moved directly to the [🎁 Feature fest board](https://github.com/orgs/fleetdm/projects/72). Just add the `~feature fest` label.
+
 
 ### Criteria for prioritization