Method

The Signal Atlas

Four verbs we use on every App Analytics engagement. If a dashboard cannot walk this path, it is furniture.

Abstract data visualization with layered nodes suggesting a map of signals
01 Capture

What happened

Raw fires, including the ugly ones: duplicates, background fetches, events named after a Jira ticket. We inventory before we moralise.

02 Name

What it is allowed to mean

A dictionary with owners. Synonyms die here. viewed is not completed, even if the designer hoped it was.

03 Cohere

What belongs together

Funnels, cohorts, and sessions that share a clock. Bank holidays in the United Kingdom are not “anomalies”; they are a calendar.

04 Decide

What changes on Tuesday

A chart earns its keep by naming a next action. If nobody will stop a campaign or ship a fix, the tile leaves the wall.

Why a map, not a stack

Vendors change. Warehouses change. The Atlas stays because it is a reading order. Students in Signal Cartography draw their own Atlas on week four; Closed Room teams redraw it after a merger when two taxonomies collide.

We keep a graveyard page. Retired events stay listed so nobody “reuses” checkout_start for a new meaning. That page is unglamorous and more valuable than a colour-coded OKR dashboard.