House method
Cohort Atlas, the drawing we actually use.
This is not software. It is a sequence of plates — paper or slides, we do not mind — that stop a team treating App Analytics as a single glowing curve.
-
Plate I — Population
Who is on the map. First-open is not first-value. Paid, organic, invite, and staff traffic are separate inks. If you cannot name the exclusion rules, the plate is blank.
-
Plate II — Windows
Retention is a window, not a vibe. We draw D1, D7, and a slower plate the product actually cares about — often D28 for mobile, sometimes a billing cycle. Mixing them in one line is how board packs go soft.
-
Plate III — Terrain
The events that define “still here.” We prefer a small set with dates of birth. Deprecated names stay in a graveyard plate so nobody resurrects them in a panic before a launch.
-
Plate IV — Claim
One sentence a sceptical partner can attack. The atlas is finished when that sentence includes a limitation. Courses at System Maphub are drills in writing this plate without theatre.
Where it is taught
The atlas is the spine of the flagship term
Cohort Cartography spends eight weeks filling these plates with your own product, or with our lent datasets if yours cannot leave the building. The Event Taxonomy Clinic is essentially Plate III in slow motion. Funnel Integrity is what happens when Plate III has been lying to Plate II.
If you only want the notes, Open Atlas contains worked examples. If you need someone to sit inside your politics, that is a Commissioned Survey, not a course.