Revise feature prioritization criteria (#38327)

Updated criteria for prioritizing new features to include labels for UX
improvements and product maturity goals.

DONE: @noahtalerman and @allenhouchins update [product maturity
assessment](https://fleetdm.com/handbook/company/product-maturity-assessment)
for 2026.
This commit is contained in:
Noah Talerman 2026-01-22 10:08:00 -05:00 committed by GitHub
parent 3792b8bf83
commit ecf2d3ab7e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -503,8 +503,8 @@ New requests are reviewed daily by the Head of Product Design and a former IT ad
To prioritize a new feature, it must meet one of these criteria:
1. Bug
2. Small UX improvement that isn't quite a bug but it's so small that it's worthwhile
3. Contributes to Fleet's [near-term roadmap](https://docs.google.com/spreadsheets/d/1zwr59MpruIw4dsV-Qbk8xFbMrbHAV3qaRJDWM7-YrwU/edit?gid=1189480063#gid=1189480063).
2. Small UX improvement (`~spiffier` label) that isn't quite a bug but it's so small that it's worthwhile
3. Contributes to Fleet's [product maturity](https://fleetdm.com/handbook/company/product-maturity-assessment) goals for the current calendar year (`~product-maturity` label)
4. Core: a feature that accentuates and directly assists in the core purpose of the company: to guide people out of the thicket through the gift of openness. It's what differentiates us. [How Fleet defined "core"](https://docs.google.com/document/d/1Vr0F218Acr69eAgaD38zsyUUQ3Ik9HDEAlitT911BzU/edit?tab=t.0#heading=h.axp63q5pht7).
5. Context: a feature that customers consider mission critical for their particular buying situation. Can either be an existing customer request or a prospect request in an order form.