9 December 2025 · Notes
Write-ups that survive a leadership review
Leadership reviews destroy memos by compression. A twelve-page appendix becomes three slides. The recommended action becomes a vibe. The caveat falls off the last slide. An App Experiment Readout System treats that compression as a known threat and designs the source file to survive it.
Open with a verb: ship, hold, iterate, or retire. Put the exposure definition in the same block. Cap the body at two pages. Charts can live in an attachment that is allowed to be ignored. If a director only forwards page one, they should still have the action, the guardrail status, and one limitation.
The limitation should be specific. “More data would help” is not a limitation. “We cannot separate new Android installs from Play listing traffic during week two” is. Specific limits travel; vague humility does not.
Cohort Readout Lab times the spoken version at twelve minutes with a hard stop. The leave-behind is the same two pages, not a new narrative invented for the room. If the room changes the action, the author updates the file the same afternoon. That update rule sounds clerical. It is the difference between an auditable system and folklore.
We mark these write-ups in the studio for structure, not for whether the business liked the outcome. A clean hold is a successful readout. A muddy ship is not.