Cohort cards that survive a finance read

Warm audience work stalls when finance cannot trace definitions. Cohort cards should read like product specs: inputs, assumptions, refresh rules, and what happens when data thins.

We favor short paragraphs over diagrams in board packs. Diagrams help practitioners, but paragraphs survive email forwards. Each card names the signal, the window, the dedupe rule, and the stage it feeds.

Cross-team reviews improve when cards carry version numbers. A version bump means someone changed a definition, not that the algorithm got moody. That distinction matters inside compliance-aware industries.

This article does not replace mentorship in View-Based Cohort Blueprints, yet it mirrors the worksheets we use on day one. Steal the structure, not the prose.