01
Taxonomy before dashboards
Most App Analytics programmes start with a charting tool. We start with the nouns. If checkout_complete and purchase_success both fire, no visualisation will rescue the week.
Correspondence studio — Outer Hebrides desk
Measure the product you actually shipped, not the one the deck described.
Stream Kernelcore teaches App Analytics as a craft: naming events so they age, reading cohorts without flattery, and writing instrumentation that a successor can still trust. We keep the roster small on purpose.
Request the Retention Telemetry Studio syllabus
From the journal
What we insist on
Four disciplines we will not skip.
02
Cohorts with a paper trail
Every retention curve in class ships with the inclusion rule written in plain English. If you cannot explain who is missing, you are not ready to present the number.
03
Readouts, not slide theatre
We practise a two-page memo: what moved, what we trust, what we do next Tuesday. Executives can have a appendix. They cannot have ambiguity dressed as insight.
04
Instrumentation that outlives the author
You will document owners, deprecation dates, and the reason a property exists. Vanity events are retired in public, not left to haunt the schema.
Flagship programme
Retention Telemetry Studio
An eleven-week atelier for product people who already have an SDK installed and still cannot explain week-four retention without a caveat. You will rebuild one live funnel, write a property dictionary, and defend a readout in front of a visiting mentor.
Informational fee: £2,850 for a Studio Bench seat. See seats for other arrangements. No checkout on this site.
Open the studio notesVoices from recent benches
Specific, and not uniformly glowing.
The property dictionary exercise in week three stopped a quiet war between growth and core product. We had been counting “activated” two different ways since February. I still think the live clinic timetable is tight if you are also shipping, but the dictionary was worth the collision.
Imani Okafor · product analytics, consumer fintech · Retention Telemetry Studio
Margot made us write the inclusion rule on the first slide. Our board pack is shorter now, which nobody asked for and everyone prefers.
Client in grocery delivery · Manchester
I came for funnels and left arguing about event deprecation. The Signal Atlas page is the piece I still open on Mondays.
Theo P. · Edinburgh
Signal Atlas
A public map of the events we consider load-bearing.
Not a vendor catalogue. A living index of identities, sessions, funnels, and the questions each should answer. Use it before you add another SDK property.
Browse the atlasCorrespondence
If your schema already feels haunted, write to the desk.
We answer within two working days. Seats are limited; we do not manufacture urgency.
Open a note