Home / Programmes / Event Family Studio

Event Family Studio

A six-week cohort for product, data, and mobile engineers who need a shared event taxonomy before the next release train.

Planning board with clustered sticky notes representing event families

What you leave holding

A versioned catalogue (Markdown plus a simple CSV), a naming RFC your staff engineers can argue with, and a retirement list for events that only exist because someone copied a Firebase sample in 2019.

You will not leave with a fully wired analytics stack. Instrumentation remains your team’s work; we teach the map, not the vendor console.

Learning outcomes

  • Separate families (progress, transact, notify, content) from screen names.
  • Write object.verb names that survive a marketing rebrand.
  • Assign property owners, types, and allowed values.
  • Run a volume audit that finds collisions without downloading every raw log.
  • Facilitate a freeze meeting so new events cannot sneak in unsigned.

Modules

  1. Inventory without judgement. Export names from your current SDK. Cluster duplicates. Do not rename yet.
  2. Family grid. Place each cluster on the seven-layer house model used at Auditmatrixgrid.
  3. Object.verb workshop. Live critiques; weak names are rewritten in the room.
  4. Property dictionary. Types, nulls, PII flags, and who may extend a key.
  5. Volume pass. Sample production counts; archive names that have not fired in 90 days.
  6. Freeze and handover. RFC, owners, and a 30-day exception process.
Portrait of instructor Maeve Croft

Instructor

Maeve Croft

Maeve spent nine years leading product analytics in Edinburgh before opening the Stronvar studio. She still reviews every catalogue that leaves Event Family Studio and refuses to sign off on screen-as-event naming.

Notes from people who sat the studio

★★★★★

Week two’s object.verb rewrite saved us from shipping “HomeScreen_v3_viewed” into the warehouse.

Tom Hedges · Android lead · Bristol

The volume pass was slower than advertised because our warehouse access took three days. Maeve was frank about that; the method still held once we had counts.

Aisha · Manchester

Questions we hear before week one

Do we need Mixpanel, Amplitude, or GA4 already?

Any of them, or a warehouse-only setup. The studio maps names, not vendor UI. You will need export access to current event names.

Can a solo founder attend without an engineer?

Yes, but you will still need someone who can change instrumentation after the freeze. We will not implement trackers for you.

What is a real limitation of this programme?

Six weeks will not reconcile a multi-brand corporation with five analytics owners and no executive sponsor. If legal and marketing cannot attend the freeze meeting, the catalogue will drift within a quarter. We say this in the first call; we would rather decline the seat.

Is the fee refundable?

See the refund notice. Cohort seats have a cutoff before the first live session.