“Week four still stings. We retired forty-one events. The Android client was sending three names for the same paywall. I would have liked a second critique week; one felt abrupt.”
— Marcus Okafor, mobile lead, Bristol
Flagship · Kernel Atelier
Event Taxonomy Studio
A six-week close reading of how an app names behaviour. You leave with a versioned taxonomy, a property dictionary, and a limitation note engineering can actually use.
What you will hold at the end
A versioned event catalogue with owners.
A property dictionary that forbids silent synonyms.
A one-page note on what you will not track, and why.
A migration sketch from the current production mess.
Who it is for
Product managers who have inherited a swamp of click events. Analytics engineers who are tired of decoding names in SQL. Founders who want a language before they buy another App Analytics seat.
Modules
-
01
Verbs and objects
The house rule: an event is a verb plus a business object. We bury page_view as a default and recover it only when a screen is the object.
-
02
Properties that survive a rebrand
Identifiers, enumerated states, and the properties that must never be free text. You will delete several of your current fields.
-
03
Client, server, and the dual-write
Where the event should be born. We look at iOS, Android, and a hybrid webview that has been lying for a year.
-
04
Critique week
You present. The room annotates. Helen will not accept a family of events that all mean “interacted”.
-
05
Versioning and deprecation
How to retire legacy_signup without orphaning last year’s dashboards. Includes a freeze window.
-
06
The limitation note
A public document for your team: identity gaps, offline queues, and the questions this schema will never answer.
Instructor
Dr Helen Ashworth
Former measurement lead at a UK subscription publisher. Helen founded the studio after a rebrand left three incompatible event languages in production. She still marks papers in pencil.
Office hours: Thursday mornings, Coalbrookdale or video.
Fee (informational)
Kernel Atelier seating for this studio is £1,860 inc. VAT. Signal Desk notes covering the same grammar are £420 if you cannot attend live. There is no checkout on this page — write to the house and we invoice after we confirm a seat.
Tuesdays 18:30–20:30 UK, six consecutive weeks. Next live room: September.
A limitation you should know
This programme does not cover warehouse modelling, dbt, or server-side GTM. If your problem is a lakehouse, Foundry Residency is the closer fit. We will say so in the first reply rather than stretch the studio.
Questions we hear in week one
Do I need to bring my own app?
Preferably. If you cannot share logs, we issue “Northiron”, a fictional fitness subscription with a deliberately rotten schema. You will still write a real taxonomy; it simply will not ship.
Which App Analytics tools do you teach?
None as a vendor course. We work in the product you already have, provided events are inspectable. The grammar is the point. Tool buttons are homework, not the syllabus.
What if I miss a Tuesday?
Recordings exist. The critique in week four does not: if you miss it, you submit a written defence instead, which is slower and less kind.
Is there a certificate?
A letter from the house stating that your limitation note was accepted. We do not issue badges. Employers who know us ask to see the taxonomy.
From people who sat this studio
★★★★☆
Taxonomy Studio, September room. The property dictionary template is the thing I still open. The live pace assumes you can protect Tuesday evenings.
via the alumni list