Studio · United Kingdom
Most teams collect more App Analytics than they can read. We teach the slower work: naming events that survive a redesign, drawing funnels that match how people actually move, and sitting with a retention curve until it stops flattering you.
Cohort XIV · autumn sitting · Bearley & remote
“I arrived able to export a funnel. I left able to argue, calmly, that the funnel was the wrong shape for the product we actually ship.”Priya N., product lead · Leeds
Programmes
Each sitting is small. We do not tour every vendor screen. We work on the measurement problems you already have, using App Analytics as the shared language.
Taxonomy, properties, and the politics of naming. The programme we return to when a product has outgrown its first tracking plan.
Cohorts, return curves, and the difference between a product people visit and a product people inhabit.
How to sit with an A/B readout in a product meeting without reaching for the first significant digit.
How the room works
App Analytics is easy to install and hard to trust. A new property appears, an old event is quietly renamed, and six months later nobody can reconstruct why checkout “dropped.” Our pedagogy starts with the sentence you should be able to say about a user, then works backwards to the event.
Students bring a live product — or a public app they know well — and rebuild a slice of its map. We mark work in conversation, not with a quiz bank. The United Kingdom cohort meets in Bearley twice a year; the rest of the sitting is remote and asynchronous.
Journal
Short essays on measurement, written after class, not before it.
If your verbs describe the interface, they will rot. If they describe the job, they travel.
A pretty N-day chart can hide a product that only the power users still recognise.
Places
Tell us the product you measure and the question you cannot yet answer. We reply within two working days, usually with a reading list rather than a pitch.