Method
The Analytics Atlas
A shared legend for app analytics work at Route Maphub. Not a framework you pin on a wall. A set of map habits we refuse to drop when a vendor screen is prettier.
Landmarks before roads
A landmark is a named event that would still matter if the interface were redrawn. `playlist.saved` is a landmark. `home_hero_click` is graffiti. The Atlas insists you collect landmarks first, then draw the paths people take between them. Teams that reverse this order build beautiful funnels through rooms that no longer exist.
Legends are not optional
Every landscape we accept in a readout carries a legend: population, first valued action, window, exclusions, owner. If a tile cannot wear a legend, it is decoration. The Quiet Dashboard Audit exists largely to remove tiles that refuse this clothing.
Travelling parties
A cohort is a party that started under comparable weather. Marketing storms, broken builds, and staff accounts are not scenery; they are climate. Mixing them produces a path that nobody actually walked. Module three of the Studio is devoted to this unglamorous sorting.
Terrain, not a single slope
Retention is a landscape with cliffs, plateaus, and hostage valleys. Averaging them into one N-day line is how boards get surprised. Retention Cartography is the short workshop for teams who only need this chapter. The Studio spends a full module on it because most schemas collapse here.
Scale
The Atlas is deliberately small. It does not cover paid attribution, MMPs, or SKAN. Those are other countries. If that is your urgent map, write anyway and we will say so quickly rather than sell you the wrong passage.