Flagship · 6 weeks · live remote
Event Taxonomy Studio
A working catalogue for one product surface, written so QA, analytics, and engineering can argue from the same page.
What you will be able to do
- Write event names as verb-object pairs that survive a copy rewrite on the button.
- Reject properties that cannot be tested or that carry unnecessary personal data under UK GDPR practice.
- Assign an owner and a retirement date so orphaned events do not linger after a feature is pulled.
- Hand a one-page contract to engineering that specifies trigger, volume, and failure behaviour.
Modules
-
Inventory without sentiment
Export what you already fire. We cluster duplicates and mark events that only exist because a vendor wizard suggested them.
-
The verb wall
Lock a short list of verbs for the product. “Clicked” is allowed; “interacted” is not, unless you can define the interaction in one sentence.
-
Property dictionaries
Each field gets a type, an example, a null policy, and a reason to exist. This is the week most teams cut volume.
-
Triggers and QA scripts
When does the event fire on first paint, on success, on retry? You write the test a contractor could run on a Thursday.
-
Ownership and change control
Who may add an event without a review, and who may not. We practice a lightweight RFC that does not stall a weekly release.
-
The contract and the readout
You present the catalogue to a sceptical peer from another cohort. Feedback is written, not applause.
Instructor
Helen Morley
Helen spent nine years in product analytics inside UK marketplace and media companies before opening Workspace Pathhub in Waterston. She still reviews event contracts for two retainers and teaches every Taxonomy Studio herself; there is no substitute instructor on this programme.
Fee (informational)
£2,450
Per seat, including six live sessions, written feedback on one catalogue, and thirty days of async comments after the readout. This page does not process payment. If you proceed, we send a separate invoice from the Waterston office.
A three-seat team rate of £6,480 is available; it is still settled off-site.
Questions we get before enrolment
Do I need an existing tracking plan?
No. A messy export or even a list of screenshots is enough. We would rather start from chaos than from a plan nobody uses.
Will you instrument our app for us?
No. That is a real limitation of this course. We teach the catalogue and the contract; your engineers still write the calls. If you need implementation staff, say so on the contact form and we will tell you we are not that vendor rather than stretch the studio into a build.
What if our stack is not Segment or Mixpanel?
The studio is vendor-agnostic. Examples have included Snowplow, a homegrown collector, and a warehouse-only pipeline. Bring whatever you use.
Notes from the last two cohorts
Helen stopped us renaming every screen event after a brand refresh. The “verb wall” from module two is now pinned next to our stand-up board.
Owen, Leeds — product manager
The async comments after week six were slower than I wanted — two replies took four days — but the contract template is what we still open in pull requests.
Anonymous client in insurance