Helen made us justify every property on order_submitted. We cut seven of them. Checkout reporting stopped drifting after each release.
Event Taxonomy Studio
A supervised rewrite of the event names your App Analytics actually depends on — including the ones nobody wants to delete.
What you leave with
- A verb–object naming contract your engineers can implement without a weekly translation meeting.
- A property list that survives a schema freeze, with types and allowed values written down.
- A retirement log for events that inflate funnels, plus an agreed sunset date.
- A one-page identity note covering anonymous users, logins, and the gaps you will not pretend to close.
Modules
01
The verb–object contract
We strip adjectives out of event names and ban “clicked”, “interacted”, and “engaged” unless they describe a specific control.
02
Properties that survive a freeze
Each property gets a type, an owner, and a rule for nulls. If marketing wants a new label every sprint, it lives in a map, not in the stream.
03
Identity, sessions, and the anonymous gap
Where a user id actually attaches, what a session means on mobile, and which joins you should stop requesting from analytics.
04
Funnels without vanity
One conversion path rebuilt with explicit inclusion rules. We will mark steps you currently count that do not belong.
05
Review clinic: your live dictionary
You bring an export. The room marks collisions, duplicates, and events that exist only because a vendor wizard suggested them.
Instructor
Dr Helen Ashworth
Studio director. Previously analytics lead at a UK marketplace; now runs the Cheshire clinics. She will not debug your warehouse, and she will say so in the first hour.
Informational fee
A Desk Seat on this programme is listed at £1,180 for one person across five clinics. Studio Pair and House Cohort fees sit on the seats page. This site does not take payment.
Questions we actually get
Do we need a specific analytics vendor?
No. Bring Mixpanel, Amplitude, PostHog, a warehouse table, or a spreadsheet export. The work is the dictionary, not the logo on the chart.
What will this programme not cover?
We do not cover warehouse modelling, dbt, or reverse ETL. If your team lives in SQL models, this room will feel product-shaped. That is a real limitation, not a teaser for a later upsell.
Can a whole squad attend?
Yes, as a House Cohort. We cap the room at twelve so the review clinic still has time to mark your events, not just lecture.
Is there a recording?
A condensed notes pack is sent after each clinic. Full recordings are not released; people speak more honestly about bad event names when the tape is not circulating.
From recent rooms
I came in thinking our taxonomy was “mostly fine”. The collision list in week one was eighteen lines long. We are still working through it, which is the point.