Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Handbook: Working groups (#32278)

Browse source 
- First working group will be #g-ux

Based on GitLab:
https://handbook.gitlab.com/handbook/company/working-groups/

---------

Co-authored-by: Luke Heath <luke@fleetdm.com>
This commit is contained in:
Noah Talerman 2025-08-27 11:48:18 -07:00 committed by GitHub
parent 61fdd8c2a2
commit bbbd19558c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 43 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
handbook/company/product-groups.md
View file

@ -96,6 +96,49 @@ The goal of the website group is to increase and exceed [Fleet's product maturit
> The [Slack channel](https://fleetdm.slack.com/archives/C097P4TAPRR), [kanban board](https://github.com/orgs/fleetdm/projects/92), and [GitHub label](https://github.com/fleetdm/fleet/labels?q=%23g-website) for this product group is `#g-website`.
## Working groups
Like a product group at Fleet, a working group is an arrangement of people from different functions. What makes a working group unique is that it is tasked with achieving a high-impact business goal fast. A working group disbands when the goal is achieved so Fleet stays fast and avoids unnecessary process.
Working groups are for important work that needs to be done quickly, when asynchronous work would be too slow.
Working groups have their own section in the handbook that includes the name, goal, resources, and contributors. See the commented out section in the handbook for an example.
Items to cover in the section:
- Name of the working group
- Desired business outcomes (goals)
- Link to the working group Slack channel and GitHub project
- Who is involved. This should include who the DRI is.
- Timeline. When will the working group start? When do we think we'll be done by?
### UX group
The goal of the UX group is to catch the Fleet product up with the [latest brand colors/styles](https://github.com/fleetdm/confidential/issues/11765) from the website (fleetdm.com), address [UX debt (spiffier)](https://github.com/fleetdm/confidential/issues/11868), and ship the Fleet product's first [2 graphs](https://github.com/fleetdm/confidential/issues/11864).
This group will kick off on 2025-08-27 and plans to wrap up on 2025-09-29.
| Responsibility | Human(s) |
|:----------------------------------|:--------------------------|
| Product Designer | [Mike Thomas](https://www.linkedin.com/in/mike-thomas-52277938) _([@mike-j-thomas](https://github.com/mike-j-thomas))_
| Product Manager (DRI) | [Noah Talerman](https://www.linkedin.com/in/noah-talerman/) _([@noahtalerman](https://github.com/noahtalerman))_
| Quality Assurance | [Janis Watts](https://www.linkedin.com/in/janis-watts-b080ab94/) _([@jmwatts](https://github.com/jmwatts))_
| Developer | [Rachel Perkins](https://www.linkedin.com/in/rachelelysia/) _([@rachelelysia](https://github.com/rachelelysia))_, Luke Heath](https://www.linkedin.com/in/lukeheath/) _([@lukeheath](https://github.com/lukeheath))_
<!--
Example working group section
### Name
Goal
| Responsibility | Human(s) |
|:---------------|:-----------|
| |
| |
| |
-->
## Making changes
Fleet's highest product ambition is to create experiences that users want.