Names
Events as object, action, and property. If two teams cannot share a name without a meeting, the atlas stops here. This is the work of Event Taxonomy Studio.
The Signal Atlas
A four-layer map we use to keep app analytics from collapsing into a single overcrowded dashboard. It is taught across the programmes; this page is the public sketch.
Cuts
Cohorts with windows, exclusions, and a calendar footnote. Default vendor cohorts are treated as drafts. This is Cohort Instrumentation.
Paths
Funnels as forensic objects: empty steps, permission prompts, 3-D Secure, store review weather. Mobile Funnel Forensics lives here.
Claims
The one-page readout: a claim, a caveat, a next instrument. Board Briefing Craft and Experiment Readouts both spend their hours on this layer.
Why a map
App analytics fails when every question is asked at once.
A United Kingdom product org will often jump from “what should we name this?” to “why did D7 drop?” in the same stand-up. The atlas forces a pause. If Layer I is rotten, we do not debate Layer II. If Layer II has no exclusion list, we do not publish a Layer IV claim.
Students sometimes want to start on claims because claims are what get you into the exec room. We let them, once, then walk back down the map when the claim cannot be reproduced.
Draw the atlas on a whiteboard before you open the vendor. If you cannot point to the layer you are in, you are decorating. Rowan Calder · studio note, 2024See where each layer is taught Ask for a fit conversation