Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 31

Update README.md (#13482)

Browse source
This commit is contained in:
Marko Lisica 2023-08-27 02:56:03 +02:00 committed by GitHub
parent 4c8a112cf7
commit 62c07307ce
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
handbook/product/README.md
View file

@ -64,7 +64,7 @@ For external contributors: please consider opening an issue with reference scree
- 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/company/ceo). 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.
+ **Feedback** mode — you know the design is not ready for final review, but would like to get early feedback. Before bringing something in feedback mode consider whether the CEO will be best for giving feedback or if it would be better suited for someone else (engineer or PM).
- 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.