Flagship programme
An eight-week studio in which your app’s event catalogue is treated as a literary object: named, versioned, and occasionally retired in public.
This is not a click-path certification for a single vendor. Interfaces move; a poorly named signup_success follows you for years.
Modules
Object, action, and tense. Why User as a prefix is almost always a confession that nobody owned the noun. Students rewrite twelve events from a provided “haunted” catalogue.
Types, enumerations, and the difference between a missing property and a legitimate null. We treat the dictionary as a contract that QA can fail a build against.
Anonymous IDs, known users, and the household iPad. We measure what a stitch drops, then write the caveat in language a trustee could read.
When an event’s meaning shifts, history is not a suggestion. Students draft a deprecation notice with dual-write windows.
A ninety-minute council: intake form, reject reasons, and a public log. We practise saying no to a growth experiment that wants a one-off event.
How to keep Amplitude or Mixpanel as a drafting table while the warehouse remains the filing cabinet. Light SQL, heavy discipline.
Each seat presents a real or reconstructed slice of their app analytics. The room annotates; the instructor does not rescue a weak name.
A six-page note: what the taxonomy now claims, what it still cannot claim, and which three events will be deleted on a named date.
Instructor
Studio director. Previously principal analyst for a London marketplace, where she inherited four overlapping “purchase” events and a dashboard nobody would sign. She now reads student dictionaries the way a solicitor reads a lease.
Limitations, stated
No. Those consoles appear as examples, not as the syllabus. If your employer needs a vendor badge, they should buy it from the vendor. We will not pretend a week of screenshots is instrumentation literacy.
Only if it is already cleared for external discussion. Most students work from a redacted extract or a reconstructed catalogue. We will stop a session rather than handle raw end-user payloads.
The naming grammar still applies. Health and children’s products add consent constraints we flag, but we are not a clinical or ICO consultancy. You remain responsible for lawful processing.
Critique is the product. Refunds follow the rules on our refund page, not the temperature of week seven.
From people who sat the atelier
Week five’s governance ritual is the piece I still use. We now reject events in writing. I wish we had been told, more loudly, that engineering would still ship a shadow event during a hack day; the atelier cannot police your culture from Sulby.
Owen H. · Bristol · staff engineer
Margot made us read our own onboarding_complete definition out loud. It did not survive the sentence.
N. Okonkwo · product analytics · London
★★★★☆
Worth the correspondence wait. The recorded reading on identity is dry, and I skipped it once; I should not have.
Platform review · App analytics track
Tell us which product you measure and how many events you believe you have. We reply within two working days.