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

Product design handbook: Clarify guide updates during drafting (#38588)

Browse source 
Context:
https://fleetdm.slack.com/archives/C084F4MKYSJ/p1768936713202219
This commit is contained in:
Noah Talerman 2026-01-21 17:58:01 -05:00 committed by GitHub
parent 9126c66687
commit b4db8d5cf5
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
handbook/product-design/README.md
View file

@ -67,7 +67,9 @@ At Fleet, like [GitLab](https://about.gitlab.com/handbook/product-development-fl
5. Add links to the user story as specified in the [issue template](https://github.com/fleetdm/fleet/issues/new?template=story.md).
6. Draft changes to the Fleet product that solve the problem specified in the story.
6. If you (Product Designer) have capacity to update Fleet's guides, add a link to the guide update PR in the "Feature guide changes" checkbox under the "Engineering" section. If not, it's up to the Engineer assigned to the story during implementation to make sure guides are updated.
7. Draft changes to the Fleet product that solve the problem specified in the story.
- Constantly place yourself in the shoes of a user while drafting changes.
- Use dev notes (component available in our library) to highlight important information to engineers and other teammates. - Reach out to sales, customer success, and demand for a business perspective.
- Engage engineering to gain insight into technical costs and feasibility.