The stories
A story is a sequence, not a chart.
The stories your data is waiting to tell.
Each story below is a complete data story — a hero, a villain, the few scenes that carry it, the branches it forks down, and the decision it exists to produce. A deck of scenes assembles into these tracks; your data decides which scenes are true and which branch the story takes. Some play live on demo data; all are real templates.
Candidate stories for CRO / Line Executive — pre-authored, not generated. Which ones actually fire is decided by their data.
The Health Check
trackThe recurring people update that reports steady states as findings and moves the meeting to what's moving.
villain · The fog — dashboards that bury the two things that matter under forty that don't
dashboard-fog · recurring-update · prioritization · steady-state-reporting
The Receipt
trackWe acted. Did it work? — answered with attribution honesty.
villain · Victory theater — the post-intervention review that declares success by enthusiasm
did-it-work · attribution · program-evaluation · budget-defense
These stories are the unit of delivery — a board pack, an insight-player run, a full presentation is a story track playing out. The database grows by program: engagement replays, the book corpus, and live use each supply new stories; the registry is the one master store. Bring data to the Story Finder to see which scenes confirm, or open The Quiet Exodus to watch one play end-to-end.