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

Handbook: Add note about different design review "modes" (#12727)

Browse source
This commit is contained in:
Rachael Shaw 2023-07-13 13:09:37 -05:00 committed by GitHub
parent 93a03ad216
commit 125590f345
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
handbook/product/README.md
View file

@ -61,6 +61,9 @@ For external contributors: please consider opening an issue with reference scree
- Prepare your draft in the user story issue.
- Prepare the agenda for your design review meeting, which should be an empty document other than the proposed changes you will present.
- Review the draft with the CEO at one of the daily design review meetings, or schedule an ad-hoc design review if you need to move faster. (Efficient access to design reviews on-demand [is a priority for Fleet's CEO](https://fleetdm.com/handbook/business-operations/ceo-handbook). Emphasizing design helps us live our [empathy](https://fleetdm.com/handbook/company#empathy) value.)
- When introducing a story, clarify which review "mode" the CEO should operate in:
+ **Final review** mode — you are 70% sure the design is 100% done.
+ **Feedback** mode — you know the design is not ready for final review, but would like to get early feedback.
- During the review meeting, take detailed notes of any feedback on the draft.
- Address the feedback by modifying your draft.
- Rinse and repeat at subsequent sessions until there is no more feedback.