House method

The Cohort Atlas

A map is not a dashboard. The Atlas is the method we use in every sitting: how a group of users is born, how it weathers a release, and which cuts are honest enough to take upstairs.

Abstract dark field of connected nodes suggesting a data map
Not a product screenshot — a reminder that a cohort is a population, not a sparkline
Birth

When the cohort starts

We do not default to ‘install day’. For some apps the first paid action is the birth. For others it is the first week in which a core verb happens twice. The Atlas forces that decision into a written line before any table is drawn.

Cut

What you are allowed to slice

Acquisition channel is the laziest cut in App Analytics. The Atlas prefers first-platform, first-country, and first-successful-task. If a cut cannot be explained to support in one sentence, it does not enter the board pack.

Weather

Annotation, not airbrush

Store outages, bank holidays, and a celebrity tweet are weather. The Atlas keeps a margin for them so that a Tuesday dip is not treated as a personality change in the user base.

Why it lives as its own page

Teams arrive asking for a tool comparison. They leave needing a shared map. The Cohort Atlas is that map: vendor-agnostic, slightly stubborn, and designed so that two analysts in the same company stop arguing about whose N-day retention is the real one.

If you want to practise the Atlas on your own artefact, the place to do it is the open programmes. If your company needs the map drawn under NDA, write to the desk for Private Advisory.

Start with Retention Signal Studio