The manuscript
You export the current event list, however shameful. We mark collisions, screen-shaped names, and properties that will never be read in a decision.
Flagship studio
Retention Telemetry Studio
Twelve weeks. One live catalogue. A ledger you can defend in a steering meeting, including the sentences about what you still cannot know.
Who it is for
Product managers, analysts, and mobile engineers who already have an SDK in production. If you are choosing a vendor from a blank page, wait. If your only goal is a badge with a platform logo, this is the wrong room — we say so again in the FAQ.
Modules
Identity without romance
Anonymous, signed-in, restored installs, and household devices. You write a memo engineers can implement. Mixing those streams because a vendor made it a toggle is treated as an error.
Session windows
Timeout defaults are rarely honest. We reconstruct sessions against commuting, bedtime, and one-thumb use, then you publish the window in the taxonomy.
Retention clocks
When week-four starts. What “retained” means in your product, not in a template. Thin samples stay thin on the page.
The board sentence
A cohort narrative with limitations in plain English. If the lift is small, you say so. Colour is optional; the sentence is not.
Learning outcomes
- A rewritten event dictionary with objects, verbs, and a short list of banned names.
- An identity rule that survives a tool change.
- A documented session window and retention clock.
- One cohort readout with sample size and limitations attached.
- The habit of refusing vanity DAU as a steering metric for a quiet subscription.
Mira Halston
Mira spent a decade in mobile product in London and Cardiff before moving the teaching to Penuwch. She still marks taxonomies by hand. She will not remotely configure your Amplitude project.
Questions we actually get
Do you teach every vendor dashboard?
No. That is a real limitation, not a tease. The studio does not include vendor certification for Amplitude, Mixpanel, or Firebase. You will work in spreadsheets, SQL excerpts, and a vendor-agnostic ledger. We assume an SDK is already installed. If your employer requires a platform badge, this is the wrong room.
How much homework?
Plan for four to six hours outside the weekly live room. Week three is heavier because naming proliferates. People who also ship on Fridays should clear that week in the diary.
Can a whole team sit in?
The fee is for one named seat. A second person may observe if we agree in writing; they do not receive marked work. House Residency is the later format for a small team.
Is there a certificate?
A letter stating you completed the studio, if you want one. No credits, no university seal, no logo exam.
From people who sat the twelve weeks
Cardiff audio: we had been counting a trial at the paywall and again at the receipt. Week two made that indefensible. The memo is two pages and the review meeting lost twenty minutes of folklore. I still want a cleaner export from iOS, which the studio does not build for you.
Helena V., product lead, subscription audio — Cardiff
Useful, and slightly monastic. I would not enrol a designer who has never opened the tracking plan. The final cohort page is the artefact I keep on my desktop; the live rooms ran long.
Samir, Leeds
★★★★☆
Board-sentence week is the module I still use. We print sample size under the curve now. I wanted more SQL than we got; the excerpts arrived late for my taste.
Platform-style note · 4/5 · winter room