Product Design responsibility: triage new bugs (#26348)

handbook/company/product-groups.md

@@ -469,6 +469,8 @@ Once reproduced, QA documents the reproduction steps in the description and move
 
 QA has reproduced the issue successfully. It should now be transferred to product design if it is a released bug, or engineering if it is unreleased.
 
+If the bugs is missing reproduction steps, it's removed from the drafting board and sent back to the "inbox" state.
+
 Remove the “:reproduce” label, add the following labels:
 
 1. The relevant product group (e.g. `#g-mdm`, `#g-orchestration`, `#g-software`). Make your best guess, and product design will change if necessary.

handbook/product-design/README.md

@@ -37,9 +37,11 @@ If a customer/prospect request is missing a Gong snippet or requires additional
 As soon as we've addressed the next quarter's objectives, the Head of Product Design cancels the daily meeting. 
 
 
-### Product design check in
+### Triage new bugs
 
-The Head of Product Design summarizes the current week's design reviews to discuss with the CEO.
+Product Designers are responsible for triaging all new reproduced bugs.
+
+Learn more [here](https://fleetdm.com/handbook/company/product-groups#in-product-drafting). 
 
 
 ### Drafting
@@ -146,17 +148,6 @@ At Fleet, features are placed behind feature flags if the changes could affect F
 > Fleet's feature flag guidelines is borrowed from GitLab's ["When to use feature flags" section](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#when-to-use-feature-flags) of their handbook. Check out [GitLab's "Feature flags only when needed" video](https://www.youtube.com/watch?v=DQaGqyolOd8) for an explanation of the costs of introducing feature flags.
 
 
-### View Fleet usage statistics
-
-In order to understand the usage of the Fleet product, we [collect statistics](https://fleetdm.com/docs/using-fleet/usage-statistics) from installations where this functionality is enabled.
-
-Fleeties can view these statistics in the Google spreadsheet [Fleet
-usage](https://docs.google.com/spreadsheets/d/1Mh7Vf4kJL8b5TWlHxcX7mYwaakZMg_ZGNLY3kl1VI-c/edit#gid=0)
-available in Google Drive.
-
-Some of the data is forwarded to [Datadog](https://us5.datadoghq.com/dashboard/7pb-63g-xty/usage-statistics?from_ts=1682952132131&to_ts=1685630532131&live=true) and is available to Fleeties.
-
-
 ### Prepare reference docs for release
 
 Every change to how Fleet is used is reflected live on the website in reference documentation **at release day** (REST API, config surface, tables, and other already-existing docs under /docs/using-fleet).