Skip to content

Use "馃Β Product design intake & outtake" board for new request triage - #52221

Closed
noahtalerman wants to merge 1 commit into
mainfrom
noahtalerman-patch-91
Closed

Use "馃Β Product design intake & outtake" board for new request triage#52221
noahtalerman wants to merge 1 commit into
mainfrom
noahtalerman-patch-91

Conversation

@noahtalerman

Copy link
Copy Markdown
Member

No description provided.

@noahtalerman
noahtalerman marked this pull request as draft August 31, 2026 20:29
@noahtalerman noahtalerman changed the title Use drafting board for new request triage Use "Product design intake & outake" board for new request triage Aug 31, 2026
@noahtalerman noahtalerman changed the title Use "Product design intake & outake" board for new request triage Use "馃Β Product design intake & outake" board for new request triage Aug 31, 2026
@noahtalerman noahtalerman changed the title Use "馃Β Product design intake & outake" board for new request triage Use "馃Β Product design intake & outtake" board for new request triage Aug 31, 2026
@noahtalerman

Copy link
Copy Markdown
Member Author

Closing in favor of #51867, which now carries this plan (the drafting board stays, renamed "馃Β Product design intake & outtake", handling new-request triage and confirm-and-celebrate; drafting-in-progress work stays on each product group's board).

The Head of Product Design is responsible for going through the inbox on the [drafting board](https://github.com/orgs/fleetdm/projects/67) and adding the correct [product group](https://fleetdm.com/handbook/company/product-groups#continuous-flow) label.

Once labeled, each Product Designer (PD) is responsible for reviewing the inbox on their product group's board and deciding whether each new request contributes to Fleet's [product maturity](https://fleetdm.com/handbook/company/product-maturity-assessment) goals for the current calendar year. If yes, the PD adds the `~product-maturity` label so the request is reviewed at the next [unpacking the why](#unpacking-the-why) call. If a request meets a different [criteria for prioritization](https://fleetdm.com/handbook/company/product-groups#criteria-for-prioritization), the PD removes the "Unpacked" checkbox in the feature request issue and either prioritizes a [user story or quick win](https://fleetdm.com/handbook/company/product-groups#work-items) to bring through [fast draft or full draft](https://fleetdm.com/handbook/company/product-groups#drafting-tracks-full-draft-vs-fast-draft), or removes it from the product group board and adds it to the [feature fest](https://fleetdm.com/handbook/company/product-groups#feature-fest) board.
Once labeled, each Product Designer (PD) is responsible for reviewing the inbox and deciding whether each new request contributes to their [product group's goal](https://fleetdm.com/handbook/company/product-groups#criteria-for-prioritization). If yes, the PD adds the `~product-maturity` label so the request is reviewed at the next [unpacking the why](#unpacking-the-why) call. If a request meets a different [criteria for prioritization](https://fleetdm.com/handbook/company/product-groups#criteria-for-prioritization), the PD removes the issue from the drafting board and either prioritizes a [user story or quick win](https://fleetdm.com/handbook/company/product-groups#work-items) to bring through [drafting](https://fleetdm.com/handbook/company/product-groups#drafting), or adds the issue to the [feature fest](https://fleetdm.com/handbook/company/product-groups#feature-fest) board.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Once labeled, each Product Designer (PD) is responsible for reviewing the inbox and deciding whether each new request contributes to their [product group's goal](https://fleetdm.com/handbook/company/product-groups#criteria-for-prioritization). If yes, the PD adds the `~product-maturity` label so the request is reviewed at the next [unpacking the why](#unpacking-the-why) call. If a request meets a different [criteria for prioritization](https://fleetdm.com/handbook/company/product-groups#criteria-for-prioritization), the PD removes the issue from the drafting board and either prioritizes a [user story or quick win](https://fleetdm.com/handbook/company/product-groups#work-items) to bring through [drafting](https://fleetdm.com/handbook/company/product-groups#drafting), or adds the issue to the [feature fest](https://fleetdm.com/handbook/company/product-groups#feature-fest) board.
Once labeled, each Product Designer (PD) is responsible for reviewing the inbox and deciding whether each new request contributes to their [product group's goal](https://fleetdm.com/handbook/company/product-groups#current-product-groups). If yes, the PD adds the `~product-maturity` label so the request is reviewed at the next [unpacking the why](#unpacking-the-why) call. If a request meets a different [criteria for prioritization](https://fleetdm.com/handbook/company/product-groups#criteria-for-prioritization), the PD removes the issue from the drafting board and either prioritizes a [user story or quick win](https://fleetdm.com/handbook/company/product-groups#work-items) to bring through [drafting](https://fleetdm.com/handbook/company/product-groups#drafting), or adds the issue to the [feature fest](https://fleetdm.com/handbook/company/product-groups#feature-fest) board.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants