Rodmersham studio · Kent

The product already speaks. Most teams mishear it.

App Analytics is not a wall of charts. It is the quiet work of naming what a person did, when the session broke, and which release actually moved retention.

Open the Event Taxonomy Studio

Laptop showing product analytics charts on a dark wooden desk — From the 2025 autumn cohort: a taxonomy wall before it is committed to the tracker.

On the calendar

Three programmes currently offered

Each one is built around a shipping problem, not a vendor certification. Browse the full list on the programmes page.

Printed charts and a calculator on a planning table

Flagship · 8 weeks

Event Taxonomy Studio

Design an event catalogue that survives a redesign, a new platform, and a change of analytics vendor.

Studio syllabus

Intensive · 5 weeks

Retention Curves Intensive

Read D1 through D30 without collapsing the story into a single percentage. Cohort tables, not vanity snapshots.

See listing

Bar chart printouts spread across a desk

Clinic · 4 weeks

Session Attribution Clinic

Follow an in-app action across cold starts, deep links, and the awkward hour when identity is still anonymous.

Ask about the next clinic

From a product lead in Leeds

“We arrived with 186 events and left with 61. The painful part was deleting the ones that made the weekly dashboard look busy.”

S. Rahman · consumer finance app

The studio does not promise a prettier Mixpanel project. Practitioners come because their funnels disagree with what support hears on the phone. The work is naming, ownership, and the nerve to retire a property that never earned its keep.

A longer set of voices — including one that still disputes our stance on auto-tracked screens — lives on the Voices page.

How the studio teaches

Four working habits, not a slide library

Name the verb first

Events describe what a person did, not what a screen is called. We spend the first seminars arguing about verbs until the catalogue can be read aloud without a designer in the room.

Keep identity boring

Anonymous IDs, logins, and device resets are treated as a plot, not a footnote. If you cannot explain who “user_id” is at 9pm on a Saturday, the retention chart is theatre.

Critique live schemas

Participants bring a real event list (redacted). We mark it in the room. Theoretical taxonomies are refused; they collapse the moment a marketer asks for a new campaign parameter.

Write the limitation down

Every readout we review must state what the data cannot see: backgrounded iOS sessions, sampled web events, consent gaps. Hiding the gap is how dashboards go stale.

A small ledger

17studio cohorts since 2019

612practitioners through the door

2,140event schemas marked in critique

38htypical flagship contact time

Who sits in the room

Product, data, and the person who owns the tracker

Product managers who inherited an analytics project they cannot defend in a steering meeting.
Analysts tired of joining tables that were named in a hurry during a 2021 growth sprint.
Mobile engineers asked to “just add Amplitude” without a property dictionary.
Founders of UK consumer apps who want a reading of retention that a board will not later unsay.