Lead tutor
Priya Nandakumar
Spent nine years inside a London mobility company, first as an analyst, later as the person who had to explain why “trips” meant three different things. Teaches the hearings; marks the identity memos herself.
Flagship · 11 weeks
Cohort Instrumentation
A taught room for people who already live in an analytics tool and need a standard their next hire can inherit.
Outcomes
What you should be able to do on week twelve
Publish an event taxonomy of forty items or fewer, each with a verb, an owner, and a retirement rule. Write an identity memo covering anonymous users, logins, and shared devices. Produce one App Analytics readout that names the cohort window in the first paragraph and states a limitation in the last.
You will not leave as a certified Mixpanel trainer. If that is the badge you need, a vendor course will be a better receipt.
Modules
01
Inventory and the graveyard
Export every event. Mark last-fired dates. Argue, in writing, which names were screens in disguise.
02
Taxonomy hearing
Public critique of five live events from volunteers. The room votes on verbs. Tutors break ties when marketing language creeps in.
03
Identity contracts
Anonymous to known, merges, and the damage a family iPad does to retention. Homework is a one-page contract, not a diagram.
04
Properties as adjectives
When a property should have been an event, and when an event is a property wearing a costume. Includes the house list of 37 patterns.
05
Cohort windows as contracts
Day-7 versus “about a week.” You freeze a window and defend it against a fictional growth lead who wants it longer.
06
Funnel forensics, compressed
Double counts, error-state fires, and the onboarding drop that was a timezone bug. Not a full Funnel Forensics ticket.
07
Retention cartography
N-day, unbounded, and rolling. Which map your board is actually looking at, whether they know the name or not.
08
Experiment readouts
A sample size you can explain without a p-value shrine. Guardrail metrics. When to refuse a ship decision.
09
The written standard
Margins from tutors. You revise until a new engineer could implement week-one events without Slack archaeology.
10
Readout studio
Draft, critique, rewrite. Charts may appear as figures. The grade sits on the sentences.
11
Open hearing
You present to the room. Alumni may attend. We record nothing; take your own notes.
From recent rooms
“The identity memo was the piece my CTO actually read. The taxonomy hearing was noisier than I like, and I still think week six tries to cover too much funnel archaeology in one evening.”
James Whitaker · staff engineer, Nottingham
★★★★☆
Short platform note after the autumn cohort: “Useful on cohort contracts. Less useful if your SDK is still half-installed. They did warn us.”
Anonymous, insurance app
Questions we actually get
Do I need to be a data scientist?
No. You need permission to change event names and enough access to export them. SQL helps in week seven; it is not a gate.
Which App Analytics vendor do you teach?
None as a product. Examples rotate between warehouse SQL, Amplitude, and Mixpanel so that no one mistakes a menu label for a method.
What is the real limitation?
We cannot repair a tracking plan if engineering will not ship event changes inside the eleven weeks. Several students leave with a beautiful standard and an unchanged production log. We will say this on night one. If your platform team is frozen until next quarter, wait, or buy Field Notes and do the inventory alone.
Are evenings the only option?
Open Cohort hearings start at 18:30 UK time. Private Atelier can sit in the day. We have not run a weekend room; childcare and energy both suffer.