Coalbrookdale · established 2018

We teach product teams to hear what their apps are actually saying.

App Analytics, treated as a language rather than a dashboard hobby. Event names, properties, and the awkward gaps between what shipped and what was measured.

Autumn syllabus

Analytics charts on a dark workstation
Studio notes, week three
1,263 practitioners who have sat the atelier since 2018, mostly from product and data pairs.
19 live cohorts, never more than twenty-two seats, run from the Coalbrookdale rooms and remotely.
6 wks typical span between finishing Event Taxonomy Studio and shipping a revised production schema.

Note

Most App Analytics programmes start with tools. We start with grammar: what an event is allowed to mean, and what it must never try to mean.

Flagship programme

Event Taxonomy Studio

A six-week close reading of how mobile and hybrid apps name behaviour. You leave with a versioned taxonomy, a property dictionary, and a written argument for what will not be tracked.

Tuesdays, 18:30–20:30 UK. Next cohort opens in September. Fees are listed without checkout — we invoice after a conversation.

Open the studio notes

Laptop showing product metrics during a working session

From the rooms

What people actually remark on

“The taxonomy review in week four was bruising. Helen would not let us keep button_click as a family of events. Two months later the warehouse queries stopped needing a three-page cheat sheet. I still think the homework load in week two is a bit much if you are also on-call.”

— Priya N., product analytics, Leeds

“Funnel Forensics taught me to distrust a 100% step. We found a silent drop caused by a dual-write on the Android client. Not glamorous. Extremely useful.”

— Client in grocery retail, Midlands

How we teach

Reading before reporting

App Analytics fails in the naming, not in the chart. We spend the first fortnight on verbs, objects, and the difference between an intent and a side effect. Only then do we open a product.

You work on your own app where possible. If you cannot, we issue a fictional subscription product with a deliberately messy event log.

Small rooms
Nineteen people at most. Critique is spoken, not dropped in a chat later.
Written artefacts
A taxonomy, a tracking plan, and a one-page limitation note you can take to engineering.
United Kingdom hours
Live sessions sit on UK evenings. Recordings exist, but the argument happens live.

Also on the syllabus

Other programmes this year

  • 4 weeks

    Funnel Forensics

    Find where a conversion story is a measurement artefact. Android, iOS, and webview traps included.

    View
  • 5 weeks

    Retention Cartography

    Cohort tables, resurrection windows, and the habit of not celebrating D1.

    View
  • 3 weeks

    Attribution for Subscription Apps

    Windows, paywalls, and the UK habit of asking where the credit actually belongs.

    View

Journal

Recent notes from the house

City towers at dusk

Measurement

Why your retention curve lies in the first seven days

D1 is a traffic report. The interesting movement starts when the novelty has worn off.

Read the note
Quiet office desks

Taxonomy

Naming events without drowning the warehouse

A verb-object rule that survives the third product manager.

Read the note
Code on a monitor

Clients

When sessionisation breaks on hybrid apps

Webviews, background timers, and the evening someone deleted a session.

Read the note

Coalbrookdale

If you want the next cohort list, write to the house.

We reply within two working days. There is no automated waitlist.

Write to us