House method
Signal Studio
A way of sitting with product data that is closer to editing a manuscript than to touring a vendor’s demo. It is the spine of every Connectvectorgrid programme.
Signal Studio began as a Saturday table in Ridsdale: six people, one export, no slides until the event names had been read aloud. The rule still holds. If two people in the room would define “activated” differently, we do not chart activation that afternoon.
The method has three movements. First, inventory — what is actually firing, in which app versions, on which platforms. Second, naming — a catalogue with owners, not a spreadsheet graveyard. Third, withholding — a written list of questions the current stream cannot answer, so that nobody fills the gap with a blended rate.
What the table refuses
Vanity totals that mix logged-out browse with paying habit. Funnels that ignore deep links. Retention slides that change definition between months. A/B results presented without an exposure event. We have watched United Kingdom product teams lose a quarter to each of these, usually with attractive tooling.
We also refuse to pretend that privacy law is a later chapter. Session replay, device identifiers, and advertising-network properties are discussed as legal and ethical objects, not as “nice to have later”.
What the table keeps
Paper. Students still leave with a bound-looking PDF atlas because a file you can annotate in a meeting behaves differently from a live dashboard someone else controls. We keep Saturday critique even when it is inconvenient. We keep a mild pace: five weeks is short; fourteen is long enough to notice a tracking seam after a release.
If this sounds like the work you already wish your analytics ritual did, look at the programmes or write to the house.