The packet shore
Every event that is allowed to exist. Named as a verb-object, owned by a role, dated. Anything not on the shore is treated as driftwood — useful perhaps, never a KPI.
Method
The Telemetry Atlas
A cartographic habit for app analytics. Not a tool. A way of placing every packet on a grid so that “engagement” cannot hide in an unnamed corner.
Most product teams inherit a fog: events named after tickets, properties added in a panic before a board, and a retention chart whose denominator nobody will claim. The Atlas is how Controlpacketgrid draws that fog on paper before anyone opens a vendor.
It is taught inside Signal Architecture and used, more lightly, in the four-week Ledger Seat. You can read it here without enrolling; you cannot fake the discipline without a live app.
Four plates
What we actually draw
Property contour
Types, null policy, and the few enumerations you will not let engineering extend without a note. Contours that keep moving are how “plan” became seventeen strings in a Manchester fintech we still use as a caution.
Retention relief
A surface, not a single line: day grain, week grain, and the cohort cut you are willing to defend. Relief maps show valleys — the silent week — rather than a heroic mountain of “stickiness”.
The forbidden sea
What we will not count: staff, QA, infighting between web and iOS identifiers, and vanity packets that fire because a designer liked a tooltip. Publishing this plate internally is often the hardest week.
Why paper first
A map that only lives in a BI tool will be edited by whoever has the password.
Governance is part of the drawing.
United Kingdom teams in health, games, and marketplaces all arrive with a different fog. The Atlas does not standardise their products. It standardises the argument: who may add a packet, how long a name may live after a feature dies, and which retention cut is allowed in a board pack.
If you want the method with a viva attached, the flagship term is the honest route. If you only need the shore and the contour, the Ledger Seat is enough. Either way, write to the desk with the product, not with a wish for “better dashboards”.