diff --git a/handbook/product/README.md b/handbook/product/README.md
index 7a8815eb0c..8e01b41dc2 100644
--- a/handbook/product/README.md
+++ b/handbook/product/README.md
@@ -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.